After changing RSA Authentication Manager 8.X virtual host information CT-KIP token provisioning fails.
Originally Published: 2014-06-04
Article Number
Applies To
RSA Authentication Manager 8.1
Virtual Host
CT-KIP
Issue
After changing the virtual host name (Deployment Configuration > Virtual Host and Load Balancing) the CT-KIP Activation URL still shows the old virtual hostname.
Cause
Resolution
To resolve this:
Login to the primary Security Console and select Setup > System Settings. Click the Tokens link. Update the Dynamic Seed Provisioning Configuration section to have the updated FQDN then click Save.
Related Articles
Steps to change the RSA Authentication API 8.x Output Return Statements in the Sample Code 17Number of Views AFX Server fails to start with java.lang.StackOverflowError errors in the log files after changing the application server … 678Number of Views Guide to Microsoft Active Directory LDAP synchronization with RSA Authentication Manager 310Number of Views RSA SecurID Desktop Token 5.0.2 for Windows Administrator's Guide 275Number of Views RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide 785Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager 8.9 Setup and Configuration Guide Using Vault instead of cleartext password in WildFly configuration file in RSA Identity Governance & Lifecycle Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update
Don't see what you're looking for?