Home
Administering
Learn how to administer the product.
Administering AppScan® Source
This section explains user management, permissions, application and project registration, and port configuration.
Creating AppScan® Source users
Typically, administrators will have users log in to AppScan® Source products with their AppScan Enterprise Server credentials. However, if there is cause for having AppScan Source users that do not exist in the AppScan Enterprise Server, administrators can create local AppScan Source users, according to the instructions in this topic.
AppScan® Enterprise Server authentication: Migration considerations for replacement of the IBM® Rational® Jazz™ user authentication component with IBM® WebSphere® Liberty
This topic describes user management-related migration considerations that you may need to consider if you are upgrading from a previous version of AppScan® Enterprise Server.

Welcome
Welcome to the documentation for HCL® AppScan® Source.
Introduction to HCL® AppScan® Source
HCL® AppScan® Source delivers maximum value to every user in your organization who plays a role in software security. Whether a security analyst, quality assurance professional, developer, or executive, the AppScan Source products deliver the functionality, flexibility, and power you need - right to your desktop.
What's New in AppScan® Source
Explore these new features that have been added to AppScan® Source - and note any features and capabilities that have been deprecated in this release.
Installing
Learn how to install the product.
Configuring
Learn how to configure the product.
Administering
Learn how to administer the product.
- Administering AppScan® Source
  This section explains user management, permissions, application and project registration, and port configuration.
  - User accounts and permissions
    Before AppScan® Source users can begin to scan or triage results, an administrator must create user accounts and assign permissions to the accounts.
  - Using AppScan® Source for Analysis in standalone mode
    You can use AppScan® Source for Analysis while not connected to an AppScan Enterprise or the AppScan Database Service. However, you will be unable to share scans or assessments with other AppScan Source clients.
  - Creating AppScan® Source users
    Typically, administrators will have users log in to AppScan® Source products with their AppScan Enterprise Server credentials. However, if there is cause for having AppScan Source users that do not exist in the AppScan Enterprise Server, administrators can create local AppScan Source users, according to the instructions in this topic.
    - AppScan® Enterprise Server authentication: Migration considerations for replacement of the IBM® Rational® Jazz™ user authentication component with IBM® WebSphere® Liberty
      This topic describes user management-related migration considerations that you may need to consider if you are upgrading from a previous version of AppScan® Enterprise Server.
    - Configuring automatic login of AppScan® Enterprise Server users
      By default, AppScan® Enterprise Server users can log in to AppScan Source and automatically be added to the AppScan Source Database (these users will be listed as AppScan Enterprise Server users). This feature can be configured in the AppScan Source for Analysis user interface according to the instructions in this topic.
    - Creating local product administrator users in AppScan® Enterprise Server Liberty
      As of AppScan® Enterprise Server Version 9.0.1, you have the ability to create a local product administrator user in AppScan Enterprise Server Liberty in order to administer AppScan Source. After the user is created, the AppScan Source Database must be registered with AppScan Enterprise Server using the administrator credentials.
    - Creating a user account for the Automation Server
      A user account is required for Automation Server use. This user account must be registered with the Automation Server during installation or by command line post-installation. A corresponding AppScan® Source user account must also then be created manually post-installation with AppScan Source for Analysis or the AppScan Source command line interface (CLI). This topic describes creating this account using AppScan Source for Analysis.
- Auditing user activity
  AppScan® Source offers a convenient location for auditing user activity. The Audit view logs events such as authentication to the AppScan Enterprise Server, the creation of new users, and the creation of new rules in the database.
- 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. All user management occurs in AppScan Enterprise.
- LDAP integration
  To add an AppScan® Source user that will be authenticated via LDAP, you must have configured the AppScan Enterprise Server user repository to use an LDAP repository.
- Registering applications and projects for publishing to AppScan® Source
- AppScan® Source application and project files
  AppScan® Source applications and projects have corresponding files that maintain configuration information required for scanning, as well as triage customization. It is recommended that these files reside in the same directory as the source code, since configuration information (dependencies, compiler options, and so forth) required to build the projects is very similar to that required for AppScan Source to scan them successfully. Best practice includes managing these files with your source control system.
- Port configuration
Developing
Learn how to develop by using the product.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.
Troubleshooting and support
There are a number of self-help information resources and tools to help you troubleshoot problems.

AppScan® Enterprise Server authentication: Migration considerations for replacement of the IBM® Rational® Jazz™ user authentication component with IBM® WebSphere® Liberty

This topic describes user management-related migration considerations that you may need to consider if you are upgrading from a previous version of AppScan® Enterprise Server.

Migrating from an Enterprise Server that only has local Jazz™ users: In this upgrade scenario, the former Jazz™ users will appear in the AppScan® Source Database as AppScan® Enterprise Server users, however, they will not be valid. These users can be removed from the Database - or they can be converted to AppScan® Source users. Contact HCL Support for information on enabling former Jazz users in AppScan® Source.
Migrating from an Enterprise Server that was configured with LDAP: During the Enterprise Server upgrade, you have the option of configuring the Enterprise Server with LDAP again. If you do this, existing users will still work in AppScan® Source.
Migrating from an Enterprise Server that was configured with Windows™ authentication: If your Enterprise Server was configured with Windows™ authentication, existing users will work in AppScan® Source, provided the new Enterprise Server Liberty is configured to use Windows™ authentication.

Note: When you migrate from an Enterprise Server that was configured with LDAP or Windows™ authentication, the existing users will be reassigned with the default permissions that are assigned to AppScan® Enterprise Server users. These default permissions are described in Configuring automatic login of AppScan Enterprise Server users.