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 Number of Views RSA SecurID Desktop Token 5.0.2 for Windows Administrator's Guide Number of Views AFX Server fails to start with java.lang.StackOverflowError errors in the log files after changing the application server … Number of Views Authentications failing after changing the directory password for the Directory User ID in the Identity Source Configurati… Number of Views RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide Number of Views
Trending Articles
How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme… Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to import CA signed console cert from AM 8.x primary into a new primary with same FQDN How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings.
Don't see what you're looking for?
