|Applies To||RSA SecurID for Microsoft Windows|
RSA ACE/Server RSA Authentication Manager
RSA SecurID Software Token for RSA SecurID Token for Windows Desktops, Smart phone and Blackberry
|Issue||How to configure the number of invalid PASSCODEs before entering Next Tokencode Mode for RSA SecurID Software Token|
How to make software tokens behave like hardware tokens as far as Next Token Code
mimic the behavior of Hardware tokens with softid_multi
Users are entering next tokencode mode on a single transaction client or do not understand the next tokencode prompt
mimic the behavior of Hardware tokens
|Cause||By default, RSA SecurID Software Tokens enter Next Tokencode Mode after a single failure|
Set an environment variable named "SOFTID_MULTI" that causes Software tokens to mimic the behavior of Hardware tokens.
Note: in some versions of AM6.1 and UNIX, you may need to manually set and export the variable, instead of modifying the script.
Stop and restart all RSA Services, a reboot is not needed on UNIX. Verify the variable has been set by using env .
You can disable the feature by setting the Value to 0 and restarting the RSA Services.
4. Add the following variable and value to the System Variables.
5. Stop all RSA Services and reboot the system
Note: You can disable the feature by setting the Value to 0. Reboot the Windows ACE/Server for this change to take effect.
If you have any Replica servers, this procedure must be repeated on each Replica.
Software token by default goes into next tokencode after one failed attempt. This environmental variable will allow the software token to go into next token code only after three failed attempts (or the number set for the type of agent).
|Legacy Article ID||6.0.1419430.2754086|