OpenSAML user discussion

["Rathod, Ashish (A.K.)" <>]

Thanks Scott that helped. I set boolean flag to true and then it was able 
sign the assertion.

Now I have another problem, Here is the error that I got after the Assertion 
was signed:
testPOSTProfile(org.opensaml.POSTProfileTest)org.opensaml.InvalidCryptoException:
 SAMLSignedObject.verify() failed to validate signature value
        at org.opensaml.SAMLSignedObject.verify(SAMLSignedObject.java:330)
        at org.opensaml.SAMLSignedObject.verify(SAMLSignedObject.java:268)
        at 
org.opensaml.POSTProfileTest.testPOSTProfile(POSTProfileTest.java:116)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at org.opensaml.POSTProfileTest.main(POSTProfileTest.java:37)

Looks like it cannot verify the signature. 

Thanks in Advance.

Ashish

-----Original Message-----
From: Scott Cantor 
[mailto:]
Sent: Wednesday, March 10, 2004 4:07 PM
To: Rathod, Ashish (A.K.); 

Subject: RE: SAMLBinding Problem


> I dont know if the flag is set or not because I don't know 
> where this is set. Do you know where this is configured?

It's a boolean config property, you'd have to have it set on manually, it's
not a default value.

I would guess the problem is something to do with one of the xerces, xalan,
or xml-security jars not getting used by the environment you're testing in.
The ones that are in our package have to be used, and in some cases
endorsed. But normally you'd get a message to that effect from the opensaml
jarfile.

-- Scott