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 2015/08/06 10:24:04 UTC
[jira] [Commented] (QPID-6606) Document the Java Broker's
AuthenticationProviders' behaviour regarding authentication mechanisms
[ https://issues.apache.org/jira/browse/QPID-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659677#comment-14659677 ]
ASF subversion and git services commented on QPID-6606:
-------------------------------------------------------
Commit 1694421 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1694421 ]
QPID-6606: [Java Broker Docs] Document the AuthenticationProviders' behaviour regarding authentication mechanisms
Work by Lorenz Quack <qu...@gmail.com>
> Document the Java Broker's AuthenticationProviders' behaviour regarding authentication mechanisms
> -------------------------------------------------------------------------------------------------
>
> Key: QPID-6606
> URL: https://issues.apache.org/jira/browse/QPID-6606
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker
> Reporter: Lorenz Quack
> Fix For: qpid-java-6.0
>
> Attachments: docs-secureonlymechanisms.diff
>
>
> The accepted authentication mechanisms of the AuthenticationProviders depend on the underlying transport. Notably, PLAIN is not accepted if the transport is not secured/encrypted.
> This is a security feature to prevent passwords being transfered in the clear.
> However, there is a way to override this and both these facts should be documented.
> This was discussed on the mailing list: http://qpid.2158936.n2.nabble.com/Runnig-python-examples-td7626255.html
--
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