How to point AM Prime server to different RSA Authentication Manager
Originally Published: 2021-07-12
Article Number
Applies To
RSA Product/Service Type: Packaged Custom Application
RSA Version/Condition: SID Access Prime
Platform: Linux
Platform (Other): Linux
O/S Version: SUSE Linux 12
Product Name: null
Product Description: null
Issue
Resolution
- Generate new sdconf.rec from the new AM instance and copy it file to ../primekit/configs/amis/auth/ directory
- Optionally delete the node secret from both the AM server and the AMIS server (../primekit/configs/amis/auth/securid)
- Import the new AM 8’s API Root CA certificate to ../primekit/certificates/truststore.jks (This step wouldn’t hurt even if the truststore.jks already contains the AM 8 root CA)
- Delete contactlist.xml (../primekit/configs/amis)
- Modify the below entry in setenv.sh or config.sh (../primekit/configs/amis/tomcat-amis) with appropriate AM server’s hostname or IP address
export CATALINA_OPTS="$CATALINA_OPTS '-Dam.server=10.208.195.196'"
- Restart AMIS. No changes in HDAP/SSP
Related Articles
Are security objects cached like keys are? Number of Views Enable verbose logging for Operations Console backups for RSA Authentication Manager 8.x Number of Views Support the use of OAuth 2.0 tokens for the RSA Identity Governance & Lifecycle Web Service API Number of Views How to obtain the newer version of database public schema? Number of Views Would like to get the original URL accessed by the user after they have authenticated to Access Manager Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
