Bug 1111046

Summary: [GSS] (6.3.x) CXF-5810 - Empty response returned when SOAP fault is thrown from an endpoint having WS-Security policy signature profile
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Tadayoshi Sato <tasato>
Component: Web ServicesAssignee: Alessio Soldano <asoldano>
Status: CLOSED CURRENTRELEASE QA Contact: Rostislav Svoboda <rsvoboda>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.3CC: bbaranow, istudens, jawilson, jbliznak, klape, myarboro
Target Milestone: CR1Keywords: Triaged
Target Release: EAP 6.3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
This release of JBoss EAP 6 contains a bug that causes a web service that has a WS-Security Signature policy in its WSDL to return an empty HTTP response that has zero-length of content to client when throws a SOAP Fault instead of the actual SOAP Fault. This issue presents only when Signature policy is in use. This is expected to be resolved in a future release of the product.
 Story Points: ---
Clone Of: 1110631
: 1111048 (view as bug list) Environment:
Last Closed: 2019-08-19 12:42:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1110631    
Bug Blocks: 1111518, 1115216, 1132166, 1144103    
Attachments:
Description Flags
Reproducer none

Description Tadayoshi Sato 2014-06-19 06:37:06 UTC 
+++ This bug was initially created as a clone of Bug #1110631 +++

Description of problem:
Platform BZ for https://issues.jboss.org/browse/JBWS-3802

Please port CXF-5810, which is the root cause of the issue, to JBoss WS.

When a web service has a WS-Security Signature policy in its WSDL and throws a SOAP Fault, it returns an empty HTTP response that has zero-length of content to client instead of the SOAP Fault.

This happens only with Signature policy and doesn't happen with any other WS-Security policies like UsernameToken, or without WS-Security.


How reproducible:
100%

Steps to Reproduce:
1. From the base maven project run:
   > mvn clean install jboss-as:deploy
2. Then run:
   > mvn clean test -Pjbossas-remote

Actual results:
- The reproducer client gets empty response from the endpoint.

Expected results:
- The reproducer client should get a SOAP Fault from the endpoint.
Comment 1 Tadayoshi Sato 2014-06-19 06:49:57 UTC 
Created attachment 910271 [details]
Reproducer
Comment 2 JBoss JIRA Server 2014-07-21 15:52:43 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3802 to Resolved
Comment 3 baranowb 2014-08-07 11:55:12 UTC 
wrong issue, reverting.
Comment 5 Jan Blizňák 2014-10-16 10:30:12 UTC 
Verified on 6.3.2.CP.CR1
Comment 6 JBoss JIRA Server 2015-04-25 20:26:35 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3802 to Closed