Installing and configuring the Java Admin API

Locate the RSA Authentication Manager 7.1 SDK.

Copy files required to run the client to the <SDK_HOME>\lib\java directory, where <SDK_HOME> is the home directory of the RSA Authentication Manager 7.1 SDK.

1. From a command prompt on your Authentication Manager server, change directories to <RSA_AM_HOME>\appserver\weblogic\server\lib\, where <RSA_AM_HOME> is the directory in which you installed RSA Authentication Manager 7.1/8.2.

2. Type:

   java -jar ..\..\..\modules\com.bea.core.jarbuilder_1.0.0.0.jar -profile wlfullclient

    

3. Copy the following files from your Authentication Manager server installation directories to the <SDK_HOME>\lib\java directory:

   RSA_AM_HOME\appserver\license.bea

   RSA_AM_HOME\appserver\modules\com.bea.core.process_5.3.0.0.jar

   RSA_AM_HOME\appserver\weblogic\server\lib\wlfullclient.jar

   RSA_AM_HOME\appserver\weblogic\server\lib\wlcipher.jar

   RSA_AM_HOME\appserver\weblogic\server\lib\EccpressoAsn1.jar

   RSA_AM_HOME\appserver\weblogic\server\lib\EccpressoCore.jar

   RSA_AM_HOME\appserver\weblogic\server\lib\EccpressoJcae.jar

Ensure that the following files are located within the SDK installation directory, for example, in this location:

C:\rsa.sdk

SDK_HOME\lib\java\axis-1.3.jar;

SDK_HOME\lib\java\commons-beanutils-1.7.0.jar;

SDK_HOME\lib\java\commons-discovery-0.2.jar;

SDK_HOME\lib\java\commons-lang-2.2.jar;

SDK_HOME\lib\java\commons-logging-1.0.4.jar;

SDK_HOME\lib\java\iScreen-1-1-0rsa-2.jar;

SDK_HOME\lib\java\iScreen-ognl-1-1-0rsa-2.jar;

SDK_HOME\lib\java\ims-client.jar;

SDK_HOME\lib\java\jdom-1.0.jar;

SDK_HOME\lib\java\jsafe-3.6.jar;

SDK_HOME\lib\java\jsafeJCE-3.6.jar;

SDK_HOME\lib\java\log4j-1.2.11rsa-3.jar;

SDK_HOME\lib\java\ognl-2.6.7.jar;

SDK_HOME\lib\java\spring-2.0.7.jar;

SDK_HOME\lib\java\systemfields-o.jar;

SDK_HOME\lib\java\ucm-client.jar;

SDK_HOME\lib\java\wlfullclient.jar;

SDK_HOME\lib\java\com.bea.core.process_5.3.0.0.jar

SDK_HOME\lib\java\am-client.jar

This .jar file will be located in the Bravura Security agent directory:

<Bravura Security agent dir>\agtrsaam.jar

The Bravura Security agent directory is:

<Program Files path>\Bravura Security\Bravura Security Fabric\<instance>\ agent

or

<Program Files path>\Bravura Security\Connector Packs\global\ agent

The SDK installation directory will be used when configuring the RSA Authentication Manager 7.1/8.2 target system address.

Copy the updated am-client.jar file from the Authentication Manager server to the <SDK_HOME>\lib\java directory on the Bravura Security Fabric server.

Copy the RSA Authentication Manager 8.x SDK (Java Admin API) to the Bravura Security Fabric server. The RSA Authentication Manager SDK can be obtained from the RSA Link Community web site within the am-8.0-SDK.zip and am-8.1-SDK.zip files or in the RSA Authentication Manager 8.x Extras zip files available from Download Central.

The set of .jar files for the SDK can be found within the lib\java directory.

Copy files required to run the client to the <SDK_HOME>\lib\java directory, where <SDK_HOME> is the home directory of the RSA Authentication Manager 8.x SDK.

The <SDK_HOME> SDK installation directory will be used when configuring the RSA Authentication Manager 7.1/8.2 target system address.

Connect to your RSA Authentication Manager server virtual appliance using an SCP or SSH client.

Navigate to the <RSA_AM_HOME>/utils directory and enter the following command:

rsautil manage-secrets --action list

Enter the RSA Authentication Manager super user’s master password when you are prompted.

The system will display a list of internal system credentials.

Locate the command client user name and password in the list of credentials, and copy them for later use. For example:

  Command Client User Name .................: CmdClient_1dckyzfx 
  Command Client User Password .............: e9SHbK0W4i

Import the Server Root Certificate.

RSA Authentication Manager 7.1 stores a self-signed root certificate in:

RSA_AM_HOME\server\security\server_name.jks. You must export the root certificate out of that file, copy the export file to the Bravura Security Fabric server, and then finally import it into the keystore of the Bravura Security Fabric server.

See "Importing the Server Root Certificate" in the "RSA Authentication Manager 7.1 Developer’s Guide" for details.

Copy the license.bea file from RSA_AM_HOME\appserver\ to the <SDK_HOME> directory.

Generate the Server Root Certificate:

1. Open Internet Explorer using the "Run as administrator" option.

2. Browse to the web address for the SSL port of the RSA Authentication Manager 8.x server; for example: https://<servername>:7002

   A 404 not found web page opens.

3. Right click anywhere on the page and select Properties to open the page’s properties dialog box.

4. Click Certificates to open the certificate dialog box.

5. Click the Certification Path tab, select the tree’s root certification path, and then click View Certificate.

   The RSA Authentication Manager server’s root certificate dialog box will open.

6. Click the Details tab and then the Copy to File button.

   Windows will open the Certificate Export Wizard.

7. Click the Next button on the Welcome page.

8. Select the DER encoded binary X.509 (.CER) radio button for the format on the Export File Format page and click the Next button.

9. Save the certificate file to a location on the Bravura Security Fabric server.

Once you have the server root certificate file, you must import it into the keystore of the Bravura Security Fabric server.

Change directories to <JAVA_HOME>/jre/bin and execute the following sample command to import the certificate file:

keytool.exe -import -keystore <RSA_SDK_HOME>/lib/java/trust.jks 
  -storepass <CACERTS_KEYSTORE_PWD> -file <RSA_AM_ROOT_CERT> 
  -alias rsa_am_ca -trustcacerts

See "Importing the Server Root Certificate" in the "RSA Authentication Manager 8.0, 8.1, or 8.2 Developer’s Guide" for details.

If the ssl certificate has changed on the RSA Authentication Manager 7.1/8.2 server, a new server root certificate file will need to be generated and then imported again to create a new trust.jks certificate keystore file.