Loading...

XML

Word

Printable

Steps to Reproduce:
Hide

Start EAP

Prepare resources

Add dir-context: /subsystem=elytron/dir-context=foo:add(url=foobar)

Add ldap-realm:

/subsystem=elytron/ldap-realm=foo:add(dir-context=foo, identity-mapping={attribute-mapping=[{from=foo, to=bar}],rdn-identifier=foobar})

Navigate to LDAP security realm in Elytron subsystem -> Security Realms / Authentication and switch to LDAP Realm

Edit any field on Attributes tab and save
Show
Start EAP Prepare resources Add dir-context: /subsystem=elytron/dir-context=foo:add(url=foobar) Add ldap-realm: /subsystem=elytron/ldap-realm=foo:add(dir-context=foo, identity-mapping={attribute-mapping=[{from=foo, to=bar}],rdn-identifier=foobar}) Navigate to LDAP security realm in Elytron subsystem -> Security Realms / Authentication and switch to LDAP Realm Edit any field on Attributes tab and save
Affects:

User Experience
Git Pull Request:
https://github.com/hal/core/pull/413

Configuration changes made on Attributes tab of a LDAP Realm are not popagated to model.

clones

JBEAP-10239 No configuration change of a LDAP security realm's attribute is propagated to model