Skip to Content.
Sympa Menu

mace-opensaml-users - Re: [OpenSAML] Saml error - Element 'Signature' is not valid for content model

Subject: OpenSAML user discussion

List archive

Re: [OpenSAML] Saml error - Element 'Signature' is not valid for content model


Chronological Thread 
  • From: "Tom Scavo" <>
  • To:
  • Subject: Re: [OpenSAML] Saml error - Element 'Signature' is not valid for content model
  • Date: Fri, 2 May 2008 11:43:36 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PEWElrXr7BckojeSKmGgC0dhdyBFmXjiq5eOpdKEQM6oG94ahiHsgyXjodUy1/JSZw1Mj3vQjiPwdEHdmdLC2QFmLMK9CUfGPYR1rmD+qpkLw2CYKuayNygm07WVUUhdLhDiR60gOL43C60njMt1x4yFIWm0CRyf/z2zDLN/5Bs=
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

Archive powered by MHonArc 2.6.16.

Top of Page