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
Configure Access Restrictions for an Existing Agent 8Number of Views After changing RSA Authentication Manager 8.X virtual host information CT-KIP token provisioning fails. 121Number of Views Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. 27Number 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 RSA Identity Governance and Lifecycle accounts linked to identities based on key identity attributes do not unlink when th… 30Number 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?