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
SQL Server data collectors in RSA Identity Governance & Lifecycle periodically fail with connection timed out errors 168Number of Views Error when importing wildcard certificates to RSA Authentication Manager 8.x 516Number of Views Troubleshooting RSA SecurID Software Token for BlackBerry deployment by CT-KIP 583Number of Views Workflow REST Web Service node returns "RSA002 : Invalid Configuration" message in RSA Identity Governance & Lifecycle 84Number of Views Token import fails on desktop using CT-KIP via Group policy 165Number of Views
Trending Articles
An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process
Don't see what you're looking for?