[ https://issues.jboss.org/browse/WFCORE-2257?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-2257: --------------------------------- Description: 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). was: 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)