idP v3 - Integrating with 3rd party API

[Camel Guy]

Thank you for the thoughtful replies.

It would be advantageous to get the third party attributes into Shibboleth
attributes for logging, auditing, etc.

Regarding building a custom data connector, V2 is well documented regarding
spring custom config schema etc. For v3, I generally read the source code.
Could you point me to where I should start?

Thank you,

cg

On Friday, June 26, 2015, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > > It appears that the best approach is to write a custom Data Connector
> that
> > > loads attributes from the API and makes them available to the rest of
> > > Shibboleth idP. Am I on the right path?
> >
> > Likely. Particularly if you mean that the format of that data is fairly
> esoteric
> > and you want to just get it into the resolver in string form I guess.
>
> That said, sadly writing a flow is easier than the custom data connector
> part. The connector's easy, but we're still using the old config schema for
> the resolver, so you would generally speaking need to create all the custom
> Spring parser and schema stuff like with V2's plugins to get it usable in
> the resolver's config file.
>
> As I say that though, I think there's a way you could just define your
> connector's bean in Spring format and then reference it by bean ID in the
> resolver. I know we were trying to make that viable so that people doing
> local extensions could skip all the parser nonsense, but I don't know where
> we got to on that, should be at least mentioned in the resolver config doc
> pages.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net <javascript:;>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150626/ac33f2dc/attachment-0001.html>