Opinion on grouper/shib options

[O'Dowd, Josh]

Thanks Rod,

After taking a closer look, I think I found the correct solution...

I have wired my connector in a new spring config file at /conf/attribute-resolver-spring.xml.  I have registered that new file location in the /conf/services.xml as part of the 'shibboleth.AttributeResolverResources' list (just under /conf/attribute-resolver.xml).  I had to make sure to invoke #setId(String) in the constructor of the connector class to make it an initializable component, and so that the id can be used as a data source reference in the resolver's AttributeDefinitions.

This is now working.  I can see the connector methods being called during attribute retrieval.

Thanks a lot for your time and example.

-Josh

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


> 
> 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.GrouperWSDataConnector" />
> 
> Not sure where to go from here...  Thanks for any help.
> 

That's symptomatic of the spring wiring failing for some reason during initialisation, you might want to check the log of your container. Or you could set the attribute resolver service non fail fast and provoke the reload after the logging system has fully initialised.

I'll see whether I have any further inspiration overnight 
-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net