SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
New Contributor
New Contributor

Explanation for RSA AM SW Token Profiles for Desktop



I've a question about RSA AM 8.4 Software Token Profile. I can't find a meaningful documentation about the offered list of desktop Software Token Profile when i am in the <Add Software Token Profile> window, and when to use which of them.

The offered list contains following Profiles for Desktop:

Desktop PC 4.0 / Dekstop PC 4.x / Desktop PC 5.x / Desktop PC SID 64-bit 3.0.x / Desktop PC with Automation 4.x / Desktop PC with Automation 5.x / (Passcode) Desktop PC AES 128-bit 3.0.x / (Tokencode Only) Desktop PC AES 128-bit 3.0.x

So is there such a documentation where i can see which kind of Profile for Desktop is the appropriate to use, what's the difference between them, why are so many profiles for Desktop


Kind regards


1 Reply

The difference is mainly the Device Type that is pre-filled in the field, and delivery formats that will work on that particular app.. You can pick a profile that matches the target software token app Device Type, or hand type the Serial, or blank it, or use any profile and hand write your long as it matches something seen on the token app itself:




It is mainly about categorizing for reporting: How many tokens are distributed to what version of RSA token app, but the functionality of the token itself is the same across all versions (6-8 digit, pin type, interval...). 


Also, profiles prevent you from picking delivery options that do not work, for example CTF or QR won't work...but you could pick an Android profile and choose .sdtid and it would load on RSA software token for windows as long as the serial number or type was also accurate. You could pick Android CTKIP as well, but you'd have to hand-change the CTKIP URL to fit the URL type the RSA software token app for windows understands....