OpenSAML user discussion

[Sidhartha Priye <>]

Scott/Brent,

I had reported that I was able to resolve this issue few weeks back with some configuration setup using (cxf-incubator-2.0); however this issue came back again couple of days back. So I logged this in Apache CXF JIRA tracker and Daniele Kulp (development lead from Apache CXF) resolved this in the latest cxf distribution 2.2.7 based on the clue you had provided. Thanks for that.

So for any one who would like to know the details of my setup that gives me a working solution. Here is the JIRA tracker item that has all the details. Read the last post with all the configuration details to integrate CXF + Open SAML 2.0 on Websphere 6.1 (IBM JDK 1.5). This is a very rare use case that is extremely difficult to accomplish and so the details here will be very useful. Remember WAS 6.1 can only endorse SAAJ1.2 so there are special set of jars required to render WAS to support SAAJ1.3 that is used by recent CXF editions.

Here is the link
https://issues.apache.org/jira/browse/CXF-2725


thanks
Sid

---

From: Scott Cantor <>
To:
Sent: Mon, March 1, 2010 4:09:59 PM
Subject: RE: [OpenSAML] local part cannot be "null" when creating a QName during unmarshalling an Assertion object

> Thanks Scott for the great suggestion. However I checked and I am using
> SAAJ1.2 which is DOM2 compliant. Besides I have the JAXP (xercesImpl-
> 2.9.1.jar, xalan-2.7.1.jar, xml-apis-2.9.1.jar) that is OpenSAML2.3
> compatible. That being said, it is a good time to have my libraries
> verified. Anything that jumps out??

I didn't say your libraries weren't aware, I said your parsing code isn't.

> Also, how do I make this code namespace aware.
>
>    DefaultBootstrap.bootstrap();
>      // check for SOAP Header
>      SOAPHeader sh = smc.getMessage().getSOAPHeader();

None of that code has anything to do with the bug. Whatever is doing the XML
parsing is not using the proper settings before doing so.

-- Scott