Logging in to AppScan Enterprise Server from AppScan Source products

Most AppScan® Source products and components require a connection to an AppScan Enterprise Server. The server provides centralized user management capabilities and a mechanism for sharing assessments via the AppScan Source Database.

When you launch AppScan Source for Analysis, you are prompted to authenticate to an AppScan Enterprise Server. If you are running AppScan Source for Development in server mode, you are prompted to authenticate to an AppScan Enterprise Server when you first initiate an action that needs access to the server, such as launching a scan, or viewing scan configurations.

Logging in from AppScan Source for Analysis and AppScan Source for Development with an AppScan Enterprise Server user ID and password

In AppScan Source for Analysis, when logging in, you are prompted for:

  • User ID: Specify your user ID (depending on how your account was set up, this is a user ID that exists both on the AppScan Enterprise Server and in the AppScan Source Database - or it is a user ID that exists only in the AppScan Source Database).
    • If your AppScan Enterprise Server is configured to use Windows™ authentication, enter the domain and user name that you use to connect to the Enterprise Console (separate the domain and user name with \ - for example, my_domain\my_username).
    • If your AppScan Enterprise Server is configured with LDAP, enter the user name that you use to connect to the Enterprise Console.
  • Password: Specify the password for your user ID.
  • AppScan Enterprise Server: Specify the URL for your AppScan Enterprise Server instance. The format of this URL is http(s)://<hostname>:<port>/ase, where <hostname> is the name of the machine on which AppScan Enterprise Server has been installed and <port> is the port on which the server is running. An example of this URL is https://myhost.mydomain.hcl.com:9443/ase.

In AppScan Source for Development, when logging in, you are prompted for:

  • Server URL: Specify the URL for your AppScan Enterprise Server instance. The format of this URL is http(s)://<hostname>:<port>/ase, where <hostname> is the name of the machine on which AppScan Enterprise Server has been installed and <port> is the port on which the server is running. An example of this URL is https://myhost.mydomain.hcl.com:9443/ase.
  • User ID: Specify your user ID (depending on how your account was set up, this is a user ID that exists both on the AppScan Enterprise Server and in the AppScan Source Database - or it is a user ID that exists only in the AppScan Source Database).
    • If your AppScan Enterprise Server is configured to use Windows authentication, enter the domain and user name that you use to connect to the Enterprise Console (separate the domain and user name with \ - for example, my_domain\my_username).
    • If your AppScan Enterprise Server is configured with LDAP, enter the user name that you use to connect to the Enterprise Console.
  • Password: Specify the password for your user ID.

Using Common Access Card (CAC) authentication to log in from AppScan Source for Analysis and AppScan Source for Development

On Windows, you can connect to AppScan Enterprise Server using CAC authentication (http://www.cac.mil). Before doing this, you must set up AppScan Enterprise Server and AppScan Source for Common Access Card (CAC) authentication. If your Enterprise Server is set up for CAC authentication, you cannot use an Enterprise Server user ID and password for logging in.

In AppScan Source for Analysis, when logging in, you are prompted for:

  • User: Select your CAC Common Name from the list.
  • AppScan Enterprise Server: Specify the URL for your AppScan Enterprise Server instance. The format of this URL is http(s)://<hostname>:<port>/ase, where <hostname> is the name of the machine on which AppScan Enterprise Server has been installed and <port> is the port on which the server is running. An example of this URL is https://myhost.mydomain.hcl.com:9443/ase.

In AppScan Source for Development, when logging in, you are prompted for:

  • Server URL: Specify the URL for your AppScan Enterprise Server instance. The format of this URL is http(s)://<hostname>:<port>/ase, where <hostname> is the name of the machine on which AppScan Enterprise Server has been installed and <port> is the port on which the server is running. An example of this URL is https://myhost.mydomain.hcl.com:9443/ase.
  • User: Select your CAC Common Name from the list.
After clicking OK, you will be prompted by a Windows Security dialog box for your CAC card pin.
Tip:
  • If login fails, ensure that your AppScan Enterprise Server is set up correctly and that your certificate is valid. Check to see if you can access the AppScan Enterprise Server via a browser. If so, you should be able to select the certificate and log in.
  • If the login dialog box User field does not list available certificates, ensure that you have modified the java.security file in your JRE, as described in Enabling Common Access Card (CAC) authentication.
  • If you are not prompted by a Windows Security dialog box for your CAC card pin, ensure that the Microsoft Smart Card Resource Manager service is running. Note that this service may not run for some remote desktop connection types.

Logging in from AppScan Source for Automation and the AppScan Source command line interface (CLI)

Login actions are also required when running AppScan Source for Automation or the AppScan Source command line interface (CLI). See the HCL® AppScan Source Utilities User Guide for more information.

AppScan Enterprise Server SSL certificates

To learn about AppScan Enterprise Server SSL certificates, see AppScan Enterprise Server SSL certificates.

Resolving AppScan Enterprise Server certificate errors

If you are logging in to an Enterprise Server with an unknown certificate authority, you may receive a certificate exception or error upon login. AppScan Source includes a small utility that can help you correct this. The tool is <install_dir>\bin\certificatetool.bat (where <install_dir> is the location of your AppScan Source installation) - or <install_dir>/bin/certificatetool.sh on Linux and macOS.