[
https://issues.apache.org/jira/browse/WSS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072302#comment-13072302
]
Colm O hEigeartaigh commented on WSS-251:
-----------------------------------------
Hi Pavel,
Yes, there will be support in 1.6.2 for the Kerberos Token Profile. I'm not
planning to support using the secret key to encrypt/sign data until 1.6.3
though.
I hadn't seen the 1.5.3 Kerberos port. I've taken a different approach in 1.6.2
- I'm not planning to support this via WS-Handler, although if there is demand
for it I will reconsider. On the outbound side there is a new BinarySecurity
type (KerberosSecurity) that provides a method to obtain a Kerberos Token. It's
up to the user to call this method and deal with the token accordingly. CXF
2.4.2-SNAPSHOT does this, and currently supports the KerberosToken Security
Policy as as SupportingToken and SignedSupportingToken.
Colm.
> Support WSS Kerberos Token Profile
> ----------------------------------
>
> Key: WSS-251
> URL: https://issues.apache.org/jira/browse/WSS-251
> Project: WSS4J
> Issue Type: New Feature
> Reporter: Christian Schneider
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6.2
>
>
> Currently wss4j does not support the kerberos token profile.
> In most windows enterprise environments and in some unix environments
> kerberos is available by default. So it would be nice to have this feature to
> allow single sign on for clients to e.g. webservices.
> I can post sample code that shows how to create a service ticket on the
> client and how to validate it on the server. Would this help?
--
This message is automatically generated by JIRA.
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]
