Jetspeed 2
  1. Jetspeed 2
  2. JS2-836

Lookup of LDAP users per role using a role membership attribute on a user is broken

    Details

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

      Description

      See the discussion on the Jetspeed user list starting on december 3rd, 2007 : "Users and Roles definition with LDAP".

      The problem is that there is a conflict between how roles are assigned to users, and the way users are found, which belong to a specific role.

      When user-role membership attributes are used (i.e. you define in an attribute on the user which roles the user has, by default this is the 'j2-role' attribute), a role is assigned to a user using the role's DN, for example 'uid=someRole,ou=Roles,o=sevenSeas'. However, to lookup the users for a role (using the user-role membership attribute), the LdapMembershipDaoImpl.searchUsersFromRoleByUser(roleUid) is used, which constructs a LDAP query which searches for the role UID value in each user's role attribute. Hence, no users are found because role attributes on the users contain role DNs instead of UIDs.

      The reverse lookup, namely looking up which roles a user has works, because the method assumes there can be either a role UID or a role DN in the role attribute of a user (see method LdapMembershipDaoImpl.searchRoleMemberShipByUser() )

      So basically, the LdapMembershipDaoImpl.searchUsersFromRoleByUser(roleUid) should look for role DNs as well as UIDs

        Activity

          People

          • Assignee:
            Ate Douma
            Reporter:
            Dennis Dam
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development