You are viewing a plain text version of this content. The canonical link for it is here.

Posted to rampart-dev@ws.apache.org by "Bridget Almas (JIRA)" <ji...@apache.org> on 2010/09/13 21:14:33 UTC

[jira] Updated: (RAMPART-308) All security exceptions reported at wsse:InvalidSecurity

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

Bridget Almas updated RAMPART-308:
----------------------------------

    Description: 
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.

  was:
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 faulcode of wsse:InvalidSecurity.


> All security exceptions reported at 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
>
>
> 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.