[ http://jira.codehaus.org/browse/XFIRE-387?page=comments#action_64951 ]
Brian Bonner commented on XFIRE-387: ------------------------------------ Thanks Tomasz. I noticed that WSS4J's UsernameToken has hashed as a default of true (again different from the oasis docs). and in the processing of UsernameToken it's not set back to false :( It looks like the handling is only handled for hashed as you said. I think there's a good opportunity to hook into external authentication modules, but currently the plain text password scenario is not fully cared for. > USERNAME_TOKEN is not validating password from PasswordCallback > --------------------------------------------------------------- > > Key: XFIRE-387 > URL: http://jira.codehaus.org/browse/XFIRE-387 > Project: XFire > Type: Bug > Versions: 1.1-RC1 > Environment: jdk1.5.0_06 > Reporter: Brian Bonner > Assignee: Tomasz Sztelak > Attachments: ws-security-testcase-patch.txt > > > Does the password use the callback value only if Digest is specified? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
