> For the complete documentation index, see [llms.txt](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/messaging-technology/messaging-bus-comparison-series/comparision-13-authentication.md).

# Comparision #13: Authentication

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Product</td><td valign="top">Authentication Methods</td><td valign="top">Authorization</td></tr><tr><td valign="top">ActiveMQ</td><td valign="top"><p>·         Basic Authentication (Username/Password)</p><p>·         LDAP</p><p>·         OAuth 2.0</p><p>·         Client Certificates (TLS)</p><p>·         SimpleAuthenticationPlugin (XML-defined users)</p><p>·         JAAS (Java Authentication and Authorization Service)</p><p>·         SimpleAuthenticationPlugin (XML-defined users)</p><p>·         SCRAM (Salted Challenge Response Authentication Mechanism)</p><p>·         Custom plugins</p><p> </p></td><td valign="top"><p>·         ACL: JAAS, SimpleAuthorizationPlugin</p><p>·         Group-to-permission: activemq.xml</p></td></tr><tr><td valign="top">AWS SQS Queue</td><td valign="top"><p>·         AWS STS (temporary credentials)</p><p>·         Signature Version 4 (HMAC-SHA256)</p></td><td valign="top"><p>·         IAM identity-based policies</p><p>·         resource-based queue policies</p></td></tr><tr><td valign="top">Azure Queue Storage</td><td valign="top"><p>·         Azure Active Directory (Microsoft Entra ID)</p><p>·         Shared Access Signature (SAS)- for HTTP only</p><p>·         Account Keys</p><p>·         Managed Identity (for Azure services)</p></td><td valign="top"><p>·         Shared Key,</p><p>·         Shared Access Signatures (SAS)</p><p>·         Azure AD-based RBAC</p></td></tr><tr><td valign="top">Azure Service Bus</td><td valign="top"><p>·         Azure Active Directory (OAuth 2.0)</p><p>·         Shared Access Signature (SAS)</p><p>·         Managed Identity</p></td><td valign="top"><p>·         Azure AD</p><p>·         RBAC</p><p>·         Shared Access Signatures (SAS)</p></td></tr><tr><td valign="top">EMQX</td><td valign="top"><p>·         Basic Authentication (Username/Password)</p><p>·         LDAP (via HTTP Auth plugin)</p><p>·         OAuth 2.0</p><p>·         Client Certificates (TLS)</p><p>·         PSK (Pre-Shared Key)</p><p>·         SCRAM (Salted Challenge Response Authentication Mechanism)</p></td><td valign="top"><p>·         Supported backends include file, built-in database, MySQL, PostgreSQL, MongoDB, Redis, LDAP, HTTP, etc.</p><p>·         Authorizers can be chained for flexible permission checks</p></td></tr><tr><td valign="top">IBM MQ</td><td valign="top"><p>·         Basic Authentication (Username/Password)</p><p>·         LDAP integration (IDPWLDAP)<br>Authentication Token</p><p>·         OAuth 2.0</p><p>·         TLS mutual authentication</p><p>·         Operating System authentication (IDPWOS)</p><p>·         Security Exits &#x26; Custom Authentication logic</p></td><td valign="top"><p>·         Utilizes the Object Authority Manager (OAM) for object-level permissions.</p><p>·         Permissions (connect, put, get, admin) granted via setmqaut, MQSC commands, or OS-level/RACF settings.</p><p>·         Channel authorization and MCAUSER control additional access context</p></td></tr><tr><td valign="top">Kafka</td><td valign="top"><p>·         Basic Authentication (Username/Password)</p><p>·         OAuth 2.0</p><p>·         Client Certificates (TLS)</p><p>·         Kerberos</p><p>·         JAAS configuration</p><p>·         SCRAM (Salted Challenge Response Authentication Mechanism)</p></td><td valign="top"><p>·         Pluggable authorizer</p><p>·         ACLs</p></td></tr><tr><td valign="top">RabbitMQ</td><td valign="top"><p>·         Basic Authentication (Username/Password)</p><p>·         LDAP (via HTTP Auth plugin)</p><p>·         OAuth 2.0</p><p>·         Client Certificates (TLS)</p><p><br><br></p></td><td valign="top"><p>·         Supports authorization via vhost-level permissions: regex-based configure, write, and read patterns.</p><p>·         Authentication backends include internal users, LDAP, or OAuth2 JWT plugin.</p></td></tr><tr><td valign="top">Solace PubSub+</td><td valign="top"><p>·         Basic Authentication (Username/Password)</p><p>·         LDAP (via HTTP Auth plugin)</p><p>·         OAuth 2.0</p><p>·         Client Certificates (TLS)</p><p>·         RADIUS</p><p>·         Kerberos</p></td><td valign="top"><p>Client Profiles</p><p>ACL profiles</p><p>Queue Owner</p><p>OAuth JWT Token</p></td></tr><tr><td valign="top">Tibco EMS</td><td valign="top"><p>·         Basic Authentication (Username/Password)</p><p>·         LDAP (via HTTP Auth plugin)</p><p>·         OAuth 2.0</p><p>·         Client Certificates (TLS)</p><p>·         JAAS (for JMS)</p></td><td valign="top"><p>·         Supports ACL-based security via users.conf and acl.conf</p><p>·         Administered using tibemsadmin, granting permissions to users/groups for queues/topics (e.g., send/receive/browse)</p><p>·         OAuth JWT Token</p></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stephen-tsoi.gitbook.io/stephen-tsoi-docs/messaging-technology/messaging-bus-comparison-series/comparision-13-authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
