OpenSAML user discussion

[Patrick Krug <>]

No I am not using the same one but I will look to move the signature to the last child element.   I tried to attach the token but it was rejected by mace as being to large. 
 
Thanks for your response I will try to change the location.

> Date: Fri, 2 May 2008 11:43:36 -0400
> From:
> To:
> Subject: Re: [OpenSAML] Saml error - Element 'Signature' is not valid for content model
>
> On Fri, May 2, 2008 at 10:59 AM, Patrick Krug <> wrote:
> >
> >
> > [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>]
>
> Are you still using the Response you posted earlier? As I said, the
> Signature element is not placed correctly. The error message above
> suggests the Signature element should be the last child element of the
> Assertion, but in the example you posted the Signature was the first
> child element of the Assertion. So the example is not schema-valid.
>
> Tom