You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2018/01/24 17:44:00 UTC

[jira] [Resolved] (QPIDJMS-361) request mutual auth for GSSAPI/Kerberos SASL

     [ https://issues.apache.org/jira/browse/QPIDJMS-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell resolved QPIDJMS-361.
------------------------------------
    Resolution: Fixed

> 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