[
https://issues.apache.org/jira/browse/WSS-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved WSS-139.
-------------------------------------
Resolution: Invalid
> securementActions - UserTokenAction (dissapearing username)
> -----------------------------------------------------------
>
> Key: WSS-139
> URL: https://issues.apache.org/jira/browse/WSS-139
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Handlers
> Affects Versions: 1.5.4
> Environment: Java 1.5, Windows XP
> Reporter: Juliusz Brzostek
> Assignee: Ruchith Udayanga Fernando
>
> Hi All,
> 1. There is a problem with dissapearing username :(
> a) username is set on "" (empty string) in line 39 of UsernameTokenAction
> class,
> b) becouse in line 102 of Wss4jHandler i have not securementCallbackHandler,
> c) and else body is run (line 130 of Wss4jHandler), with:
> callback = new WSPasswordCallback("", WSPasswordCallback.UNKNOWN);
> Is there any reason to set ID with empty string instead of to use passed to
> method username?
> 2. Last changes in wss4j-1.5.4 has broken our integration tests :( To find a
> problem we spent much
> time, becouse no one imagine that is passible to change major things without
> upgrading version of library :(
> HTH
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
