idP v3 - Integrating with 3rd party API

[Cantor, Scott]

> > 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