[
https://issues.apache.org/jira/browse/ARTEMIS-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118399#comment-16118399
]
ASF GitHub Bot commented on ARTEMIS-1310:
-----------------------------------------
GitHub user gtully opened a pull request:
https://github.com/apache/activemq-artemis/pull/1449
[ARTEMIS-1310] SASL GSSAPI support
update to proton-j 0.20.0 and qpid-jms 0.24.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gtully/activemq-artemis sasl-gssapi
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1449.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1449
----
commit d4a281ed049acfa11b489ed43a06ba57669d7588
Author: gtully <[email protected]>
Date: 2017-07-28T15:02:32Z
[ARTEMIS-1310] add amqp sasl gssapi mechanism support
delegate to the jdk saslServer. Allow acceptor configuration of supported
mechanismis; saslMechanisms=<a,b>
and allow login config scope for krb5 to be configured via
saslLoginConfigScope=x
commit 1496b8c463eec9fbe385a8c9e4be7e9141018454
Author: gtully <[email protected]>
Date: 2017-08-02T11:19:07Z
[ARTEMIS-1310] [ARTEMIS-1264] consolidate configuration to require login
configuration scope
commit b551f9ea978eaf0607cd7b8c1567cc13d06031c8
Author: gtully <[email protected]>
Date: 2017-08-02T14:05:50Z
[ARTEMIS-1310] require mechanism to be explicitly enabled
----
> Provide GSSAPI (kerberos) SASL mechanism for AMQP
> -------------------------------------------------
>
> Key: ARTEMIS-1310
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1310
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.2.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 2.3.0
>
>
> implement GSSAPI sasl mechanism for AMQP transport allowing kerberos single
> sign on (authentication) and subsequent authorisation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)