This feature is controlled by requiring the use of separate device definition files during token provisioning.

1. RSA released definition files publicly for administrators to adopt this feature. 
2. Obtain the Android-2.3.x-swtd.xml and/or iOS-2.4.x-swtd.xml  from RSALink Portal.
3. Create software token profiles, and import the device definition files into the RSA Authentication Manager primary:     
   1. Log in the Security Console using super admin credentials.
   2. Browse Authentication > Software Token Profiles > Add New.
   3. Create a name for the new profile.
   4. Click Import New Device Definition File.
   5. Click Choose File to browse to the definition file then click Submit.
   6. Select the Delivery Method. You can distribute the software token file in one of three ways:

• Dynamic Seed Provisioning (CT-KIP URL or QR code), 
• File-based provisioning.         

4. Distribute the software token using this new software token profile:
   1. In the Security Console, click Authentication > SecurID Tokens > Manage Existing.
   2. Use the search fields to find the software token that you want to distribute.
   3. Click the token serial number, and choose Distribute.
   4. Select the software token profile that was created in Step 3b and 3c.
   5. Click Save and Distribute.
   6. Provide the software token to the end user.
   7. Import the software token on the Android or iOS phone.