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
Hide User Details Columns on HDAP for AM Prime Number of Views Support the use of OAuth 2.0 tokens for the RSA Identity Governance & Lifecycle Web Service API Number of Views Are security objects cached like keys are? Number of Views A user registered through Activation On the Fly and would like to change the login name the system generated and the defau… Number of Views Would like to allow access to a 'backup' account that can read the encrypted files (not decrypt them) and archive that to … Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
