[
https://issues.jboss.org/browse/WFLY-7781?page=com.atlassian.jira.plugin....
]
Ondrej Lukas updated WFLY-7781:
-------------------------------
Description: {{username-load}} attribute of legacy LDAP Realm stop to work. This
attribute is used for assigning username from some LDAP entry attribute. In current
behavior username passed in credential is used as username even if username-load attribute
is configured. (was: {{username-load}} attribute of legacy LDAP Realm stop to work in EAP
7.1.0.DR9. This attribute is used for assigning username from some LDAP entry attribute.
In current behavior in EAP 7.1.0.DR9 username passed in credential is used as username
even if username-load attribute is configured.
Due to regression we request blocker. Taking EAP 7.0.x configuration and put it into EAP
7.1.x will causes that username-load feature stop to work.)
Summary: username-load attribute of legacy LDAP Realm stop to work (was:
Regression in EAP 7.1.0.DR9: username-load attribute of legacy LDAP Realm stop to work)
username-load attribute of legacy LDAP Realm stop to work
---------------------------------------------------------
Key: WFLY-7781
URL:
https://issues.jboss.org/browse/WFLY-7781
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Blocker
{{username-load}} attribute of legacy LDAP Realm stop to work. This attribute is used for
assigning username from some LDAP entry attribute. In current behavior username passed in
credential is used as username even if username-load attribute is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)