HELP : AMQP and SSL Certificate

[Jeremy_DE_CAMPOS]

Hello @n8n @bartv

I need to communicate with an ActiveMQ stream.
For this, I’m going to use the AMQP node.
So far, so good

Except that the connection to this stream must be made via an SSL certificate… (the provider requires this).

And on this node, we don’t have the option to enable the SSL certificate.

I had the same problem with the API call, but with the HTTP Request node, we have the option (see below):

Is there another way to do this?
Is this a feature that could be developed natively? (That would be great)

Thanks for your feedback

[jabbson]

Hey @Jeremy_DE_CAMPOS hope all is well.

@Jeremy_DE_CAMPOS

For this, I’m going to use the AQMP node.

AMQP?

In my opinion, this is more of a Feature Request type of question. (UPR: which you already created here. So what is the reason for this separate post?

Is it possible? I don’t think it isn’t possible. Will this get in front of other features and bug fixes, which are already planned? It’s for the team to decide, but this isn’t how it usually works. But let’s of course wait and hear from the team.

[Jeremy_DE_CAMPOS]

@jabbson

AMQP?

In my opinion, this is more of a Feature Request type of question. (UPR: which you already created here. So what is the reason for this separate post?

Is it possible? I don’t think it isn’t possible. Will this get in front of other features and bug fixes, which are already planned? It’s for the team to decide, but this isn’t how it usually works. But let’s of course wait and hear from the team.

Yes, I made two posts.
The first is to see if the n8n team would be interested in this development.
The second (this post) is to see if the community has already encountered this issue and, if so, how to address it without necessarily developing this feature directly in Node.

For example, by adding the certificate to Docker, for example.

[jabbson]

If you are looking to add a custom certificate to the trust store for n8n to use? Then you can put them in /opt/custom-certificates.

Read this doc for more info:

Configure n8n to use your own certificate authority | n8n Docs

This is how you can make n8n trust extra certificates, which isn’t a part of the default installation.

[Jeremy_DE_CAMPOS]

Yes, I had come across that but will the AMQP node actually take the certificate into account?

[jabbson]

If the node accesses a service which uses it’s own certificate which isn’t globally verifiable, yes. If you need the certificate to use for mutual auth - then no.

[Jeremy_DE_CAMPOS]

The application that provides the ActiveMQ stream requires the connection to be with an SSL certificate.
They provide the public key and the certificate.
Basically, it’s like the HTTP request connection. I don’t know if you’ve already tried adding the certificate to the HTTP request node, but it’s the same.

[jabbson]

Ok, it is for client auth then. I don’t believe there is a way to enforce using client certificates for outgoing requests to a given domain, so I guess you could be stuck with http request node for this (at least until such functionality is natively integrated to the node in question.