Software tokens, when assigned to a user, then need to be 'distributed' from the RSA server...
so, they need to be sent through a profile, so that it more closely matches the end user device
that the software token will be running on.
A profile pre-determines 6 or 8 digit, 30 or 60 second interval, pinpad style, keyfob style, or pinless,
password protected, and device serial numbers. A profile also makes sure you don't generate a token
that won't install on a target device due to some incompatible setting.
Delivery method might be a file, a URL, a QR code with URL, compressed token format.
So, build (a) profile(s) using the appropriate device type and other settings based on
a) make, model, and version of target device
b) delivery method of the token
c) what the admin guide for the RSA token for that device says or recommends
Each target device type has an RSA software token administrator guide
that can give you more specifics about how to set up a software token profile and delivery methods for that type of device.
Admin guides here
https://community.rsa.com/docs/DOC-40601#token
