[
https://issues.apache.org/jira/browse/RAMPART-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583029#comment-13583029
]
Ronnie Kilsbo commented on RAMPART-205:
---------------------------------------
I have stumbled upon this issue now as well. I cannot find any way to apply
custom Validators, and since WSS4J deprecated
WSPasswordCallback.USERNAME_TOKEN_UNKNOWN and made
WSPasswordCallback.getPassword() forever null, I fail to see how I can
authenticate UsernameToken at all.
There is the policyValidatorCbClass configuration option in rampart
configuration but, as far as I know you can only get the results of the default
validators in use within WSS4J.
Would love a feature to apply custom Validators, as it is now, I'm forced to
use transport level authentication with Rampart.
> Setting WSSConfig properties from RampartConfig
> -----------------------------------------------
>
> Key: RAMPART-205
> URL: https://issues.apache.org/jira/browse/RAMPART-205
> Project: Rampart
> Issue Type: Improvement
> Reporter: Frode Laukus
> Priority: Minor
>
> I believe it's not currently possible to set properties on WSS4J WSSConfig
> using the RampartConfig. I think it would be a nice improvement to be able to.
> One example is WSSConfig.HANDLE_CUSTOM_PASSWORD_TYPES which I recently found
> I would have liked being able to set to true, being default false.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
