Skip to Content.
Sympa Menu

mace-opensaml-users - Re: Problems signing response...XMLObject does not have the XMLSignature created during marshalling

Subject: OpenSAML user discussion

List archive

Re: Problems signing response...XMLObject does not have the XMLSignature created during marshalling


Chronological Thread 
  • From: Brent Putman <>
  • To:
  • Subject: Re: Problems signing response...XMLObject does not have the XMLSignature created during marshalling
  • Date: Mon, 14 May 2007 15:40:22 -0400

Is that using IBM's JDK?

FWIW, I just tested the latest trunk of java-xmltooling on my IBM Linux
JDK, using BouncyCastle configured as a security provider. Everything
compiles OK and all unit tests pass.

That's with this IBM JDK version:

$JAVA_HOME/bin/java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build
pxi32dev-20070201 (SR4))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32
j9vmxi3223-20070201 (JIT enabled)
J9VM - 20070131_11312_lHdSMR
JIT - 20070109_1805ifx1_r8
GC - 200701_09)
JCL - 20070126


Bouncy Castle is configured in jre/lib/security/java.security as the
last provider, like so:

#
# List of providers and their preference orders (see above):
#
security.provider.1=com.ibm.jsse2.IBMJSSEProvider2
security.provider.2=com.ibm.crypto.provider.IBMJCE
security.provider.3=com.ibm.security.jgss.IBMJGSSProvider
security.provider.4=com.ibm.security.cert.IBMCertPath
security.provider.5=com.ibm.security.sasl.IBMSASL
security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider


I remember I had to experiment quite a bit awhile back with the ordering
of the security providers in the IBM JDK, and this seemed the only
ordering that worked for the Apache XML Security library stuff. This
was my first foray into using IBM's JDK, however, so YMMV.

--Brent




Mike Klein wrote:
> I pulled latest release for each subsystem and can get them to build,
> although tests don't pass again.
>
> I now have SignatureConstants class which is good.
>
> I notice there are some changes which now break startup/initialization.
> This may be because we are using xerces 2.7.1 (I will try 2.9.0) but it
> seems like coding error. I am looking into it.
>
> java.lang.NullPointerException
> at
> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.getAttribute(Unknown
> Source)
> at
> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown
> Source)
> at
> org.opensaml.xml.parse.BasicParserPool.createBuilder(BasicParserPool.java:506)
> at
> org.opensaml.xml.parse.BasicParserPool.getBuilder(BasicParserPool.java:158)
> at
> org.opensaml.xml.parse.BasicParserPool.parse(BasicParserPool.java:199)
> at org.opensaml.xml.XMLConfigurator.load(XMLConfigurator.java:128)
> at
> org.opensaml.DefaultBootstrap.initializeXMLTooling(DefaultBootstrap.java:126)
> at org.opensaml.DefaultBootstrap.bootstrap(DefaultBootstrap.java:71)
>
>
> mike
>
>
>
>



Archive powered by MHonArc 2.6.16.

Top of Page