Jetspeed 2
  1. Jetspeed 2
  2. JS2-847

LDAP user dn is not resolved correctly when user is in hierarchy

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.3, 2.2.0
    • Fix Version/s: 2.2.0
    • Component/s: LDAP
    • Labels:
      None

      Description

      Users in my LDAP are in hierarchy (which represents supervising).
      For example (rootContext is dc=company,dc=com and userFilterBase is o=users):
      dn: uid=bigboss,o=users,dc=company,dc=com
      dn: uid=employer,uid=bigboss,o=users,dc=company,dc=com

      Now method org.apache.jetspeed.security.spi.impl.ldap.LdapPrincipalDaoImpl.getUserDN(String, boolean)
      returns invalid DN: uid=employer,o=users,dc=company,dc=com

      This cause that roles and groups are not resolved.
      Let say I have a role:
      dn: cn=admin,o=roles,dc=company,dc=com
      objectClass: groupOfUniqueNames
      objectClass: top
      cn: admin
      uniqueMember: uid=employer,uid=bigboss,o=users,dc=company,dc=com

      but role admin is not assigned to user employer.

        Activity

          People

          • Assignee:
            Vivek Kumar
            Reporter:
            Martin Petras
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development