Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6FEBA10253 for ; Tue, 11 Feb 2014 23:02:25 +0000 (UTC) Received: (qmail 51556 invoked by uid 500); 11 Feb 2014 23:02:20 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 51239 invoked by uid 500); 11 Feb 2014 23:02:20 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 51017 invoked by uid 99); 11 Feb 2014 23:02:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Feb 2014 23:02:20 +0000 Date: Tue, 11 Feb 2014 23:02:20 +0000 (UTC) From: "Ted Leung (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CXF-5540) Add a flag to return the security cause error in a SOAP Fault MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898458#comment-13898458 ] Ted Leung edited comment on CXF-5540 at 2/11/14 11:00 PM: ---------------------------------------------------------- I think I instigated this issue, but I think the issue description is not accurate. I believe it should say something like : currently a WSSecurityException is mapped to a SOAPFaultException and SoapFault before leaving the server. This means the client side never knows a WSSecurityException occurred, only that a SOAPFaultException and SoapFault occurred. The desire is to have the client receive a WSSecurityException instead of a SOAPFaultException, or to have at least the "cause" of the of SOAPFaultException contain a chain to WSSecurityException. The original desire/concern has nothing to do with the message in side the exception, it's the desire to have the WSSecurityException class actually thrown to the client. was (Author: r6squeegee@gmail.com): I think I instigated this issue, but I think the issue description is not accurate. I believe it should say something like : currently a WSSecurityException is mapped to a SOAPFaultException and SoapFault before leaving the server. This means the client side never knows a WSSecurityException occurred, only that a SOAPFaultException and SoapFault occurred. The desire is to have the client receive a WSSecurityException instead of a SOAPFaultException, or to have at least the "cause" of the of SOAPFaultException contain a chain to WSSecurityException. The original desire/concern has nothing to do with the message in side the exception, it's the desire to have the Exception class actually thrown. > Add a flag to return the security cause error in a SOAP Fault > ------------------------------------------------------------- > > Key: CXF-5540 > URL: https://issues.apache.org/jira/browse/CXF-5540 > Project: CXF > Issue Type: Improvement > Components: WS-* Components > Affects Versions: 2.7.9 > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 3.0.0-milestone2 > > > Currently a security exception message is mapped to a standard error message. This task is to add a boolean configuration flag to allow a server to return the root cause message to the client (for diagnosis etc.). The default will be to only return the generic message. -- This message was sent by Atlassian JIRA (v6.1.5#6160)