-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
In case when legacy LDAP Realm uses username-load attribute and its value does not exist in LDAP entry then current implementation returns status code 500. This is different behaviour from WildFly 10 where status code 401 is returned.
This issue can be related to WFCORE-2258 (500 return for nonexistent user in legacy ldap security realm).
- clones
-
JBEAP-8584 Missing username in LDAP entry for legacy ldap realm returns 500 instead of 401
- Closed
- duplicates
-
WFCORE-2258 500 return for nonexistent user in legacy ldap security realm
- Resolved