OpenSAML user discussion

[Bob Daly <>]

Hi,
I came across this archived posting from May 2003, and
I'm seeing the exact same error...receiver of a signed
SAMLAssertion can't verify.

I definitely have the endorsed .jars in both my JDK
and Tomcat (using Axis and Tomcat).

Just wondering if anything else was discovered related
to this before I spend more time trying to solve it or
take a different approach.

thanks,
Bob Daly

>
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

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

---------------------------------------------------mace-opensaml-users-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

---------------------------------------------------mace-opensaml-users--