[
https://issues.apache.org/jira/browse/ARTEMIS-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226821#comment-17226821
]
Robbie Gemmell commented on ARTEMIS-2971:
-----------------------------------------
I moved the comment above about behaviour when failing to agree a common SASL
mech out to its own Jira: ARTEMIS-2977
> outgoing 'server-connection' doesnt support ANONYMOUS or EXTERNAL SASL
> mechanisms
> ---------------------------------------------------------------------------------
>
> Key: ARTEMIS-2971
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2971
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.16.0
> Reporter: Robbie Gemmell
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.17.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The broker supports using ANONYMOUS and EXTERNAL (and PLAIN) SASL mechanisms
> for connecting AMQP clients to the broker. However, it doesnt support either
> for the outgoing 'server-connection' feature to have the broker establish
> connections to other servers. This means an Artemis broker may be unable to
> connect to another Artemis broker using this feature, depending on its
> configuration.
> The broker currently only supports using PLAIN if a user+pass is supplied for
> the outgoing connection, or using a raw AMQP (no SASL) connection if no
> user+pass is supplied. This means the broker cant connect to a server unless
> it either offers PLAIN, or accepts bare AMQP without SASL auth (which some
> dont, e.g I think ActiveMQ 5 by default at least).
>
> EXTERNAL is going to be fairly desirable for such use cases. Using SASL
> ANONYMOUS for connections without user+pass/EXTERNAL woud be a more typical
> default, but it should at least be supported if not the default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
