Configuring the SQL Server database for AppScan® Enterprise
The AppScan® Enterprise Server configuration needs information about SQL Server. Configure the SQL Server first to save time during the AppScan® configuration. If you upgrade SQL Server to a newer version, follow these instructions as well.
To ensure security and prevent connection issues, follow these guidelines when configuring your SQL Server account for AppScan Enterprise.
-
Don't use the default '
sa' accountThe default SQL Server system administrator (
sa) login must not be used for AppScan Enterprise. Using the 'sa' account is a significant security risk because information about this account is public and its permissions can't be modified. Attempting to use the 'sa' principal will result in a connection error (Source: Cannot use the special principal 'sa'). Instead, create a dedicated SQL Server login with the appropriate permissions for AppScan Enterprise. -
Manage password expiration
Ensure that the password for the SQL Server account you use isn't expired and isn't set to expire. A connection can fail if the user password has expired, preventing the Configuration Wizard from completing successfully. If your organization's security policy requires password rotation, you must manually update the password in AppScan Enterprise after it has been changed in SQL Server. For more information, see Resetting Service Account Password in AppScan Enterprise through the ASE AdminUtil tool.
SQL Server properties
To define server properties:
- Right-click the server name and select Properties > Security.
- In the Server Authentication section, choose Windows™ Authentication mode or SQL Server and Windows Authentication mode and click OK.
SQL Server or Server\Instance name: <sql_server_host>\<sql_server_instance> instead
of SQL Server or Server\Instance name: <sql_server_host>.