mace-opensaml-users - RE: problems verifying signatures with saml 1.1 api
Subject: OpenSAML user discussion
List archive
- From: Scott Cantor <>
- To: 'mochamaster' <>, 'saml' <>
- Subject: RE: problems verifying signatures with saml 1.1 api
- Date: Mon, 12 May 2003 15:07:39 -0400
- Importance: Normal
- Organization: The Ohio State University
> org.apache.xml.security.signature.XMLSignatureException:
> The Reference for URI #d416e1355c30706bdffc11bae94b2d07 has no
> XMLSignatureInput
>
> seems that xmlsec can't obtain the signed components
> during de-transformation.
Yeah, that's basically it. Normally you see that when the parser hasn't
tagged the ResponseID as an ID attribute. On the signing
side, that's why I have to use the DOM3 calls. On the verify side, it's
normally only an issue if you're not validating, but my code
uses a schema. So Xerces should already tag it properly.
Is the code you're running just a simple program, or a servlet? Do you have
the dom3 jars in the endorsed lib folder of your JDK or
Tomcat?
I can try running whatever code you've got, but I fear it's likely to be an
environmental thing.
-- Scott
---------------------------------------------------mace-opensaml-users-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at
http://archives.internet2.edu/
---------------------------------------------------mace-opensaml-users--
- problems verifying signatures with saml 1.1 api, mochamaster, 05/12/2003
- RE: problems verifying signatures with saml 1.1 api, Scott Cantor, 05/12/2003
Archive powered by MHonArc 2.6.16.