cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-3484) Password set to null in UsernameTokenValidator
Date Tue, 03 May 2011 09:59:03 GMT

    [ https://issues.apache.org/jira/browse/CXF-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028134#comment-13028134
] 

Colm O hEigeartaigh commented on CXF-3484:
------------------------------------------


This is not a bug. The job of the password callback is to supply a password to the validator
for the given user, so why would it need to know the password that has been received?

Colm.

> 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
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message