000017552 - User is unable to import the converted CTF string token or CT-kip token into new RSA iOS application v 2.0.0

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000017552
IssueCustomer converted the SDTID file to CTF string using a token converter.
Token import fails.
Customer recently upgraded from RSA application from ver 1.3 to 2.0 in their iPhone.
Customer is using device definition file for ver 1.3.
CauseWith new version of application, customers need to use newer version of token converter to get the right CTF string.
ResolutionDownload the Token Converter 3.1(link below ) to generate the CTF string for newer version of the iOS application.

Refer to the documentation on how to use the token converter 3.1.

The token converter 3.1 is backward compatible. If you want to generate the CTF string for iOS application 1.3, -v 2 is required, because the iOS 1.3 app only supports legacy format CTF strings.
java -jar TokenConverter.jar c:\tmp\user2-passwordtoken.sdtid -ios -p t0kenpw1 -o c:\tmp\tokenfile.txt -v 2
Download the new device defintion file from the emc website for iOS application 2.x.
Workaround: If your CTF string URL has .iphone in it, just remove and resend it to your user.

Change com.rsa.securid.iphone://ctf?ctfData=200002068164720663136011170432774461076477164632456201026172115044046062716712650
to com.rsa.securid://ctf?ctfData=200002068164720663136011170432774461076477164632456201026172115044046062716712650
Workaround : New version of token applications support SDTID file based token import. Use file based token distribution to import the token into the RSA application.
NotesSeeUser is unable to import the converted CTF string token into new RSA iOS Software Token 2.0.0 for additional information.
Legacy Article IDa66550