After changing RSA Authentication Manager 8.X virtual host information CT-KIP token provisioning fails.
Originally Published: 2014-06-04
Last Modified: 2023-10-06
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
RSA SecurID token import via CT-KIP URL does not work using Authentication Manager Bulk Admin 1.6 on Authenitcation Manage… Number of Views RSA Authentication Manager 7.1 to 8.1 - Upgrading an Existing Hardware Appliance 3.0 Number of Views Token import fails on desktop using CT-KIP via Group policy Number of Views How to troubleshoot CT-KIP failures in Authentication Manager 8.x Number of Views Troubleshooting RSA SecurID Software Token for BlackBerry deployment by CT-KIP Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
