Skip to content

use SASL EXTERNAL for RabbitMQ AMQP TLS without credentials #1727

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.

Sign up for GitHub

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

Open
rickbrouwer wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −1
Open

use SASL EXTERNAL for RabbitMQ AMQP TLS without credentials #1727

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion content/docs/2.20/scalers/rabbitmq-queue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,9 @@ This allows sensitive credentials to be stored and managed separately from the c
- `cert` - Certificate for client authentication (optional).
- `key` - Certificate Key for client authentication (optional).

> 💡 **Note:** Using RabbitMQ host with AMQPS protocol will require enabling the TLS settings and passing the required parameters.
> 💡 **Notes:**
Copy link
Copy Markdown
Contributor

@dttung2905 dttung2905 Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should address this and update the doc accordingly kedacore/keda@e5c66bb#r3053338950

Copy link
Copy Markdown
Member Author

@rickbrouwer rickbrouwer May 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you make a code proposal @dttung2905 ?

> - Using RabbitMQ host with AMQPS protocol will require enabling the TLS settings and passing the required parameters.
> - When using certificate-based authentication (SASL EXTERNAL via the `rabbitmq_auth_mechanism_ssl` plugin), omit `username` and `password` from both the `host` URI and `TriggerAuthentication`. KEDA will automatically use SASL EXTERNAL when TLS is enabled and no credentials are present. RabbitMQ will derive the user identity from the CN field of the client certificate.

#### Azure Workload Identity authentication

Expand Down
Loading