[
https://issues.apache.org/jira/browse/CXF-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved CXF-5748.
--------------------------------------
Resolution: Fixed
> Improve WS-Security Kerberos configuration
> ------------------------------------------
>
> Key: CXF-5748
> URL: https://issues.apache.org/jira/browse/CXF-5748
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Affects Versions: 2.7.11, 3.0.0
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Priority: Minor
> Fix For: 2.7.12, 3.0.1
>
>
> Configuring Kerberos with WS-Security is currently a bit more cumbersome than
> it needs to be on the client side. The user must create a KerberosClient
> Object, set the JAAS Context + service name / CallbackHandler on it, and set
> it as a JAX-WS property.
> For Spnego on the other hand, we can simply use the
> "ws-security.kerberos.jaas.context", "ws-security.kerberos.spn" and standard
> "ws-security.callback-handler" properties. This task is to allow this when
> working with Kerberos as well.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
