Grouper Users - Open Discussion List

[Julio Polo <>]

Thanks Chris for confirming, and for clarifying that wsGroupLookup is for the group I'm adding members to (which explains its singular form).  I'll also add subjectSourceId, as you suggested, to further avoid potential source namespace collisions.

-julio

On Wed, Feb 17, 2016 at 12:22 PM, Hyzer, Chris <> wrote:

Sorry, something like this:

 

PUT /grouper-ws/servicesRest/v2_2_000/groups/aStem%3AaGroup/members HTTP/1.1

Connection: close

Authorization: Basic xxxxxxxxxxxxxxxxx==

User-Agent: Jakarta Commons-HttpClient/3.0

Host: localhost:8092

Content-Length: 173

Content-Type: text/x-json; charset=UTF-8

 

{

  "WsRestAddMemberRequest":{

    "replaceAllExisting":"F",

    "subjectLookups":[

      {

        "subjectSourceId":"g:gsa",

        "subjectIdentifier":"a:b:c:d"

      },

      {

        "subjectSourceId":"g:gsa",

        "subjectIdentifier":"a:b:c:e"

      }

    ]

  }

}

 

 

From: [mailto:] On Behalf Of Hyzer, Chris
Sent: Wednesday, February 17, 2016 5:19 PM
To: Julio Polo <>;
Subject: RE: [grouper-users] groupName equals subjectIdentifier?

 

if you are looking up a group to use as a subject, you need to use subjectLookup J

 

in addMember the wsGroupLookup is the group to add the subjects to

 

You can yes, for subject source id you can use “g:gsa”, and for subjectId you can use the UUID or for subjectIdentifier you can use the group system name… ok? J

 

I would like the non lite one and pass in the body of the call a bunch of subject lookups…

 

Like this sample:

 

http://anonsvn.internet2.edu/viewvc/viewvc.py/i2mi/trunk/grouper-ws/grouper-ws/doc/samples/addMember/WsSampleAddMemberRest_json.txt?revision=9015&view=co

 

PUT /grouper-ws/servicesRest/v2_2_000/groups/aStem%3AaGroup/members HTTP/1.1

Connection: close

Authorization: Basic xxxxxxxxxxxxxxxxx==

User-Agent: Jakarta Commons-HttpClient/3.0

Host: localhost:8092

Content-Length: 173

Content-Type: text/x-json; charset=UTF-8

 

{

  "WsRestAddMemberRequest":{

    "replaceAllExisting":"F",

    "subjectLookups":[

      {

        "subjectIdentifier":"a:b:c:d"

      },

      {

        "subjectIdentifier":"a:b:c:e"

      }

    ]

  }

}

 

Thanks

Chris

 

From: [] On Behalf Of Julio Polo
Sent: Wednesday, February 17, 2016 4:59 PM
To:
Subject: [grouper-users] groupName equals subjectIdentifier?

 

I'm using Grouper web services to add several groups as members of another group.  I'm using addMember, but I couldn't use its wsGroupLookup because it appears to support adding only one group at a time.

I noticed that I can specify the group names (e.g. path:to:group:one, path:to:group:two, etc.) as the values for subjectLookups / subjectLookup / subjectIdentifier.  Is this a supported way of doing this?   Prior to this, I was making an extra call to fetch the UUIDs of the groups, then passing those as the values for subjectLookups / subjectLookup / subjectId when calling addMember.  I just want to make sure that I'm not using an unintended side effect.

-julio

Julio Polo
Enterprise Middleware, Identity and Access Management
Information Technology Services
University of Hawaii