Uploaded image for project: 'WildFly Elytron'
  1. WildFly Elytron
  2. ELY-2358

Option extract-rdn selects the rightmost matching RDN instead of the leftmost one

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.15.14.Final
    • None
    • Realms
    • None
    • Hide

      There are workarounds like configuring a different mapping (a search for groups that reads the CN attribute in the example) or coding your custom role decoder or mapper.

      Show
      There are workarounds like configuring a different mapping (a search for groups that reads the CN attribute in the example) or coding your custom role decoder or mapper.

      When a mapping in a ldap realm is configured to use the option extract-rdn, for example something like the following:

      /subsystem=elytron/ldap-realm=ldap_realm:add(dir-context=ldap_dir-context, direct-verification=true, identity-mapping={search-base-dn="cn=Users,dc=example,dc=com", rdn-identifier="samacountname", attribute-mapping=[{from="memberOf", to="Roles", extract-rdn="cn"}]})
      

      The RDN farthest to the right with name cn is selected. For example with a group name cn=Role1,cn=Roles,dc=example,dc=com the value Roles is returned instead of Role1. This makes no sense because all the roles inside that branch will be transformed in the same role name Roles. The RDN situated furthest to the left should be selected instead, Role1 in the example.

              rhn-support-rmartinc Ricardo Martin Camarero
              rhn-support-rmartinc Ricardo Martin Camarero
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: