login_file

Description

Log in to the AppScan® Enterprise Server using a token file (token files are created using the -persist option with the CLI login (in) command or when creating the AppScan Source for Automation user).

If the login is successful, the prompt changes to AllApplications>> to indicate that you are logged in.

Syntax

login_file server token_file [-acceptssl]
  • server: Required. Specify the URL for your Enterprise Server instance.
  • token_file: Required. Indicate the path and file name of the token file. If the token file was created with the CLI login (in) command, the file is ouncecli.token and it resides in the .ounce folder of the users home directory. If the token file was created for AppScan Source for Automation, the file is <data_dir>/config/ounceautod.token (where <data_dir> is the location of your AppScan Source program data, as described in Installation and user data file locations).
  • -acceptssl: Optional. Automatically accept SSL certificates. For more information, see AppScan Enterprise Server SSL certificates
    Important: If this argument is not included, logging in or publishing to the AppScan Enterprise Console will fail with error if an invalid certificate is encountered (if you have not already permanently accepted the certificate while logging in via another AppScan Source client product).

Example

User John Smith logs into the AppScan Enterprise Server, using a token file that was created on Windows from the CLI:

>> login_file https://myserver:9443/ase/ 
     C:\Users\Administrator\.ounce\ouncecli.token
Login successful.
AllApplications>>