[JBoss JIRA] (JBWS-3832) Different default Spring descriptor name for creating client and server Bus instances
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-3832:
-------------------------------------
Summary: Different default Spring descriptor name for creating client and server Bus instances
Key: JBWS-3832
URL: https://issues.jboss.org/browse/JBWS-3832
Project: JBoss Web Services
Issue Type: Feature Request
Components: jbossws-cxf
Reporter: Alessio Soldano
Fix For: jbossws-cxf-5.0
When Spring integration is enabled, the CXF Bus factory uses the same name to lookup descriptor defining the bus to be used for clients or endpoints (usually cxf.xml). Generally speaking, we might want to have the JAX-WS clients end up always using different Spring descriptors then any other consumer of the CXF Spring Bus factory.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months
[JBoss JIRA] (JBWS-3831) Failure of test org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3831?page=com.atlassian.jira.plugin.... ]
Alessio Soldano reopened JBWS-3831:
-----------------------------------
Assignee: Alessio Soldano (was: R Searls)
> Failure of test org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase
> -----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3831
> URL: https://issues.jboss.org/browse/JBWS-3831
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Reporter: R Searls
> Assignee: Alessio Soldano
>
> This test failure started with the switch to jbossws-cxf (5.0.0-SNAPSHOT).
> Only tests test2311 and test2321 in org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase are failing.
> ---
> test2321(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase):
> An error was discovered processing the <wsse:Security> header.
> test2311(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase):
> SAML token security failure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBWS-3831) Failure of test org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-3831?page=com.atlassian.jira.plugin.... ]
R Searls commented on JBWS-3831:
--------------------------------
There has been a change in the evaluation of the "bearer" signature checking in
the apache code. jbossws-cxf (5.0.0-SNAPSHOT) uses 2 updated apache archives,
<cxf.version>3.0.2-SNAPSHOT</cxf.version>
<wss4j.version>2.0.2-SNAPSHOT</wss4j.version>
(wss4j code repo: http://svn.apache.org/repos/asf/webservices/wss4j/trunk)
There was a major change in "bearer" signature identification in class, org.apache.wss4j.dom.processor.SAMLTokenProcessor. (log comment:
r1624049 | coheigea | 2014-09-10 12:06:15 -0400 (Wed, 10 Sep 2014) | 1 line
Record SAML Token signed results so that it can be used in SignedElements evaluation.
)
Below is the diff of the most current rev (r1624049) and the prev rev (r1609062)
(Used cmd svn diff -r 1609062 ./ws-security-dom/src/main/java/org/apache/wss4j/dom/processor/SAMLTokenProcessor.java
)
Lines starting with (-) is the prev and lines starting with (+) are the current.
There is a significant change starting with "SamlAssertionWrapper samlAssertion = new SamlAssertionWrapper(elem);"
@@ -76,8 +80,15 @@
Validator validator =
data.getValidator(new QName(elem.getNamespaceURI(), elem.getLocalName()));
- Credential credential = handleSAMLToken(elem, data, validator, wsDocInfo);
- SamlAssertionWrapper samlAssertion = credential.getSamlAssertion();
+
+ SamlAssertionWrapper samlAssertion = new SamlAssertionWrapper(elem);
+ XMLSignature xmlSignature =
+ verifySignatureKeysAndAlgorithms(samlAssertion, data, wsDocInfo);
+ List<WSDataRef> dataRefs = createDataRefs(elem, samlAssertion, xmlSignature);
+
+ Credential credential =
+ handleSAMLToken(samlAssertion, data, validator, wsDocInfo);
+ samlAssertion = credential.getSamlAssertion();
if (LOG.isDebugEnabled()) {
:
:
For these 2 "bearer" tests no signature is found in the message.
Evaluation is continuing to determine why this is true and how to resolve it.
> Failure of test org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase
> -----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3831
> URL: https://issues.jboss.org/browse/JBWS-3831
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Reporter: R Searls
> Assignee: R Searls
>
> This test failure started with the switch to jbossws-cxf (5.0.0-SNAPSHOT).
> Only tests test2311 and test2321 in org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase are failing.
> ---
> test2321(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase):
> An error was discovered processing the <wsse:Security> header.
> test2311(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase):
> SAML token security failure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBWS-3831) Failure of test org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-3831?page=com.atlassian.jira.plugin.... ]
R Searls commented on JBWS-3831:
--------------------------------
A server stacktrace of the failure.
15:13:20,723 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "jaxws-samples-wsse-policy-oasis-23x.war" (runtime-name : "jaxws-samples-wsse-policy-oasis-23x.war")
15:13:27,455 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-4) Interceptor for {http://www.jboss.org/jbossws/ws-extensions/wssecuritypolicy/oasis-samples}SecurityService has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: SAML token security failure
at org.apache.cxf.ws.security.wss4j.SamlTokenInterceptor.processToken(SamlTokenInterceptor.java:158)
at org.apache.cxf.ws.security.wss4j.AbstractTokenInterceptor.handleMessage(AbstractTokenInterceptor.java:111)
at org.apache.cxf.ws.security.wss4j.AbstractTokenInterceptor.handleMessage(AbstractTokenInterceptor.java:64)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307) [cxf-core.jar:3.0.2.SNAPSHOT]
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core.jar:3.0.2.SNAPSHOT]
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:243)
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:110)
at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:131)
at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:290)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:209)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136)
at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi.jar:3.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:259) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:246) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:75) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:165) [undertow-servlet-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:737) [undertow-core-1.1.0.Beta7.jar:1.1.0.Beta7]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: org.apache.wss4j.common.ext.WSSecurityException: SAML token security failure
at org.apache.wss4j.dom.validate.SamlAssertionValidator.verifySubjectConfirmationMethod(SamlAssertionValidator.java:165) [wss4j-ws-security-dom.jar:2.0.2-SNAPSHOT]
at org.apache.wss4j.dom.validate.SamlAssertionValidator.validate(SamlAssertionValidator.java:100) [wss4j-ws-security-dom.jar:2.0.2-SNAPSHOT]
at org.apache.wss4j.dom.processor.SAMLTokenProcessor.handleSAMLToken(SAMLTokenProcessor.java:162) [wss4j-ws-security-dom.jar:2.0.2-SNAPSHOT]
at org.apache.wss4j.dom.processor.SAMLTokenProcessor.handleToken(SAMLTokenProcessor.java:89) [wss4j-ws-security-dom.jar:2.0.2-SNAPSHOT]
at org.apache.cxf.ws.security.wss4j.SamlTokenInterceptor.processToken(SamlTokenInterceptor.java:206)
at org.apache.cxf.ws.security.wss4j.SamlTokenInterceptor.processToken(SamlTokenInterceptor.java:97)
... 42 more
> Failure of test org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase
> -----------------------------------------------------------------------------------------------------
>
> Key: JBWS-3831
> URL: https://issues.jboss.org/browse/JBWS-3831
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf
> Reporter: R Searls
> Assignee: R Searls
>
> This test failure started with the switch to jbossws-cxf (5.0.0-SNAPSHOT).
> Only tests test2311 and test2321 in org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase are failing.
> ---
> test2321(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase):
> An error was discovered processing the <wsse:Security> header.
> test2311(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase):
> SAML token security failure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBWS-3831) Failure of test org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase
by R Searls (JIRA)
R Searls created JBWS-3831:
------------------------------
Summary: Failure of test org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase
Key: JBWS-3831
URL: https://issues.jboss.org/browse/JBWS-3831
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf
Reporter: R Searls
Assignee: R Searls
This test failure started with the switch to jbossws-cxf (5.0.0-SNAPSHOT).
Only tests test2311 and test2321 in org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase are failing.
---
test2321(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase):
An error was discovered processing the <wsse:Security> header.
test2311(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase):
SAML token security failure
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBWS-3830) WSProvideTask "address" option not working
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3830?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3830:
----------------------------------
Description: When implementing JBWS-3510, we erroneously named "portSoapAddress" the additional field in WSProvideTask. That should have been "address". As a result the "address" option does not work. (was: When implementing JBWS-3510, we erroneously named "portSoapAddress" the additional fields in WSProvideTask. That should have been "address". As a result the "address" option does not work.)
> WSProvideTask "address" option not working
> ------------------------------------------
>
> Key: JBWS-3830
> URL: https://issues.jboss.org/browse/JBWS-3830
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, tools-jaxws
> Affects Versions: jbossws-cxf-4.1.0.Final
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Priority: Minor
> Fix For: jbossws-cxf-5.0
>
>
> When implementing JBWS-3510, we erroneously named "portSoapAddress" the additional field in WSProvideTask. That should have been "address". As a result the "address" option does not work.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months
[JBoss JIRA] (JBWS-3830) WSProvideTask "address" option not working
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3830?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3830:
----------------------------------
Description: When implementing JBWS-3510, we erroneously named "portSoapAddress" the additional fields in WSProvideTask. That should have been "address". As a result the "address" option does not work. (was: When implementing JBWS-3510, we erroneously called "portSoapAddress" the additional fields in WSProvideTask. That should have been "address". As a result the "address" option does not work.)
> WSProvideTask "address" option not working
> ------------------------------------------
>
> Key: JBWS-3830
> URL: https://issues.jboss.org/browse/JBWS-3830
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-cxf, tools-jaxws
> Affects Versions: jbossws-cxf-4.1.0.Final
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Priority: Minor
> Fix For: jbossws-cxf-5.0
>
>
> When implementing JBWS-3510, we erroneously named "portSoapAddress" the additional fields in WSProvideTask. That should have been "address". As a result the "address" option does not work.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 7 months