Opinion on grouper/shib options

[Cantor, Scott]

On 9/4/15, 12:21 PM, "users on behalf of O'Dowd, Josh" <users-bounces at shibboleth.net on behalf of Josh.O'Dowd at mso.umt.edu> wrote:

>I'm not sure I am following...  Are you saying I should not proceed, due to unavailability of API classes such as:
>edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.dataConnector.BaseDataConnector
>edu.internet2.middleware.shibboleth.common.config.attribute.resolver.dataConnector.BaseDataConnectorBeanDefinitionParser
>edu.internet2.middleware.shibboleth.common.config.attribute.resolver.dataConnector.BaseDataConnectorFactoryBean

No, I was referring to the Spring parsing classes, not the resolver itelf. Those base classes all exist (well, classes exist, they're all different).

As far as the Spring stuff is concerned, we were just discussing the issue of extensions on the dev call and it may be possible to start by wiring up a custom data connector in Spring alone, in a separate beans file in the resolver and reference that in the rest of the resolver config. Rod was going to look into that.

The main problem with extensions has always been the need for a schema and a Spring parser, none of which has anything to do with the functionality you're trying to build.

-- Scott