How to point AM Prime server to different RSA Authentication Manager
3 years ago
Originally Published: 2021-07-12
Article Number
000064682
Applies To
RSA Product Set: RSA SecurID
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
Customer would like to reconfigure the AMIS,SSP and HDAP servers to point to the new RSA primary.
Resolution
Here are the steps for pointing AMIS to a different RSA Authentication Manager.
  1. Generate new sdconf.rec from the new AM instance and copy it file to ../primekit/configs/amis/auth/ directory
  2. Optionally delete the node secret from both the AM server and the AMIS server (../primekit/configs/amis/auth/securid)
  3. 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)
  4. Delete contactlist.xml (../primekit/configs/amis)
  5. 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'"
 
  1. Restart AMIS. No changes in HDAP/SSP

Related Articles

Trending Articles

Don't see what you're looking for?