Generate QR codes for multiple device types

[EdHumes]

We've been deploying new soft tokens to user through either an STID file or with the CT-KIP method and the self-help console. While that is working for small groups of people at a time it is much more manual and labor intensive than we'd like since we first have to determine if the user has an android or IOS device. This does not bode well for an upcoming expiration of about 800 hardware tokens.

It appears that all of the methods including CTF require the administrator to know either the type of device or even the serial number. Is there a method where we can generate these regardless of what type of mobile device the recipient has?

[Michiel]

Have you already tried scanning an 'android code' on an iOS device (or vice versa)? To be honest, I haven't tried myself either, but I assume there would be a difference as otherwise that switch for the command line utility would have been obsolete? Just a guess! Curious to your findings

[JaneDing]

When creating a token profile, you can select Generic AES 128. It can be used on all kinds of devices/platform including ios, android, desktop, etc. But only file based and CT-KIP delivery methods are available under Generic AES 128, because only these 2 methods are applicable to all devices/platform.

[JamesNichols]

This does not work. We created a new soft token profile with Generic AES 128 selected to go along with the file-based method and could not distribute the file to a iOS Phone and Windows Desktop client to work together as one license.

[StevenSpicer]

"self-help console" - do you mean the Self Service Console (SSC) built into Authentication Manager?  Have you created software token profiles for each of iOS, Android and Windows, and enabled them in the SSC?  The end user should be able to select the correct type.

[JamesNichols]

No. simply assigning a single license to a user with a windows desktop and cell phone consuming only one rsa license.

[StevenSpicer]

That DOES only consume one license. It uses two tokens, but only one license.

[JamesNichols]

we could not get that feature to work with assigning/distributing a single soft token profile to multiple devices configured with Generic AES 128, and Issued the token as an .sdtid token file. The rsa link below does not provide much information.

https://community.rsa.com/t5/securid-access-knowledge-base/how-to-install-one-rsa-securid-software-token-on-multiple/ta-p/3813

[StevenSpicer]

If you insist on installing the same token on multiple devices you must use an sdtid files or a CTF link. Since they allow repeated installations, both are insecure compared to CT-KIP delivery, and you must take steps to keep the file/link out of unauthorized hands.

[JamesNichols]

Do you have the rsa link enabling a single soft token for multiple devices with ct-kip delivery to share?