Shibboleth Developers

["wz qiang" <>]

Hi,
Thank you very much for your quick response.
As you mentioned, I am reading the old version of OpenSAML. What I read
now is java-opensaml1 in Shibboleth CVS (Which is also used in the
GridShib source code). Do I need to read the java-opensaml2 package? Is
that the new one?

Thank you

with best regards,

weizhong

On 3/27/07, Scott Cantor <> wrote:

> I am diving into the source code of Shibboleth, because our project needs
> the SAML function. I have some questions about the source code (Maybe I
> will have more questions, Sorry for bothering you).

Your questions seem to be more about OpenSAML than Shibboleth, so you might
want to go to that list instead.

> I wonder who call the "addHook" function, and I cannot find any in all of
> the *.java files?

OpenSAML is a library. It exposes APIs, it doesn't call them all itself.
There is no part of Shibboleth in Java that uses most of the old OpenSAML
SOAP code that I wrote, so as a practical matter, nothing calls that
particular function anywhere, in Java at least.

> Moreover, It seems that "addHook" is basis for "incoming" and "outgoing"
> functions, I also wonder where is the implementation of "incoming" and
> "outgoing"?

Again, that's not part of the library. That's what a system like Shibboleth
implements. There is no such code in Java, the IdP code today does not use
any of those SOAP APIs.

> 2, Is the C++ implementation of SAML mature?

It's more mature than the Java is in most respects because I know C++ well,
and I don't know Java well.

But you need to understand that a SAML library does not implement SAML. It
implements pieces of specs that have to be combined into a whole.
Shibboleth's code is many times the size of the SAML library code.

OpenSAML 2.0 is much larger and does much more, and Shibboleth's code is
still larger than it is, or will be anyway.

You are also looking at old APIs that will never be fully documented and we
have no plans to support going forward.

-- Scott