Shibboleth Developers

[John-Paul Robinson <>]

Hello,

Back in January I exchanged some email with Scott about how I might go
about taking attributes at the SP and providing "alternate communication
pathways" for them into the application, other than the CGI header.  The
idea being to help adapt applications ignorant of CGI header processing
for attributes by allowing them to "see" the attributes in their
preferred native format, eg. LDAP or DB.

I was interested in doing this in a generic way that didn't requiring
hacking the sp and was pleased to learn that shib-sp 2.0 modularity
could handle something like this as a plugin.  I promised to collect my
thoughts and post to the list the following week....well. ehem. It's a
bit more than a week...I still want to pursue this and hope it's not
gone stale.

After reviewing the SHIB2 wiki, it looks like this type of solution
would fall in the category of "Provision the Application's Database or
Session" under Shibbolizing a Resource.

I'd like to create an attribute resolver for the SP that would take the
attributes and present them to applications in the native format. I'm
trying to get a handle on where to start with this but am fairly
ignorant of the structure of the SP code.  I've looked around a bit but
was wondering if I could get a pointer or two on what basic files are
needed to stub out a resolver.  Is it sufficient just to concentrate
attention in the shibsp/attribute/resolver/impl area?

Sorry for the basic question but this is the first time I'm stepping
into the SP side.

Thanks,

~jpr