When using “Challenge Response Authentication” your CAG / Netscaler (or other) device will ask (challenge) you for your token PIN right after login, rather than on the login page.
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 a text editor (such as Notepad).
2. Set AuthEnginePinCodeTokenSeparated to “True”.

3. Set NotifyPinCodeIncorrectOnAccess to “True”.
While having this setting on “False” may possibly increase security, it may also significantly confuse your users when they forget their PIN.

4. Change the text message text if using challenge / response.
When a user goes from the first login screen (the username, password, PIN screen) to the second login screen (where they enter the challenge response), the system sends a text / SMS message with the challenge response (code). Make sure this message is easily understand. We recommend using a simple message such as: “Your passcode for this login is: XYZ”. The screen shown is found in the “configuration” menu, in “Admin Console”. (You can only change this screen if you’re an Admin user within SMS2.)

5. Restart the “AuthEngine” service after making the configuration changes.
“service.msc” can be opened through the Windows Run dialog.

6. Test RADIUS challenge / response.
Before rolling this out into your full production environment, it’s a good idea to test and make sure everything works. In-order to test our systems we use NTRadPing, this a free software application that is available from http://www.mastersoft-group.com/download/
If you correctly supply the username and PIN code you’ll get a response of “Access-Challenge” and a “State”. If you supply an incorrect PIN and “NotifyPinCodeIncorrectOnAccess” is set to “True” you’ll get an “Access-Reject” message. If you supply an incorrect PIN and “NotifyPinCodeIncorrectOnAccess” is set to “False” you will get an “Access-Challenge”, but no matter how you respond to the challenge the overall authentication process will fail as the PIN was wrong. Although this functionality can prevent attackers from knowing if a failure was due to an incorrect PIN or token we recommend having “NotifyPinCodeIncorrectOnAccess” set to true “True”.

7. Reply to the challenge.
We need to reply to the server with the state code we were issued (we do this so the server knows we are replying to a challenge). Add the state code provided and put the current token value into the password box, click Send.
Note the “Access-Accept” message indicating success.
Now we know RADIUS challenge / response is working we can configure Citrix Access Gateway, NetScaler, or any other product as required.

8. After you’ve followed this process your login should look like this.
9. This is the new screen that challenge / response adds.
Challenge / Response on the iPhone/iPad is not supported at this time.
