Grouper Users - Open Discussion List

[Keith Hazelton <>]

Chris (and all),

Our current thinking is to use the delivered Grouper admin UI for adding 
members to a Project Bamboo group: The group admin enters a fragment of a 
person's name, then clicks a checkbox by the desired name on the returned 
list of subjects and clicks "Assign privileges" to add them to the group.

Seems like the next step for Project Bamboo is to figure out how to write an 
extension to BaseSourceAdapter that would invoke the following RESTful Bamboo 
Person Service when the group admin clicks the "Search" button in the UI 
after entering the name fragment.  See the example HTTP GET at the bottom.  
Of course, we'd need to add stuff to sources.xml to glue this all together.

-----
/**
     * Returns a Bamboo Person list.
     *
     * @param bpid - identifier for the Bamboo Person
     * @param filter - returns list filtered by the given field name
     * @param operation - operation to use when filtering. Valid values are:
     * <ul>
     * <li>"contains" return elements where filterValue appears somewhere in 
the element's filterBy field value
     * <li>"equals" return elements where filterValue exactly matches the 
element's filterBy field value
     * </ul>
     * @param value - value to use when filtering; use "*" wildcard to return 
all
     * @param orderedby - specifies the property to sort by; defaults to the 
resource identifier
     * @param order - specifies sort order for the collection to be returned. 
Valid values are:
     * <ul>
     * <li>"ascending"
     * <li>"descending"
     * </ul>
     * @param index - index into a specific page for the collection to be 
returned
     * @param count - page size for a paged collection
     * @return HTTP Response Status will be 200 OK, with the HTTP body 
containing
     *         a Bamboo Person Profile list
     * @throws DocumentHandlerException
     */
     
The call would be something like:
GET /bsp/persons/?filter=name&operation=contains&value=smith HTTP/1.1
-----

Advice on how to proceed?

         Regards,    --Keith
____________________
On Aug 5, 2012, at 3:30 PM, Chris Hyzer wrote:

> Oh, sorry, misunderstood the question.  Yes, you could implement a bamboo 
> subject adapter.  Or we could try to make a generic REST one, though that 
> seems like more effort...
> 
> I would start by seeing what you need the implement with interface Source 
> (or it is easier to extend BaseSourceAdapter), and see what restful things 
> you can do with bamboo and map and design it.  Then someone needs to code 
> it, I can help if you like...
> 
> Thanks,
> Chris
> ________________________________________
> From: 
> 
>  
> []
>  on behalf of Keith Hazelton 
> []
> Sent: Sunday, August 05, 2012 3:23 PM
> To: 
> 
> Subject: Re: [grouper-users] Subject source exposed as RESTful 
> interface--Is this a doable Grouper configuration?
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Thanks, Chris,
> 
> In the typical case, as far as I understand it, the subject source is meant 
> to be accessible from Grouper via JDBC or JNDI connectors as configured in 
> sources.xml.
> 
> The challenge in the Bamboo case is that the people we want to be able to 
> put in groups are only accessible via Bamboo RESTful queries. There's some 
> missing glue it would seem.  Or maybe I'm still just missing a crucial clue.
> 
>       --Keith
> _________
> On Aug 5, 2012, at 15:01:18, Chris Hyzer wrote:
> 
>> You could use the Grouper WS get subject operation, or ldap, but I would 
>> try not to load the subject API or grouper API into bamboo, but it is also 
>> an option and is probably doable.
>> 
>> Thanks,
>> Chris
>> ________________________________________
>> From: 
>> 
>>  
>> []
>>  on behalf of Keith Hazelton 
>> []
>> Sent: Sunday, August 05, 2012 6:34 AM
>> To: 
>> 
>> Subject: [grouper-users] Subject source exposed as RESTful interface--Is 
>> this a doable Grouper configuration?
>> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> For Project Bamboo, subjects (people) are exposed exclusively via RESTful 
>> calls. I'm wondering whether the Grouper subject adapter is sufficiently 
>> generic to be able to handle this via configuration.  If not, am I looking 
>> at some kind of custom code? If so, where would you suggest I start? What 
>> options seem promising?  I find myself wondering if an LDAP server with 
>> dynamic attribute support via plug-ins might work, but who knows?
>> 
>>          --Keith Hazelton
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
>> Comment: GPGTools - http://gpgtools.org
>> 
>> iQEcBAEBAgAGBQJQHkxTAAoJEPXbVHOlscTvFy8IAJx9whNN2h6cMoxFjj0dvaT8
>> +7L3mnPitjLqU1CyIR8eHwgbvfLVRLcJqshWZ2wa3B/GfSVqJ+Ssg4ubashTkSHt
>> 9qNu7FERg3RijjgVzwQLvdGgFdstI+oW0VW+SZkPP8ARXADPK4fa0zoxeO8B8Etq
>> zFFJYb26ncxlUcGFPUWQ19ahf0WHJ3+va8XR+E37cWM/iCPeRGxQP+XV0OKOWzP3
>> SZN83F19yFGihXnhyOoUBwCxlfyjNN8+E6XmD37xCYWvJBEO167HBzS/9KuALej7
>> gkTMtJVdgsV5Mod19utsK7AwIiYbqvI9Y+S+fc/ExiesMPft+QzTC4xZM3+r2JM=
>> =0EiX
>> -----END PGP SIGNATURE-----
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> 
> iQEcBAEBAgAGBQJQHsgqAAoJEPXbVHOlscTviQ0H/3zntC4Fz+rTemmMtFL0p590
> Jj39ObxsH7y09U7B5xWbnDgnGHZmTzBp23XHjsBklff+A3T+lnK2clbc2DZXTzM6
> GfoM6lnHbctN3h0eWRB/AwIWByagETVZPAOEovgy6WlqZUz1iyWrdOcszqeFP/vJ
> TCnoA0YWhd0qmUQFjH+iyR6n+1xjQxpGfCq/qaFLTdU7153m+izd8B+KgXOKkM7e
> pD5rvko4rHosOdzQroE/jup0pI/NDFTo218IkH0kCM9m8qMjabcE8IHoHX4k4Pz/
> VyQZssmjTAPrtbjbb43B3sYF6oqaRKD1fyU6x2UX4L/jF2/B+F6i5vynsa5FvUg=
> =rCk8
> -----END PGP SIGNATURE-----