[
https://issues.apache.org/jira/browse/QPIDJMS-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095026#comment-16095026
]
ASF GitHub Bot commented on QPIDJMS-303:
----------------------------------------
GitHub user gtully opened a pull request:
https://github.com/apache/qpid-jms/pull/10
[QPIDJMS-303] implement sasl gssapi (kerberos) mechanism
Using the current username or configured url prams the current kerberos
credential
is propagated via sasl gssapi mechanism. the default server principal is
amqp/<hostName>@<REALM>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gtully/qpid-jms-1 QPIDJMS-303
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-jms/pull/10.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 #10
----
commit 4ba8b7d954171b357c5552203ee2960434403fad
Author: gtully <[email protected]>
Date: 2017-07-20T16:55:07Z
[QPIDJMS-303] implement sasl gssapi (kerberos) mechanism
Using the current username or configured url prams the current kerberos
credential
is propagated via sasl gssapi mechanism. the default server principal is
amqp/<hostName>@<REALM>
----
> Add support for SASL GSSAPI Kerberos mechanism
> ----------------------------------------------
>
> Key: QPIDJMS-303
> URL: https://issues.apache.org/jira/browse/QPIDJMS-303
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Reporter: Gary Tully
>
> It would be great to be able to authenticate using kerberos credentials using
> the SASL GSSAPI mechanism.
> Authentication would be sufficient leaving TLS to do encryption of the
> channel if that is necessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
