Custom data connector issue

Cantor, Scott cantor.2 at osu.edu
Fri Aug 12 18:19:13 EDT 2016


On 8/12/16 6:06 PM, Cantor, Scott wrote:
> On 8/12/16 5:59 PM, Dev31 wrote:
>> Actually Scott this is the only error in the shibbolet idp-process log
> 
> Then the problem would have to be a basic error in the file causing the
> name of the connector and the ref to it to not match up, and the
> resolver isn't even loading your plugin/connector. If it were and it
> wasn't working, all sorts of other errors would show up when it tried to
> construct everything at the very start.

Possible subtle issue...I don't know what all is involved in making sure
the custom parsed objects get registered in Spring with the id attribute
on the DataConnector element set as the ID of the bean. If you're not
using our custom parser base classes, or maybe even if you are, perhaps
the connector's getting parsed and loaded but doesn't have the ID
established internally.

You would have to look at our source code in the
idp-attribute-resolver-spring module to compare against what you're doing.

Also make sure your connector is inheriting from the appropriate base
class, which I would assume would take care of getting some of the low
level interfaces into the picture like IdentifiableComponent.

-- Scott


More information about the dev mailing list