Customer is having issues with configuring the Defender OTP to work correctly with the Web Access portion of vWorkspace. They are entering Username and then entering the OTP that was configured in the Defender policy section of Active Directory Users and Computers (ADUC).
The Defender Policy was configured to use the Token and AD password. When the customer then pressed enter they failed Radius Authentication resulting in no applications being presented to them.
Create a new policy and use Token only (using eight characters for their OTP) and then test again, this time entering the OTP generated from Defender and then the AD password.
Radius will validate the OTP and Active Directory will validate the password.
The way that we integrate with any of the Radius deployments is that we have incorporated the Users AD password and the Radius OTP into one line called password. When the user enters that information the Web Access Server then strips the first or last characters from the string and passes that information to the Radius server for Authentication, once that is passed we then authenticate with the remainder of that string with our Broker for AD authentication. If both forms of authentication pass then their applications are presented to the user.