[
https://issues.apache.org/jira/browse/WSS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed WSS-391.
--------------------------
Resolution: Not A Problem
The functionality I was asking for is already available via
WSPasswordCallback.getUsage():
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/sts/src/demo/wssec/sts/STSCallbackHandler.java?revision=1344008&view=markup
> Create a PrivateKeyPasswordCallback for retrieval of server key passwords
> -------------------------------------------------------------------------
>
> Key: WSS-391
> URL: https://issues.apache.org/jira/browse/WSS-391
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Glen Mazza
> Assignee: Colm O hEigeartaigh
> Fix For: 2.0
>
>
> WSS4J presently relies on the same org.apache.ws.security.WSPasswordCallback
> for retrieval of UsernameToken passwords and server private key passwords,
> requiring separate callback handlers to be configured for each task.
> Recommend creation of a non-backwards compatible PrivateKeyPasswordCallback
> (or whatever named) for retrieval of server key passwords. When used with
> the instanceof operator (by checking the precise callback type being
> requested), this will allow the developer the option of using the same
> CallbackHandler to handle retrieval of both the private key password and any
> UsernameToken passwords.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
