qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gordon Sim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3246) JMS client on 0-10 codepath sets chosen mech to PLAIN by default
Date Mon, 09 May 2011 14:43:03 GMT

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

Gordon Sim commented on QPID-3246:

"The JMS client does look at the mech list supported by the broker and will compile a list
of mutually supported mechs." - doesn't seem to. It seems to have PLAIN set as the client-side

"Except for PLAIN (and CRAMMD5) every other mechanism needs explicit configuration (Ex KERBEROS,
EXTERNAL), therefore specifying the mech explicitly isn't too much trouble either. Infact
it's probably better to specify the mech explicitly in the case." - not entirely true, ANONYMOUS
for example does not need any configuration. CRAM-MD5 likewise does not get chosen unless
explicitly set, even if that is the only mutually supported mechanism.

> JMS client on 0-10 codepath sets chosen mech to PLAIN by default
> ----------------------------------------------------------------
>                 Key: QPID-3246
>                 URL: https://issues.apache.org/jira/browse/QPID-3246
>             Project: Qpid
>          Issue Type: Improvement
>            Reporter: Gordon Sim
> would be better to allow the underlying sasl libraries to determine the available mechs
from those registered. As it is, changing from PLAIN requires expcliti client configuration
for java - there is no negotiation by default.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message