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
Mitigator Memory Increasing Daily in RSA Web Threat Detection 5.1 Number of Views Linux commands used to manage RSA Identity Governance & Lifecycle services Number of Views Change the Hostname of a Primary or Replica Instance in Azure Number of Views Is it possible to migrate an existing KCA 4.5.x installation on a Windows NT machine to a Windows 2000 machine? Number of Views Services will not start after changing IP address of RSA Authentication Manager 8.x from command line Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
