Return
-
Title
LDAP authentication not validated properly when Full Primary UserID field is blank -
Description
When LDAP is set as the Primary Authentication and the Full Primary UserID field is left blank, it will allow the user to login with invalid credentials. The authentication is validated and will rejected invalid credentials when the Full Primary UserID field is populated. -
Resolution
STATUS
This issue has been reproduced and product defect #10441 has been submitted to the product management team for review. No ETA for a fix is available at this time.
WORKAROUND
If authenticating against an LDAP directory, please ensure the Full Primary UserID is properly filled in with the DN of the user.If authenticating against AD, then the WinAD authentication method should be selected instead.
-
Change Request
10441