Resolution | This feature is controlled by requiring the use of separate device definition files during token provisioning. We are restricting access to this feature by controlling the availability of the device definition files. This allows us to know the effect of the new feature on end users. Contact RSA customer support to request the files.
- Contact RSA customer support and reference knowledge article 000038035.
- Obtain the Android-2.3.x-swtd.xml and/or iOS-2.4.x-swtd.xml from support.
- Create software token profiles, and import the device definition files into the RSA Authentication Manager primary:
- Log in the Security Console using super admin credentials.
- Browse Authentication > Software Token Profiles > Add New.
- Create a name for the new profile.
- Click Import New Device Definition File.
- Click Choose File to browse to the definition file then click Submit.
- 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),
- Compressed Token Format (CTF), or
- File-based provisioning.
- Click Save when done.
- Distribute the software token using this new software token profile:
- In the Security Console, click Authentication > SecurID Tokens > Manage Existing.
- Use the search fields to find the software token that you want to distribute.
- Click the token serial number, and choose Distribute.
- Select the software token profile that was created in Step 1b and 1c.
- Click Save and Distribute.
- Provide the software token to the end user.
- Import the software token on the Android or iOS phone.
|