Opinion on grouper/shib options

[O'Dowd, Josh]

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

-Josh


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Friday, September 04, 2015 9:54 AM
To: Shib Users
Subject: Re: Opinion on grouper/shib options

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

>I don’t mind writing an extension.  It is well documented for IDPv2.x.  I am assuming the extension instructions at https://wiki.shibboleth.net/confluence/display/SHIB2/IdPDevExtDataCtr can be applied to v3 because I haven’t seen anything to indicate otherwise.

There are class differences, but the broad outline is the same. But there are no current classes available as an API to build Spring custom parsers. We have an issue open to finalize the split in the spring modules to designate what classes can be used as APIs by extensions. Most of the Abstract* classes will probably be APIs.

-- Scott

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