You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/04/01 13:18:25 UTC
[jira] [Commented] (QPIDJMS-150) Scram SHA SASL support for
authentication
[ https://issues.apache.org/jira/browse/QPIDJMS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221561#comment-15221561 ]
ASF subversion and git services commented on QPIDJMS-150:
---------------------------------------------------------
Commit de9539de3f8c5bc8dfa31adebd2d891419a47650 in qpid-jms's branch refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=de9539d ]
QPIDJMS-150: update the config docs to include the new mechanisms
> Scram SHA SASL support for authentication
> -----------------------------------------
>
> Key: QPIDJMS-150
> URL: https://issues.apache.org/jira/browse/QPIDJMS-150
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Fix For: 0.9.0
>
> Attachments: 0001-QPIDJMS-150-Add-support-for-SASL-SCRAM-SHA1-256-RFC-.patch
>
>
> The SCRAM SHA-1 and 256 SASL mechanisms https://tools.ietf.org/html/rfc5802 offer better security than older SASL implementations. In particular the authentication information stored in the authentication database is not sufficient to impersonate the client if the database were to be stolen.
> (The Java Broker already supports these mechanisms. The intention is to switch to recommend SCRAM instead of CRAM-MD5 shortly. One barrier to making this switch is the absence of support in the client).
--
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