[
https://issues.apache.org/jira/browse/RAMPART-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bridget Almas updated RAMPART-308:
----------------------------------
Attachment: rampart_receiver_patch
See attached patch file which tries first to get the faultCode from the source
exception, falling back to the current behavior setting it to InvalidSecurity
only if it wasn't able to retrieve it from the supplied exception.
> All security exceptions reported as wsse:InvalidSecurity
> --------------------------------------------------------
>
> Key: RAMPART-308
> URL: https://issues.apache.org/jira/browse/RAMPART-308
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.5
> Environment: N/A
> Reporter: Bridget Almas
> Assignee: Ruchith Udayanga Fernando
> Fix For: 1.5
>
> Attachments: rampart_receiver_patch
>
>
> It doesn't seem possible to get Rampart to return specific wsse fault codes
> other than wsse:InvalidSecurity.
> RampartReceiver.setFaultCodeAndThrowAxisFault() always sets the fault code as
> WSConstants.INVALID_SECURITY. This means that even if your callback handler
> returns a more specific Fault, such as wsse:FailedAuthentication, that always
> gets reported as a nested exception in the faultstring of a Fault with a
> faultcode of wsse:InvalidSecurity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
