Shibboleth Developers

[André Cruz <>]

As long as you are touching that code maybe you can give me a few
pointers regarding the ShibTarget API. :)

My plugin will be very simple in such that it will have only one
configuration option (besides the config file and schema dir) which will
be the shib session:

pass - the plugin will not touch the request
optional - it will fill the headers if there is a session and empty them
if not
always - a shib session is mandatory and created if there is none

So, no htaccess processing or attribute checks in the lighttpd config
file, everything will be done on shibboleth.xml.

I'm trying to find out what interfaces I will have to implement...
ShibTarget is one of them. Will I need to implement IRequestMapper as
well? I see some htaccess stuff on ApacheRequestMapper so I'm not sure...

On the initialization there are some features that are selected...

ShibTargetConfig::Listener
ShibTargetConfig::Metadata
ShibTargetConfig::AAP
ShibTargetConfig::RequestMapper
ShibTargetConfig::LocalExtensions
ShibTargetConfig::Logging

Will I need the same features as mod_apache?

Sorry to bother you with these questions but this is not documented
anywhere I could find. Maybe I can contribute to shibboleth with this
plugin in the end.

Thanks,
André

Scott Cantor wrote:
>> Ok... You said that for Shibboleth 2.0 this would be completely
>> changed... So what you said here will not apply? Will there still be
>> this layer and this ShibTarget class to implement?
>>     
>
> I just meant that the API will be different and your code won't compile
> without changes, not that the design will be completely different.
>
> Going from the old SAML code to the new is a huge alteration and it's taking
> me a lot of time to even manage that port, not even including all the new
> functionality.
>
> -- Scott
>
>

Attachment: signature.asc
Description: OpenPGP digital signature