[
https://issues.apache.org/jira/browse/QPID-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030746#comment-13030746
]
Rajith Attapattu 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.
If there are no matching mechs an exception will be thrown.
The client then creates it's SASL client based on the compatible set of mechs
and will check to see if there is an initial response. I suspect that this step
will always pick PLAIN if it was in the mix. Is that the issue here ?
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.
Perhaps I misunderstood your point. Could you explain the circumstances behind
the issue?
> 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:[email protected]
