Importing a token via CT-KIP fails indicating that the token already exists
Originally Published: 2021-05-19
Article Number
Applies To
RSA Product: RSA Software Token for iPhone
RSA Product: RSA Software Token for Android
Version: 2.6
Issue
The token import fails to indicate that the token already exists. RSA token application should not check for a duplicate token prior to importing the token. The reason for this, once a CT-KIP URL is generated for token distribution, it creates a new seed in the database and the existing token becomes unusable.
Cause
Resolution
Old RSA Software Token Application RSA Software Token 3.0
Related Articles
Configure Access Restrictions for an Existing Agent 8Number of Views RSA Authentication Manager 7.1 to 8.1 - Upgrading an Existing Hardware Appliance 3.0 63Number of Views Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. 27Number of Views RSA SecurID token import via CT-KIP URL does not work using Authentication Manager Bulk Admin 1.6 on Authenitcation Manage… 66Number of Views How to access RSA Registration Manager enrollment page without being warned that the site is not trusted (even through the… 9Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update Authentication Manager How to Retrieve the LDAPS Certificate and Configure an External Identity Source to Use LDAPS
Don't see what you're looking for?