[
https://issues.apache.org/jira/browse/CXF-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358236#comment-16358236
]
Colm O hEigeartaigh commented on CXF-3484:
------------------------------------------
Yes you need to store the clean text password somewhere on the receiving side
to compare against the received password. Alternatively, you can plug in a
custom Validator to do some custom validation. There is a
JAASUsernameTokenValidator available in WSS4J that validates the password using
a JAAS LoginModule for example.
> Password set to null in UsernameTokenValidator
> ----------------------------------------------
>
> Key: CXF-3484
> URL: https://issues.apache.org/jira/browse/CXF-3484
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.4
> Environment: Linux, jetty 6.10
> Reporter: Nicolas Poirot
> Priority: Minor
> Labels: UserNameToken, security
> Fix For: Invalid
>
>
> When trying to do basic authentication in Soap header with UserNameToken,
> token is well read from XML, but badly passed to password callback.
> Line 165 of org.apache.ws.security.validate.UsernameTokenValidator :
> WSPasswordCallback pwCb =
> new WSPasswordCallback(user, null, pwType,
> WSPasswordCallback.USERNAME_TOKEN, data);
> The password is set to null, while it has been correcty read just before.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
