Return
-
Title
Logging in with Defender Desktop Login, sometimes a user is able to login successfully and other times the same user fails. The failed attempts show "Authentication Rejected (No matching user found)" in the DSS Audit Log. -
Description
A Defender Desktop Login user is able to login successfully at some times, however at other times it is found that the login fails. The user may see "Access Denied - no valid route found."
Examples from the Defender Security Server logs (when the Defender Desktop Login workstation is online):
Success:
Wed 16 Nov 2016 13:18:50 Info: User test_user found as user CN=test_user,OU=Users,DC=test_domain,DC=org Session ID: B123456712345671Wed 16 Nov 2016 13:18:50 User test_user authenticated with token GO01234512345 Session ID: B123456712345671
Failure:Wed 16 Nov 2016 13:19:45 Radius response: Authentication Rejected (No matching user found) User-Name: test_user , Request ID: 1 Session ID: B123456712345681 -
Cause
In this particular example, note the User-Name value in the logs has a trailing space, showing immediately following the username and before the comma:
"User-Name: test_user , Request ID: 1"
Defender Desktop Login is passing the user-name value including the trailing space and this user does not exist.
-
Resolution
Ensure that the user is not adding any trailing spaces when trying to login to Defender Desktop Login.