Jetspeed 2
  1. Jetspeed 2
  2. JS2-873

Simplified parent-child relationship model for Roles and Groups

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.0
    • Component/s: Admin Portlets, Security
    • Labels:
      None

      Description

      The current Jetspeed security role/group model technically supports a hierarchical relationship.
      In practice though, this isn't used really, nor do the j2-admin portlets support it through the UI.
      Furthermore, the hierarchical relationship is based on a specific (preferences) hierarchy naming which really doesn't fit well (better said: not at all) with a backend like LDAP.
      The current model simply cannot be used with LDAP for using role-group relationships.

      A typical use-case requiring a more simple and straighforward solution:

      • defining organisation divisions and subdivisions as groups and defining a parent-child relationship between them
      • a user belonging to a division group then also belongs to any subdivision group of that division
      • the same goes for roles, the user could automatically inherit the roles assigned to the subdivision group.

      As AFAIK the hierarchical relationship model isn't used at all right now, this issue will resolve its complexity and limitation by replacing it with "flat" parent-child relationships:

      • only support non-hierarchical groups and roles
      • allow a group or role needs to be defined as child of another group or role
      • just need a security-role-role and security-group-group table (and corresponding LDAP mapping)
      • check/enforce no circular references can be created
      • adding UI support for this will be rather easy: we already have support for the group-role relationships, this is just more of the same

        Activity

        Hide
        Ate Douma added a comment -

        The brand new portal trunk (copied over from the security-refactoring branch) now provides a new and (extremely) flexible, extendable and pluggable Principal Associations solution
        which provides all the features described, and then some

        Show
        Ate Douma added a comment - The brand new portal trunk (copied over from the security-refactoring branch) now provides a new and (extremely) flexible, extendable and pluggable Principal Associations solution which provides all the features described, and then some
        Hide
        Ate Douma added a comment -

        Work for the issues JS2-870, JS2-872 and JS2-873 will commence in the separate security-refactoring branch (branched off the JS2-869 branch).

        Show
        Ate Douma added a comment - Work for the issues JS2-870 , JS2-872 and JS2-873 will commence in the separate security-refactoring branch (branched off the JS2-869 branch).

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 120h
              120h
              Remaining:
              Remaining Estimate - 120h
              120h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development