Step by Step, setup AM8.1 Admin SDK Environment in Eclipse
Version 2 (2015/09/17)
1. Download Java SDK, install. (Java 6 and above)
http://www.oracle.com/technetwork/java/javaee/downloads/index.html
2. Download Eclipse, install.
http://www.eclipse.org/downloads/
3. Export server root certificate, import it to Client JKS
1> cd /opt/rsa/am/appserver/jdk/jre/bin
2> ./keytool -export -keystore /opt/rsa/am/server/security/trust.jks -file am_root.cer -alias rsa-am-ca (no password)
3> Download "am_root.cer". Basically the location to put the file is not restricted. For me, I just put it in the JRE bin folder.
4> Alternatively, we can export the certificate via Internet Explorer.
5> Import "am_root.cer" to local JKS. The location for local JSK is not restricted as well.
( I just put it in the SDK\lib\java. )
keytool -import -keystore "<SDK> \lib\java\trust.jks" -storepass cacerts_keystore_password -file am_root.cer -alias rsa_am_ca -trustcacerts
4. Replace Java Cryptography Extension Unlimited Strength Jurisdiction Policy Files
1> Download the file here: (For difference version JDK please download different version of JCE files accordingly)
http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html
2> Replace the existing ones in JRE/lib/security/
5. Setup SDK(sample project) in Eclipse
1> Create a new Project
2> Create from a "build.xml" file
3> Configure Build Path
4> Add external Libraries, add all libs under SDK/lib/java
5> Import "config.properties"
6> Edit "config.properties"
1> In the ssh console issue:
rsaadmin@marge:/opt/rsa/am/utils> ./rsautil manage-secrets --action list
2> In the eclipse edit the "config.propertites"
( If it’s for web service please also change)
7> Modify launch parameters
-Dweblogic.security.SSL.trustedCAKeyStore="<JKS>" (Please use quote if there’s space in the file path)
-Dbea.home="<your SDK home>\sdk\lib\java"
-Dsun.lang.ClassLoader.allowArraySyntax=true
8> Test the code.
Related Articles
enVision: how to specify just one collector using lsdata 48Number of Views Deployment of the aveksa.ear in a clustered environment fails with 305000 ms timeout error in RSA Identity Governance & Li… 212Number of Views Changing the Environment Name in one system causes a change in another environment in RSA Identity Governance and Lifecycle 7Number of Views Old connector Log4j files not removed in RSA Governance & Lifecycle 49Number of Views How to exclude RSA Authentication Manager 8.x from picking up disabled user account data from the Microsoft LDAP directory 160Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x