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

Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2014/10/04 23:53:33 UTC

[jira] [Updated] (WSS-514) Missing CUSTOM_TOKEN action in WSSecurityUtil#decodeHandlerAction @l961

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

Colm O hEigeartaigh updated WSS-514:
------------------------------------
    Fix Version/s: 2.0.3

> Missing CUSTOM_TOKEN action in WSSecurityUtil#decodeHandlerAction @l961
> -----------------------------------------------------------------------
>
>                 Key: WSS-514
>                 URL: https://issues.apache.org/jira/browse/WSS-514
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Core
>    Affects Versions: 2.0.1
>            Reporter: bounkong khamphousone
>            Assignee: Colm O hEigeartaigh
>            Priority: Minor
>             Fix For: 2.0.3
>
>
> While setting action "CustomToken", to the wss4jOutInterceptor, it is not able to resolve the string CustomToken as defined in ConfigurationConstant. We are still able to use the customtokenaction with the integer defined in wsconstants.
> I think the decodehandler has to add CustomToken in it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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