Opinion on grouper/shib options

[O'Dowd, Josh]

Thanks Kevin,

The thread I responded to doesn't properly represent the original issue.  While Jim's solution is a viable option for RESTful WS connections, I was working on a speculation from Scott Cantor that one can create a custom data connector and wire the connector in using just spring configuration xml.  The connector I wrote is a very simple concrete implementation within the idp-attribute-resolver-api which leverages utilities provided by the grouper-client.jar.  I am not really reinventing anything, but trying to find a cleaner way to implement a custom data connector in Shib3 without using schema.

I will repost my reply to one of Scott's original responses in order to provide better context.  This issue was born last week.

Thanks again for you time and input.

-Josh

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Kevin Foote
Sent: Thursday, September 10, 2015 12:29 PM
To: Shib Users
Subject: Re: Opinion on grouper/shib options

Hey Josh,



> On Sep 10, 2015, at 10:24 AM, O'Dowd, Josh <Josh.O'Dowd at mso.umt.edu> wrote:
> 
> Thanks Rod.  Unfortunately I am not having success with my implementation....
> 
> I have taken Scott's direction and created a new DataConnector using the idp-attribute-resolver-api.  I have chosen to extend the AbstractSearchDataConnector and I have completed the class along with its dependencies; such as ExecutableSearch, ExecutableSearchBuilder, MappingStrategy, and Validator.  The dependencies are wired into the new class during constructor.
> 
> I have wired the DC into spring using our /conf/global.xml (this does not seem to be working, see below...):
> 	<bean id="grouperWsDc" 
> class="edu.umt.shibboleth.idp.attribute.resolver.dc.grouper.GrouperWSD
> ataConnector" />
> 
> Our attribute-resolver.xml currently loads in LDAPDirectory DC via schema, which provides the bulk of our released user attributes.  The GrouperWS DC is intended to create a single 'isMemberOf' attribute to include in the release.  I have not add anything to attribute-resolver.xml for the GrouperWS DC or the 'isMemberOf' attribute.
> 
> So my initial difficulty is that the bean is not being loaded at startup.  I have a logger entry in the constructor that I am not seeing at runtime.
> 
> Not sure where to go from here...  Thanks for any help.

Hey Josh, 

Not sure what OOB GrouperWS returns in form of information XML or what.. 

If the native grouperWS returns XML then we have two points of confirmation that the webservice connector[1][2] that Jim wired up works flawlessly with the v3 IdP. Why re-invent the wheel when there is one to use? :-) 

[1] https://wiki.shibboleth.net/confluence/x/ngIUAQ
[2] https://github.com/UWIT-IAM/uw-idp-rws-connector

--------
thanks
 kevin.foote

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net