axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (RAMPART-308) All security exceptions reported as wsse:InvalidSecurity
Date Tue, 21 Dec 2010 14:10:00 GMT

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

Samisa Abeysinghe reassigned RAMPART-308:
-----------------------------------------

    Assignee: Samisa Abeysinghe  (was: Ruchith Udayanga Fernando)

> 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: Samisa Abeysinghe
>             Fix For: NextVersion
>
>         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.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message