ReleaseBytes
aws AWS Big Data Blog ·

Amazon MQ for RabbitMQ Adds OAuth 2.0, LDAP, and HTTP Authentication

blogsecurityawsgaarchitect
feature

Amazon MQ for RabbitMQ now supports OAuth 2.0, LDAP, and HTTP-based authentication backends, allowing direct integration with existing enterprise identity infrastructure. This update eliminates the need to manage separate static RabbitMQ credentials, enhancing security and reducing operational overhead. The change centralizes user management, access control, and audit capabilities for better governance. This post details how each method functions, key configurations, and guidance for choosing the best fit for specific use cases.

  • →OAuth 2.0 Authentication for Token-Based Access
  • →LDAP Authentication for Directory Services Integration
  • →Flexible HTTP Authentication Backend for Custom Logic
Features (3) ›
  • OAuth 2.0 Authentication for Token-Based Access

    Clients can now obtain short-lived tokens from an identity provider and present them to the broker as bearer credentials. The broker validates these tokens using JSON Web Key Sets (JWKS) and derives permissions from token scopes, thereby eliminating the need for static broker credentials.

  • LDAP Authentication for Directory Services Integration

    The broker can delegate credential verification to an LDAP directory, such as Active Directory, enabling users to authenticate with their existing directory credentials. RabbitMQ permissions are mapped to LDAP group memberships, centralizing user management and applying existing password policies.

  • Flexible HTTP Authentication Backend for Custom Logic

    This approach allows the broker to delegate authentication and authorization decisions to an external HTTP service. This provides flexibility for implementing custom logic or integrating with identity systems that do not natively support OAuth 2.0 or LDAP.

Read the original announcement →

https://aws.amazon.com/blogs/big-data/oauth-2-0-ldap-and-http-auth-for-amazon-mq-for-rabbitmq/

Related releases