Previous Topic: Honor-Based LicensingNext Topic: DevTest Solutions Usage Audit Report


How Licensing, ACLs, and Audit Reports Work Together

The topic includes:

Usage-Based License Agreement

Your license agreement with CA Technologies is based on the maximum number of concurrent user sessions by user type. User types are:

Each activity a user can perform with DevTest Solutions has a corresponding permission. Each permission is associated with a role; each role is associated with one of the user types. Administrators assign permissions to users.

License Activation

License activation for DevTest Solutions is file-based. CA Technologies provides you with a license file (devtestlic.xml). During installation or upgrade of DevTest Solutions, the Setup wizard puts the file in the LISA_HOME directory on the host where the Enterprise Dashboard is installed. Subsequent installations of the Server component (DevTest Server) reference the URL of the Enterprise Dashboard. License activation occurs the first time you start the Enterprise Dashboard and the registries. No other component requires license activation.

If you are upgrading, request a new devtestlic.xml license from CA Technologies. The current license key generation process is leveraged to generate a product key delivered via the devtestlic.xml file. This key is used to activate or unlock the Enterprise Dashboard.

ACL Activation

Access Control (ACL) is enabled by default. Before users can access DevTest Solutions, they must be authenticated with valid credentials and then authorized to perform the tasks associated with their role. Using the Administration tab on the Server Console, you define for each user a user name, a password, and a role that is composed of a set of permissions. Roles are tied to user types.

Users must log in with valid credentials to access any UI (User Interface) or CLI (Command Line Interface). When a user opens the Workstation, browses to the Portal, or browses to the DevTest Console, a logon dialog is presented. The user logs in with the credentials defined in DevTest or in LDAP, if you have configured DevTest to use LDAP credentials. If the entered credentials match that of an authorized user, the UI opens. The features that are presented to the user are based on the permissions you grant to that user.

For backward compatibility, one exception exists. Although ACL is enabled, authorized users can run tests and start virtual services without specifying a valid login user name and password.

Note: We recommend that you change the passwords for the standard users to ensure that only authenticated users gain access to DevTest Solutions.

Honor-based Compliance

The customer is responsible for license compliance with the terms of contract. The license issued does not enforce the maximum concurrency by user type. As outlined in the Usage Audit Report section, DevTest Solutions Usage Audit Reports are sent to CA Technologies upon request. The CA account manager may contact you to assess your interest in expanding your purchase agreement if the Audit Reports indicate concurrent usage of a user type that exceeds the agreement.

Customers who wish to evaluate functionality that has not been purchased should contact their Account Team to discuss a Proof of Concept trial, or to address questions about the new functionality. Any Support cases raised for product functionality that has not been purchased are treated as "Out of Scope".

Continuous Collection of Usage Data by User Type

When users log in to a DevTest Solutions UI or CLI, each registry captures session data by user type and forwards it to the Enterprise Dashboard at the top of each hour. If connectivity between the registries and the Enterprise Dashboard is lost, the usage audit data accumulates on the registries until connectivity is re-established. The Enterprise Dashboard compiles usage data from across the enterprise to count concurrent sessions by user type.

Usage Audit Report

Periodically, an administrator logs onto the Enterprise Dashboard and generates the Usage Audit Report for a specified time period. Data from the specific UI or CLI users log into is reported. The concurrent sessions with the maximum number of users of a given user type are used in the report calculations. The report details concurrent usage counts by user type across registries. For each user type with data, the report generator creates a tab with drill-down details. The access detailed in the Audit Reports can be compared to the license agreement to determine the level of compliance. You can evaluate this report in light of your license agreement to verify compliance or to see if you want to upgrade your contract.