Token import fails on desktop using CT-KIP via Group policy
2 years ago
Originally Published: 2011-09-30
Article Number
000042670
Applies To
Software token 4.1 for Desktop
Activation code expiration time
Issue
Token import fails on desktop using CT-KIP via Group policy
Is there any expiration time for Activation code?
Administrator has created CT-KIP URL for automatic downloading tokens on Software token for Desktop. If the user imports the token it works as expected.
Some users did not launch software token for Desktop for more than two weeks. Token import fails if the URL is not used within certain timeframe.
Resolution

The activation code or CT-KIP URL do not have any expiration time. The token import can fail due to any other reason and needs to be investigated further like any other token import failure.  See How to enable debug logging on the RSA Software Token?Enable debugging on Software token

Location of debug log file:

Standard Installation:

C:\Documents and Settings\<Login name>\Application Data\RSA\RSA_Software_Token_Log.txt  

If installation is done using SingleDatabase option:

C:\Documents and Settings\All Users\Application Data\RSA\RSA_Software_Token_Log.txt  

On Vista machine, click on Organize, then select folder options select "show all hidden files"  A folder will appear in C:\Program_data\RSA\Logfiles. The debug file RSA_Software_Token_Log.txt will be located in that folder.

 

 


Workaround
The above observations give us an impression that "Activation Code" may have some expiration time. The CT-KIP URL does not work after some time.
Don't see what you're looking for?