qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7292) Qpid clients should verify the server-final message when using SCRAM-* authentication
Date Tue, 07 Jun 2016 10:23:21 GMT

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

Keith Wall commented on QPID-7292:
----------------------------------

This is wider than the Java Client.  The Python client (pure python implementation) and the
Qpid JMS Client will be affected too.  The clients will need a switch so they can tolerate
older Broker that don't provide a server final message.

> Qpid clients should verify the server-final message when using SCRAM-* authentication
> -------------------------------------------------------------------------------------
>
>                 Key: QPID-7292
>                 URL: https://issues.apache.org/jira/browse/QPID-7292
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>            Reporter: Rob Godfrey
>
> QPID-7282 addressed the issue that the Java Broker was not sending the server-final message
in the SCRAM-* SASL exchange, however this omission was not causing the clients to fail, since
they blindly accept the server's acceptance of their credentials.
> Clients implementing SCRAM-* or similar protocols which include a client verification
step, should perform the verification of the server and fail or warn (to be configured by
a system property) if the verification does not occur or it fails.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message