How do you import file based tokens on a mobile device for Android and IOS
First, ensure that your end user has the RSA SecurID Software Token for Android or RSA SecurID Software Token for iOS installed on their device. Also make sure that your software tokens have been imported into Authentication Manager and that you have configured a software token profile where the delivery method is defined as File Based (SDTID).
In the Security Console, click Help and search for Assign and Distribute a Software Token to a User Using File-Based Distribution in the User Dashboard.
When issuing tokens via SDTID you must protect them. The first line of defense it to set the device binding ID. The end-user must provide this value from their device, typically via an email. The binding ID is entered into the DeviceID section during the token distribution. A good trick is to set up the profile with a default Device Serial set with a text notification similar to: "Enter user's deviceID here"
Once entered, the token can be distributed. The admin will need to save it to their desktop and emailed to the end user.
It's strongly recommended SDTID be abandoned and CTKIP used instead to distribute tokens. SDTID files are provided for backward compatibility.
To deliver a token, you send an email with an SDTID file attachment to the emailclient on the Android device.
Retrieving data ...