Opinion on grouper/shib options
Tom Zeller
tzeller at dragonacea.biz
Thu Sep 10 16:44:45 EDT 2015
> On Sep 10, 2015, at 12:24 PM, 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.GrouperWSDataConnector" />
>
> 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.
If the bean is not being used anywhere, then I would not expect it to be instantiated, even if defined in conf/global.xml. A data connector is usually instantiated by the parser which reads attribute-resolver.xml, and you said you have not added anything to that file.
More information about the users
mailing list