qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-361) request mutual auth for GSSAPI/Kerberos SASL
Date Wed, 24 Jan 2018 17:41:00 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337950#comment-16337950
] 

ASF subversion and git services commented on QPIDJMS-361:
---------------------------------------------------------

Commit bb5abafc145f32c60c90f5c8009ca2e2e55a2406 in qpid-jms's branch refs/heads/master from
[~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=bb5abaf ]

QPIDJMS-361: request mutual auth for GSSAPI/Kerberos SASL


> request mutual auth for GSSAPI/Kerberos SASL
> --------------------------------------------
>
>                 Key: QPIDJMS-361
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-361
>             Project: Qpid JMS
>          Issue Type: Improvement
>          Components: qpid-jms-client
>    Affects Versions: 0.29.0
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 0.30.0
>
>
> The JMS client does not currently request mutual-auth when authenticating via GSSAPI/Kerberos,
since this is not performed by default by the JVMs SaslServer impl. The cyrus-sasl usage of
proton-c and qpid-cpp clients for GSSAPI does result in mutual-auth, where it seems it is
performed by default by Cyrus. The JMS client should be updated to match, making their behaviour
consistent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message