[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074589#comment-16074589
]
Gary Tully edited comment on ARTEMIS-1264 at 7/5/17 12:38 PM:
--------------------------------------------------------------
next steps:
- ensure mapping from kerberos principal to broker identity is locked down
- ensure jms client config is trivial
- validate broker side ticket expiry and renewal
- work with qpid-jms to validate amqp client
- validate with non java - proton-c client
was (Author: gtully):
next steps:
- ensure jms client config is trivial
- validate broker side ticket expiry and renewal
- work with qpid-jms to validate amqp client
- validate with non java - proton-c client
> Client authentication via Kerberos TLS Cipher Suites (RFC 2712)
> ---------------------------------------------------------------
>
> Key: ARTEMIS-1264
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1264
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 2.1.0
> Reporter: Gary Tully
> Assignee: Gary Tully
>
> Allow a client authenticated with a kerberos credential to authenticate to
> the broker using SSL via the Kerberos cipher suites.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
