Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-109

Consistent treatment to users in special groups

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.0, 1.5.1, 1.5.2
    • Fix Version/s: 1.5.2
    • Component/s: DSpace API
    • Labels:
      None
    • Attachments:
      0
    • Comments:
      14

      Description

      We populate users into their groups via the use of "special groups" on the fly (as part of Shibboleth authN integration into DSpace) and had been noticing that the mapped users cannot gain access to their resources despite they have the aforementioned groups in the special group.

      Temporary fix for this is to persist the group membership, e.g.

      int[] groupIDs = AuthenticationManager.getSpecialGroups(context,request);
      for(int i=0;i<groupIDs.length;i++){
      Group g = Group.find(context, groupIDs[i]);
      //.....
      g.addMember(eperson);
      g.update();
      }

      This is not ideal, it would be better if the special groups are loaded/integrated into Group.isMember(eperson), or Group.isMember(groupid), etc calls. These isMember seem to be only honouring explicit users assigned in DB. Currently special groups only included in Group.allMemberGroupIDs and isMember(context,groupid).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bollini Andrea Bollini (4Science)
                Reporter:
                bliong Bruc Liong
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: