The Access Manager 7.1 documentation is available in the following collection:
SecurID has been converted to a Java-based authentication module and is supported on the following platforms:
Solaris SPARC and x86 systems beginning with Access Manager 7.1 patch 2 (CR 6621802).
Linux systems beginning with Access Manager 7.1 patch 3 (CR 6767780).
Previously, you had to start the SecurID authentication process (amsecuridd) manually. Now, the SecurID authentication process runs similar to the other authentication modules, fully-contained within the Access Manager 7.1 server process.
The Java version of SecurID requires the following files:
authapi.jar (SecurID API) in the following directory:
WAR file deployment: WEB-INF/lib directory
Installer (package-based) deployment: AccessManager-base/SUNWam/lib
log4j.properties, rsa_api.properties, and sdconf.rec files in the default /opt/ace/data directory.
To configure a SecurID authentication module:
Log in to the Access Manager 7.1 Administration console.
Under Access Control, click realm-name and then Authentication.
Under Module Instances, click New and add a New Module Instance with Type as SecurID.
Configure the following SecurID Realm Attributes:
ACE/Server Configuration Path. Default is /opt/ace/data.
Helper Configuration Port. Default is 58943.
Helper Authentication Port. Default is 57943.
Authentication Level. Default is 0 (zero).
Save your configuration and log out of the console.
Restart the Access Manager web container.
A new document entitled Chapter 1, Technical Note: Deploying Access Manager Instances to an Application Server Cluster, in Technical Note: Deploying Access Manager to an Application Server Cluster has been added to the Access Manager 7 2005Q4 collection.
The Sun Java System Access Manager Policy Agent 2.2 collection has also been revised to document new agents: