Skip to Content.
Sympa Menu

mace-opensaml-users - Re: [OpenSAML] AttributeValue of type XSString or XSInteger causing signature validation to fail

Subject: OpenSAML user discussion

List archive

Re: [OpenSAML] AttributeValue of type XSString or XSInteger causing signature validation to fail


Chronological Thread 
  • From: JM Tremblay <>
  • To:
  • Subject: Re: [OpenSAML] AttributeValue of type XSString or XSInteger causing signature validation to fail
  • Date: Tue, 2 Nov 2010 16:56:57 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=u0ETExSy792/oS/2e4LvswW1VwgWCUDvP3n88nBL80VGb8XcicqTwOgknxCh8gcNbz gmu5URiBLlJJ6HVKyVnm78/47eoJ1ZT9cMTeVma4Qkub/AIRQShma5IM3tRmQdSwI716 BCTvutFlfAhhMMHDPuGaEje+DbsmslPffq+cE=

> 1) how are you serializing the DOM on the signing side?  Are you using
> our helper methods or your own code?

I was using some helper method we had already. It had indentiation
turned on, which I just commented out, and got rid of the issue
(SignedInfo has the InclusiveNamespaces without the extra newlines).
Transformer transformer = TransformerFactory.newInstance().newTransformer();
//transformer.setOutputProperty(OutputKeys.INDENT, "yes");
...

I didn't suspect this would be a problem. I thought canonicalization
on the parser side would get rid of any extra formatting. It did for
the digester output part, I suppose.

I'll probably change my code to use your helper methods instead.
Thanks guys for your help and your quick replies.

JM



Archive powered by MHonArc 2.6.16.

Top of Page