[jira] Commented: (WSS-229) UsernameTokenProcessor should be able to act as a UsernameToken parser only and not enforce the validation of passwords

["Marcin Markiewicz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WSS-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972091#action_12972091 ] 

Marcin Markiewicz commented on WSS-229:
---------------------------------------

Hello,
I had the same problem, but could solve it by using my own password type. In this case wss4j reads the values only and does not check it against anything. But the sender and receiver must both know the new type... And wss4j must be set to allow own password types.

> UsernameTokenProcessor should be able to act as a UsernameToken parser only and not enforce the validation of passwords  
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WSS-229
>                 URL: https://issues.apache.org/jira/browse/WSS-229
>             Project: WSS4J
>          Issue Type: Improvement
>          Components: WSS4J Core
>            Reporter: Sergey Beryozkin
>            Assignee: Ruchith Udayanga Fernando
>             Fix For: 1.6
>
>         Attachments: wss-229-1.patch
>
>
> UsernameTokenProcessor enforces the validation of passwords. In some cases it could be advantageous to use it only as a token parser creating a principal, ex, when it is used explicitly from a custom code.  In such cases, the custom code can proceed with validating the username token details as needed.
>  

-- 
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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org