Shibboleth Developers

[<>]

Nate & Chad,

 

Thanks for the pointers.  I was able to get my first custom data connector ported over, although I have not reworded my packaging yet (in Shib 1.3 we packaged our connectors in a seperate jar file, I just built it straight into Shibcommon for now).  I plan to package it the same way eventually, although it looks to be a more complex procedure now.  I'll try to document my process in case it would be a useful entry on the Wiki.

 

Thanks,
Jeff

---

From: Nate Klingenstein [mailto:]
Sent: Saturday, September 29, 2007 8:49 PM
To:
Subject: Re: Attribute Encoders on the IDP?

Jeff, this message is relayed from Chad.  Hopefully it will help you out.

All of the pluggable components are controlled by Spring now. For the items that I expected people to configure I created custom XML schemas for the configuration. If you want to write a custom plugin you should probably check out the Spring documentation on this.

http://static.springframework.org/spring/docs/2.0.x/reference/extensible-xml.html

You can check out all the current plugin/spring code by looking in the config package in the shib-common project. They should offer pretty good examples.

On 28 Sep 2007, at 18:47, <> <> wrote:

Chad, 

I was not working with my custom connector yet, just experimenting with

the attribute encoder.  Thanks for the info.

I have now ported my custom data connector from Shib 1.3 to Shib 2.0,

and I believe it is okay, but there is some binding somewhere I can't

find.  In the old resolver, you could specify the classname from the

resolver.xml; in the current releases, the classes are never specified,

just the name.  I believe there is some configuration file or class that

I am overlooking that I need to update so that Shibboleth can use my

connector.  Any pointers would be great.

My instinct is that the file I need to update is internal.xml, since it

includes many maps of ID to class, but I see nothing in the file related

to data connectors, so if I do need to update it, I'm unsure how.

Thanks,

Jeff