Can RSA provide an .xml file for “import new device definition file” in which we can define device type name to include our company name so that this new name displays in the drop-down menu for device types?
Download Software Token Device Definition Type (.swtd) files to be customized.
Edit the file to change Device and Token names, and any other changes or defaults needed.
Import this new Software Token Device Definition Type (.swtd) file into the Security Console for use with a Software Token Profile.
Step 1 is to Download Software Token Device Definition Type (.swtd) files to be customized from RSA Link - Go to SecurID Access Downloads and check the Device Type needed, e.g. Android, iPhone, Windows Desktop, etc...
Each Device Type has a link to download the software token application and a second link to download the Software Token Device Definition Type (.swtd) file for that Device, usually at the bottom of the Page.
Step 2 is to Edit the file to change Device and Token names, and any other changes or defaults needed. NotePad++ will retain the .xml format. You can edit field such as:
To add your company name, in this example ACME, or to even change the version number that is displayed or any of the Description fields.
Some fields have default values, <DefaultValue> as well as a Description, </Description>, which can be changed. Be careful and fully test any changes made here.
Step 3 is to Import this new Software Token Device Definition Type (.swtd) file into the Security Console for use with a Software Token Profile. This is done in the Security Console.
Since the swtd files are not digitally signed, they can be edited, but caution should be exercised in any changes that are made to these definition files. Description fields pose very little to no risk. Other fields like <TokenName>, <TokenFamily> and <TokenVersion>have been successfully changed and used to distribute a software token file imported into a Windows Desktop Software token application, which successfully authenticated a user. But extensive QE testing has not been performed, therefore there could be some additional risk of this not working. However, those risks should be easily identified after initial testing for a user. This solution is provided as-is, it should work fine, but we are not implying it is a supported feature or Authentication Manager.