Importing a token via CT-KIP fails indicating that the token already exists
Originally Published: 2021-05-19
Last Modified: 2022-06-20
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
How to troubleshoot CT-KIP failures in Authentication Manager 8.x 187Number of Views RSA SecurID token import via CT-KIP URL does not work using Authentication Manager Bulk Admin 1.6 on Authenitcation Manage… 67Number of Views Troubleshooting RSA SecurID Software Token for BlackBerry deployment by CT-KIP 593Number of Views Token import fails on desktop using CT-KIP via Group policy 169Number of Views IWA RSA connector server shows wrong certificate when connecting to it through browser with error : Invalid Request 3Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?