-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add RabbitMQ connection options #13071
Labels
Comments
tetofonta
added
needs triage
This issue has not been looked into
type: enhancement 🐺
labels
Jan 19, 2024
Would you like to create a PR for this issue? |
Deniks
added a commit
to Deniks/nest
that referenced
this issue
Jan 27, 2024
change socketOptions type from custom AmqpConnectionManagerSocketOptions to amqp-manager's AmqpConnectionOptions which allows to specify not only mTLS but also External auth Closes nestjs#13071
Deniks
added a commit
to Deniks/nest
that referenced
this issue
Jan 27, 2024
change socketOptions.connectionOptions type from any to amqp-manager's AmqpConnectionOptions which allows to specify not only mTLS but also External auth Closes nestjs#13071
12 tasks
Hey, i have created PR for this issue. |
let's track this here #13105 |
Deniks
added a commit
to Deniks/nest
that referenced
this issue
Jan 31, 2024
change socketOptions.connectionOptions type from any to copied amqp-manager's AmqpConnectionOptions Closes nestjs#13071
Closed
15 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
The RabbitMQ microservice client allows only the property relative to socket options to the underlying ampqlib as per line client/client-rmq.ts:136. There is no way to pass additional connection options like ssl certificates and client certificates or to specify a different authentication method like EXTERNAL.
Describe the solution you'd like
Add a key to RmqOptions or substitue RmqOptions#socketOptions with the full options object
Teachability, documentation, adoption, migration strategy
External Authentication method: Here
amqplib ssl example passing certificates to the connect handler: Here
amqplib ssl EXTERNAL auth example: Here
ampqlib EXTERNAL auth method issue: Here
What is the motivation / use case for changing the behavior?
Impossibility of integrating RabbitMQ inside an existing microservice architecture because RabbitMQ is configured with mTLS authentication.
The text was updated successfully, but these errors were encountered: