1. Open the Configuration.xml file.

Navigate to the Settings folder inside the installation folder (usually under c:/Program Files/Wright/Settings), then open ‘configuration.xml’ with your favorite text editor (such as Notepad).

2. Set the AuthEnginePinCodeTokenSeparated to “False”.

The challenge / response is turned on and off using the “AuthEnginePinCodeTokenSeparated” setting. Change “AuthEnginePinCodeTokenSeparated” to either “True” or “False”. “True” will turn it on, and “False” will turn it off.

3. Change the CloudSMS Token Expiry Time.

Challenge / response CloudSMS tokens (text message tokens) are sent immediately after the username, password, PIN authentication page. This isn’t possible when the token needs to be input on the first authentication page. The solution is to increase the token’s expiry time and send the user a message with their next token.

The value is in minutes. There are 1,440 minutes in a day. 10,080 in a week. 40,320 minutes in four weeks.

4. Generate a new text / SMS message when the login is refused due to an incorrect PIN (as apposed to an incorrect token code).

If “NotifyPinCodeIncorrectOnAccess” is “False” then a new token will be sent via text / SMS message every time authentication fails for any reason.
If “NotifyPinCodeIncorrectOnAccess” is “True” then a new token will only be sent if the token code was incorrect but the PIN code was correct.
We recommend you set this value to “True”.

5. Change the text on the text / SMS message.

This screen is available to SMS2 admins by opening “Admin Console” and selecting “configuration”.
You should change the text to something similar to “Your next passcode is: {passcode}”.

6. Send yourself an initial token.

This screen is in the SMS2 “Admin Console” under “Configuration” and is available to all users.
If users do not send themselves an initial token, one will be sent automatically when they attempt their first login.

7. Restart AuthEngine.

“service.msc” can be opened through the Windows Run dialog.

8. Attemp a login using NTRanPing to check RADIUS is working as planned.

Note the “Access-Accept” message indicating authentication was successful.