|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I tried the work-a-around Nikolay recommended, but I had no luck.
When option #1 and #2 didn’t work by themselves, I tried both together. I couldn’t remove the following error when #2 is applied:
10:04:35,833 ERROR [org.apache.catalina.connector] (http-/0.0.0.0:8543-1) JBWEB001018: An exception or error occurred in the container during the request processing: java.lang.NoClassDefFoundError: org/w3c/dom/Node
at org.apache.jcp.xml.dsig.internal.dom.DOMXMLSignatureFactory.unmarshal(DOMXMLSignatureFactory.java:167) [xmlsec-1.5.3.jar:1.5.3]
…
Caused by: java.lang.ClassNotFoundException: org.w3c.dom.Node from [Module "org.apache.santuario.xmlsec:main" from local module loader @65e10e56 (finder: local module finder @1a74645b (roots: C:\Java\jboss-as-7.2.0.Final\modules,C:\Java\jboss-as-7.2.0.Final\modules\system\layers\base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.2.0.CR1]
I tried disabling all the modules in org.apache.santuario.xmlsec and adding them to my jboss-deployment-structure instead, however that didn’t work (same error as just disabling javax.api)
modules\system\layers\base\org\apache\santuario\xmlsec\main
<module xmlns="urn:jboss:module:1.1" name="org.apache.santuario.xmlsec">
…
<dependencies>
<!-- Attempt to get picketlink XMLSignatures working, what else will this break? <module name="javax.api" /> -->
<!-- Attempt to get picketlink XMLSignatures working, what else will this break? <module name="org.apache.commons.logging" /> -->
<!-- Attempt to get picketlink XMLSignatures working, what else will this break? <module name="org.apache.xalan" /> -->
</dependencies>
my-ear\src\main\application\META-INF\jboss-deployment-structure.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="javax.api" export="true" />
<module name="org.apache.commons.logging" export="true" />
<module name="org.apache.xalan" export="true" />
<module name="org.apache.santuario.xmlsec" export="true" />
<module name="org.picketlink" export="true" />
</dependencies>
</deployment>
</jboss-deployment-structure>
BTW, I noticed that ADFS is returning the SAML2 token as a POST (correction to my original post).
This issue is blocking an upgrade from JBoss6 to JBoss7.
If I downgrade from PicketLink 2.5.1.Final back to the picketlink 2.1.6 release included with JBoss7.2.0 will PicketLinkSP SupportsSignatures work with an ASFS STS?
I noticed that picketlink-installer-1.1.3.Final is available (I used picketlink-installer-1.1.2.Final). This upgrades picketlink-as-extension from 1.1.0.Final to 1.1.1.Final. Would re-installing picketlink on JBoss 7.2.0 with picketlink-installer-1.1.3.Final resolve this issue? Or allow work-a-around #1 to work?
Thanks,
Geoff