[
https://issues.apache.org/jira/browse/ARTEMIS-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076702#comment-16076702
]
ASF subversion and git services commented on ARTEMIS-1264:
----------------------------------------------------------
Commit cda1e018e1bd7ccd85d6ffd2333fc910b67febf5 in activemq-artemis's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=cda1e01 ]
ARTEMIS-1264 Foundation work for authentication with Kerberos using KRB_ cypher
suites.
Core client with netty connector and acceptor doing kerberos
jaas.doAs around sslengine init such that the SSL handshake can do kerberos
ticket
generaton and validation.
The kerberos authenticated user is then validated with the security manager
before
being populated into the message userId.
The feature is enabled with the kerb5Config property. When lowercase it is the
principal. With a leading uppercase char it is the login.config entry to use.
> 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)
