coheigea wrote
> Thanks, this is now fixed:
> 
> http://svn.apache.org/viewvc/webservices/wss4j/trunk/ws-security-dom/src/?view=log

Thanks Colm, the same patch needs to be applied at 767 too:

diff --git
a/ws-security-dom/src/main/java/org/apache/wss4j/dom/processor/SignatureProcessor.java
b/ws-security-dom/src/main/java/org/apache
index 8f01968..795a7a7 100644
---
a/ws-security-dom/src/main/java/org/apache/wss4j/dom/processor/SignatureProcessor.java
+++
b/ws-security-dom/src/main/java/org/apache/wss4j/dom/processor/SignatureProcessor.java
@@ -764,7 +764,7 @@ public class SignatureProcessor implements Processor {

                 if (WSConstants.C14N_EXCL_OMIT_COMMENTS.equals(algorithm))
{
                     parameterSpec = transform.getParameterSpec();
-                    if (!(parameterSpec instanceof ExcC14NParameterSpec)) {
+                    if (parameterSpec != null && !(parameterSpec instanceof
ExcC14NParameterSpec)) {
                         bspEnforcer.handleBSPRule(BSPRule.R5407);
                     }
                 }







--
View this message in context: 
http://cxf.547215.n5.nabble.com/CXF-Service-can-t-process-PublicKey-SAML-Sender-Vouches-IssuedToken-in-WS-Policy-tp5739904p5740198.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to