Sample Dataconnector for Shib 3.1

[Cantor, Scott]

On 5/14/15, 2:08 PM, "Krug, Jeff" <Jeff.Krug at gtri.gatech.edu> wrote:

>I spent a bit of time reviewing the content of idp-attribute-resolver-spring, and specifically the class that I imported, the AbstractDataConnectorParser, and that has a quite a bit of functionality that I would expect anyone writing a Data Connector would want...  

I'm not disagreeing, but the old custom syntax model has been a failure from day one, and the difficulty of the plugins is the biggest reason. Maybe it needs to be API, but it definitely is not right now.

The only reason we're still using it is compatibility, it simplifies upgrades from V2 enormously to stick with that syntax for now, but it is a nightmare for extension authoring.

>I don't mind taking on the risk of having to update my code with point releases given the value I see in reusing this part of the IDP code, but I would be curious to see how a data connector should be written if what I am doing is wrong.  I certainly do not mind reworking the code I have if there is a better way.  

Originally the hope was that we would be able to somehow mix the native and custom syntaxes so that new plugins would just be written as Java beans without all the extra work. That didn't pan out so far at least.

-- Scott