Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Subject source exposed as RESTful interface--Is this a doable Grouper configuration?

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Subject source exposed as RESTful interface--Is this a doable Grouper configuration?


Chronological Thread 
  • From: Keith Hazelton <>
  • To:
  • Subject: Re: [grouper-users] Subject source exposed as RESTful interface--Is this a doable Grouper configuration?
  • Date: Sun, 05 Aug 2012 15:23:21 -0400

-----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-----



Archive powered by MHonArc 2.6.16.

Top of Page