Extending ResolverStoredIDDataConnector
Tom Poage
tfpoage at ucdavis.edu
Mon Jun 11 16:16:22 BST 2012
On Jun 11, 2012, at 4:52 AM, Chad La Joie wrote:
> On Mon, Jun 11, 2012 at 7:47 AM, Alistair Young
> <alistair.young at uhi.ac.uk> wrote:
>> I'm looking into migrating to the shib IdP 2.3.6 but already have a database of ePTID values. Is it possible to register your own connectors, such as an extended ResolverStoredIDDataConnector to deal with the legacy database?
>
> Yes.
After attending a one-day conference on the subject, I'm impressed enough to consider using MongoDB to store ePTIDs and (eventually) uApprove data.
The IdP v2 connector looks to be written by a 10gen programmer. From my Java-naive point of view, it looked to require a decent understanding of what's going on at that level of the code.
Will IdP v3 require this type of adapter/code, or will v3 perhaps use something along the lines of Spring Data to manage technology-specific aspects of the data source?
Alternatively, might there be a facility/framework for storing ePTIDs etc. in LDAP?
Thanks.
Tom.
More information about the dev
mailing list