Shibboleth Developers

["Alistair Young" <>]

Looks good Tom.

You could perhaps add the Bodington VLE, which is a Shibboleth compatible
IdP in it's own right (it uses Guanxi/SAMUEL):
http://bodington.org
http://sourceforge.net/projects/bodington

Look forward to seeing your slides. Can we see them?

cheers,
Alistair


-- 
Alistair Young
Senior Software Engineer
UHI@Sabhal
 Mòr Ostaig
Isle of Skye
Scotland

> Alistair, thanks for the clarification.  It is confusing, isn't it?
> That's why I'm trying to write this all down, once and for all.
> Here's what I have so far:
>
> Implementations of SAML 1.1 core:
> - OpenSAML 1.0.1 (Java/C++) http://www.opensaml.org/
> - SourceID SAML 1.1 Java Toolkit 2.0
> http://www.sourceid.org/projects/saml-1.1-toolkit.html
> - SAMUEL (Java) http://sourceforge.net/projects/guanxi/
> - Proprietary vendor implementations
>
> Implementations of SAML 1.1 profiles:
> - Shibboleth 1.3 http://shibboleth.internet2.edu/
> - Proprietary vendor implementations
>
> Implementations of Shibboleth (the spec):
> - Shibboleth (of course!) http://shibboleth.internet2.edu/
> - Guanxi http://www.jisc.ac.uk/index.cfm?name=project_guanxi
> - AthensIM (IdP only) http://www.athensams.net/shibboleth/AthensIM/
>
> Implementations of Liberty ID-FF:
> - SourceID ID-FF 1.2 Java Toolkit 2.0
> http://www.sourceid.org/projects/id-ff-1.2-java-toolkit.html
> - Lasso http://lasso.entrouvert.org/
> - Proprietary vendor implementations
>
> Look good?  Am I still missing something?
>
> Tom
>
> On 4/27/05, Alistair Young 
> <>
>  wrote:
>> > I suppose you could argue that Guanxi and AthensIM are
>> > implementations of SAML by extension
>>
>> not quite. A SAML toolkit would be an implementation of SAML, i.e.
>> openSAML and SAMUEL. Guanxi and AthensIM are implementations of the
>> Shibboleth profile that use a SAML implementation, openSAML in
>> AthensIM's
>> case, SAMUEL in Guanxi's
>