Ondrej Lukas created WFCORE-2257:
------------------------------------
Summary: Missing username in LDAP entry for legacy ldap realm returns 500
instead of 401
Key: WFCORE-2257
URL:
https://issues.jboss.org/browse/WFCORE-2257
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
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 EAP 7.0.x where status code 401 is returned.
This issue can be related to JBEAP-8106 (500 return for nonexistent user in legacy ldap
security realm).
[~dlofthouse] should it be handled as blocker due to regression or is this change intended
and we should just cover this change only in release notes?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)