Following notes are basic explanations of RSA ACE/Server Licensing:

Enforcement of License Limits

RSA ACE/Server 5.1, 5.2, & Authentication Manager 6.0.x & 6.1.x software enforces the ACE/Server license limits both during installation and in the normal course of daily operation and administration.
 

License Enforcement During Installation

Whether you are upgrading from an older version of RSA ACE/Server or performing a new installation, you must specify the location of your license file (license.rec). This can be a Version 3 (pre-5.1 format) or Version 4 (5.1, 5.2, & 6.0) or Version 5 (6.1) license file on the original diskette or copied to a hard drive location. If you are upgrading from a previous version of RSA ACE/Server, the setup program checks to see that your current installation is valid under the terms of your current license. If the database exceeds the licensed number of active users or Replica Servers, the upgrade places your RSA ACE/Server in upgrade violation mode. Upgrade violation mode effectively turns your license into a 90-day temporary license. When your license expires, it goes into violation mode, meaning you are prevented from activating additional users and/or adding new Replicas. You must bring your RSA ACE/Server 5.2 or 6.x into compliance within 90 days by doing one of the following:

• ?      Removing Replicas or reducing the number of active users, depending on your upgrade violation
• ?       Purchasing a new license from RSA Security To purchase a new license, contact your RSA Security sales representative or local distributor, or go to http://www.rsasecurity.com/contact/upgrades.html

License Enforcement During Daily Operation and Administration

During normal RSA Authentication Manager administration, a valid license can go into violation mode. Periodically, the RSA AM checks for license compliance. For example, you activate more users than your license allows, RSA AM detects this and displays a warning message:

There are too many active users in the database/ Number of active users in the database exceeds license limit / Number of active users in the database reached license limit.

When your license is in violation mode, you cannot activate additional users and/or add new Replicas. You must bring your RSA ACE/Server 5.2 or 6.x into compliance right away by doing one of the following:

• ?      Removing Replicas or reducing the number of active users, depending on your upgrade violation
• ?      Purchasing a new license from RSA Security

To purchase a new license, contact your RSA Security sales representative or local distributor, or go to http://www.rsasecurity.com/contact/upgrades

Active Users
 

An active user is the basis of all ACE/Server licensing one active users uses one license unit and is defined as:

• ?      A user record in the RSA ACE/Server database that has some authentication method assigned, regardless of token status.
• ?      Up to three authenticators (any combination of our various token types and / or a user password) assigned to him or her

            For example, a user who has two assigned tokens and one assigned user password counts as one active user. A user who is listed in the RSA ACE/Server database but does not have an assigned token or user password is not an active user.
 

Note:A user who has an disabled, expired, or lost token assigned, counts as an active user. For information about how to unassign an expired token, see the Help button on the Edit User page in Database Administration Host or Remote Mode..

License active user limit being approached

When you exceed the limits of your license, you will be in violation mode. Violation mode occurs under either of the following circumstances:

? You have installed a new RSA Authentication Manager and have exceeded your license limits.

? Your license was in upgrade violation mode and is now in violation mode.

When your license is in violation mode, you cannot activate additional users. When you exceed the limits of your license, to bring your system back into compliance, contact RSA Security to obtain a new license. Alternatively, you can deactivate a sufficient number of users to bring your system back into compliance.