AnsweredAssumed Answered

RSA SecurID token not recognized by custom app after update

Question asked by RSA Admin Employee on Mar 18, 2014
Latest reply on Mar 24, 2014 by RSA Admin

Hi all, my app uses the RSA library to install SecurID token, and generates token code for validation against the RSA server, only after token code validated successfully we let user proceed and login to the app. The first version of the app was released last year and available in the Apple B2B App Store. A new version was released recently and it is not able to recognize the token that was previously installed with the old app. If users install new tokens then they can proceed with the new app, but majority of our users do not have the permission to install token. The person who has the permission needs to handle this manually which is not easy to do as there are many devices already deployed.


Our server log shows that the device identifier generated using the Apple device API identifierForVendor has been changed during the update. Not sure if this is related to the issue.


Other environment/setting changes done in the new version of our app was:

1. New code built with Xcode5 and iOS 7 library (old version was built with Xcode4 and iOS 6 library)

2. Provisioning profile used during development was changed