[ 
https://issues.apache.org/jira/browse/ARTEMIS-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797239#comment-17797239
 ] 

Robbie Gemmell edited comment on ARTEMIS-4538 at 12/15/23 4:21 PM:
-------------------------------------------------------------------

The documentation has a specific note already that the TLS config for broker 
connections is in fact not configured differently than any other broker TLS 
connection config, just in case anyone should assume they were for $reasons I 
dont understand. There is also already a specific example referenced showing 
how to configure TLS for an amqp broker connection: 
[https://github.com/apache/activemq-artemis-examples/tree/main/examples/features/broker-connection/amqp-sending-overssl.]

[https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html#amqp-server-connections]

"Note that the connection URI options for transport settings such as enabling 
and configuring TLS are common with other Artemis connector URIs. See [the 
transport 
doc|https://activemq.apache.org/components/artemis/documentation/latest/configuring-transports.html#configuring-netty-ssl]
 for more. An example configuration for a TLS AMQP broker-connection can be 
found in the broker examples at 
./examples/features/broker-connection/amqp-sending-overssl."

 

(The example reference could be updated for 2.32.0 to point to the new examples 
repo, I'll take of that under ARTEMIS-4533)


was (Author: gemmellr):
The documentation has a specific note already that the TLS config for broker 
connections is in fact not configured differently than any other broker TLS 
connection config, just in case anyone should assume they were for $reasons I 
dont understand. There is also already a specific example showing how to 
configure TLS for an amqp broker connection: 
[https://github.com/apache/activemq-artemis-examples/tree/main/examples/features/broker-connection/amqp-sending-overssl.]

https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html#amqp-server-connections

"Note that the connection URI options for transport settings such as enabling 
and configuring TLS are common with other Artemis connector URIs. See [the 
transport 
doc|https://activemq.apache.org/components/artemis/documentation/latest/configuring-transports.html#configuring-netty-ssl]
 for more. An example configuration for a TLS AMQP broker-connection can be 
found in the broker examples at 
./examples/features/broker-connection/amqp-sending-overssl.

 

(The example reference could be updated for 2.32.0 to point to the new examples 
repo, I'll take of that under ARTEMIS-4533)

> Update mirroring documentation to clarify format of mirroring connection URIs
> -----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4538
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4538
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>            Reporter: John Clifford
>            Priority: Major
>
> The [Artemis 
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html]
>  explains how to make a connection for mirroring using the 
> {{<amqp-connection>}} configuration. However, it isn't clear what format the 
> connection URI takes. In particularly, it isn't clear how to configure it to 
> use TLS.
> I understand that the URI format is, in fact, the same as that used by other 
> Artemis network connections. I would not have guessed this, because Artemis 
> does not use AMQP for any of these other connections, and I just assumed that 
> AMQP mirroring connections would be configured differently.
> So I think all that is needed here is one additional line explaining this, 
> and perhaps linking to the relevant section of the docs. A specific example 
> of configuring a mirror connection using TLS would, I think, provide useful 
> additional help.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to