[jboss-jira] [JBoss JIRA] (WFCORE-2257) Missing username in LDAP entry for legacy ldap realm returns 500 instead of 401
Ondrej Lukas (JIRA)
issues at jboss.org
Thu Feb 2 02:16:00 EST 2017
[ https://issues.jboss.org/browse/WFCORE-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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?
> 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 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).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list