cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-1632) Improve WS-Security error handling
Date Fri, 06 Jun 2008 18:10:46 GMT

     [ https://issues.apache.org/jira/browse/CXF-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-1632.
------------------------------

    Resolution: Fixed
      Assignee: Daniel Kulp

> Improve WS-Security error handling
> ----------------------------------
>
>                 Key: CXF-1632
>                 URL: https://issues.apache.org/jira/browse/CXF-1632
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 2.1, 2.0.6
>            Reporter: Colm O hEigeartaigh
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.1.1, 2.0.7
>
>         Attachments: cxf_1632.patch
>
>
> A number of minor changes are required to how error handling is implemented for WS-Security
in CXF. The SOAP Message security 1.1 specification (chapter 12 "Error Handling") details
standard fault strings and fault codes to be returned to the user in the event of an error,
something we don't always adhere to in the WSS4JInInterceptor.
> In particular, the WSS4JInInterceptor must be modified to catch "WSSecurityException"s
thrown by WSS4J, and populate and throw a SoapFault object accordingly. In addition, the content
of the SoapFault changes depending on whether SOAP 1.1 or 2.0 is used.
> Please review and apply the attached patch for this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message