OpenSAML user discussion

[Patrick Krug <>]

I implemented SAML using SourceID's saml stuff for .NET. I get the same error as I did for my other implementation.
Here is the error that the vendor said they got on their side from their opensaml parser:
 
[date = 5/2/2008 09:59:19.026AM][orb = GSA_CERT_PS][txid = 4][host = c-hestia][msg = caught a SAML exception: <Status xmlns="urn:oasis:names:tc:SAML:1.0:protocol" xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol"><StatusCode Value="samlp:Responder"/><StatusMessage>XML::Parser detected an error during parsing: Element 'Signature' is not valid for content model: '((Conditions,Advice,((Statement|SubjectStatement|AuthenticationStatement|AuthorizationDecisionStatement)|AttributeStatement)),Signature)'</StatusMessage><StatusDetail xmlns:opensaml="http://www.opensaml.org"><opensaml:ExceptionClass>org.opensaml.MalformedException</opensaml:ExceptionClass></StatusDetail></Status>]
 
Any ideas? 

---

From:
To:
Date: Mon, 28 Apr 2008 16:23:24 -0400
Subject: RE: [OpenSAML] Saml error - Element 'Signature' is not valid for content model

I will look at Ping's SourceID.  Thanks.

> From:
> To:
> Date: Mon, 28 Apr 2008 15:45:47 -0400
> Subject: RE: [OpenSAML] Saml error - Element 'Signature' is not valid for content model
>
> > The error message on the vendors side is : XML::Parser detected an error
> > during parsing: Element 'Signature' is not valid for content model
>
> Your Signature element isn't in the right place inside the assertion.
> One-offing SAML isn't really a terrific idea. I believe Ping's SourceID
> stuff supported .NET.
>
> -- Scott
>
>
>