Authentication backends (LDAP, OAuth) in RabbitMQ - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is LDAP in the context of RabbitMQ authentication?

LDAP (Lightweight Directory Access Protocol) is a protocol used to access and maintain distributed directory information services. In RabbitMQ, LDAP can be used as an authentication backend to verify user credentials against a central directory server.

intermediate

How does OAuth differ from LDAP as an authentication backend?

OAuth is an open standard for access delegation, often used for token-based authentication and authorization. Unlike LDAP, which verifies user credentials directly, OAuth allows RabbitMQ to accept tokens issued by an external identity provider to authenticate users.

beginner

Which RabbitMQ plugin enables LDAP authentication?

The rabbitmq_auth_backend_ldap plugin enables RabbitMQ to authenticate users against an LDAP server.

intermediate

What is a key benefit of using OAuth with RabbitMQ?

OAuth allows RabbitMQ to integrate with modern identity providers and supports single sign-on (SSO) and token-based authentication, improving security and user experience.

intermediate

Name one configuration setting needed to enable LDAP authentication in RabbitMQ.

You need to configure the LDAP server URL, for example: ldap_servers = ["ldap://ldap.example.com"] in the rabbitmq.conf file.

Which RabbitMQ plugin is required to use LDAP for authentication?

A rabbitmq_stomp

B rabbitmq_auth_backend_oauth2

C rabbitmq_management

D rabbitmq_auth_backend_ldap

The rabbitmq_auth_backend_ldap plugin enables LDAP authentication in RabbitMQ.

OAuth in RabbitMQ is primarily used for:

A Direct password verification

B Token-based authentication

C Message queue management

D Logging and monitoring

OAuth provides token-based authentication, allowing RabbitMQ to accept tokens from external identity providers.

LDAP stands for:

A Lightweight Data Authorization Process

B Local Directory Access Program

C Lightweight Directory Access Protocol

D Linked Data Access Protocol

LDAP stands for Lightweight Directory Access Protocol, used for directory services.

To configure LDAP in RabbitMQ, you must specify:

A LDAP server URL

B OAuth client secret

C RabbitMQ queue name

D Message TTL

LDAP server URL is required to connect RabbitMQ to the LDAP directory for authentication.

Which of the following is a benefit of using OAuth with RabbitMQ?

A Supports single sign-on (SSO)

B Requires direct password storage

C Only works with LDAP servers

D Disables token authentication

OAuth supports single sign-on (SSO) and token-based authentication, enhancing security.

Explain how LDAP authentication works in RabbitMQ and what configuration is needed.

Think about how RabbitMQ connects to an external directory to check user names and passwords.

Describe the advantages of using OAuth as an authentication backend in RabbitMQ.

Consider how OAuth uses tokens instead of passwords and works with external services.

Practice

1. What is the main purpose of using LDAP or OAuth as authentication backends in RabbitMQ?

easy

A. To allow RabbitMQ to verify users using external systems

B. To speed up message delivery between queues

C. To store messages persistently on disk

D. To enable RabbitMQ clustering automatically

Solution

1. Step 1: Understand authentication backends

   Authentication backends like LDAP or OAuth let RabbitMQ check user credentials against external systems.

2. Step 2: Identify the main purpose

   This helps centralize user management and improve security by not storing passwords locally.

3. Final Answer:

   To allow RabbitMQ to verify users using external systems -> Option A

4. Quick Check:

   Authentication backend purpose = Verify users externally [OK]

Hint: Authentication backends check users outside RabbitMQ [OK]

Common Mistakes:

• Confusing authentication with message delivery
• Thinking backends store messages
• Assuming backends manage clustering

2. Which of the following is the correct way to enable LDAP authentication backend in rabbitmq.conf?

easy

A. auth_backends.1 = ldap

B. auth_backends = [ldap]

C. auth_backends = ldap

D. auth_backends = {ldap}

Solution

1. Step 1: Recall RabbitMQ config syntax for backends

   RabbitMQ uses dotted notation for lists in auth_backends, such as auth_backends.1 = ldap.

2. Step 2: Identify correct syntax

   auth_backends.1 = ldap is the correct format.

3. Final Answer:

   auth_backends.1 = ldap -> Option A

4. Quick Check:

   Dotted notation auth_backends.N [OK]

Hint: Use dotted notation auth_backends.1 = ldap [OK]

Common Mistakes:

• Using square brackets [] like auth_backends = [ldap]
• Assigning string without numbering
• Using curly braces {}

3. Given this rabbitmq.conf snippet:

auth_backends.1 = ldap
ldap.servers.1 = ldap.example.com
ldap.user_dn_pattern = cn=${username},ou=users,dc=example,dc=com

What happens when a user tries to log in with username alice?

medium

A. RabbitMQ denies login because user_dn_pattern is missing

B. RabbitMQ uses local user database ignoring LDAP

C. RabbitMQ checks LDAP server at ldap.example.com using DN 'cn=alice,ou=users,dc=example,dc=com'

D. RabbitMQ tries OAuth authentication instead

Solution

1. Step 1: Analyze LDAP config parameters

   The config sets LDAP as backend and defines server and user DN pattern with ${username} placeholder.

2. Step 2: Substitute username in DN pattern

   For username 'alice', DN becomes 'cn=alice,ou=users,dc=example,dc=com'. RabbitMQ uses this to query LDAP server.

3. Final Answer:

   RabbitMQ checks LDAP server at ldap.example.com using DN 'cn=alice,ou=users,dc=example,dc=com' -> Option C

4. Quick Check:

   Username substitution in DN pattern = LDAP query [OK]

Hint: User DN pattern uses ${username} to query LDAP [OK]

Common Mistakes:

• Assuming local database is used
• Thinking user_dn_pattern is optional
• Confusing OAuth with LDAP backend

4. You configured OAuth as an authentication backend but RabbitMQ always rejects valid tokens. Which config mistake could cause this?

medium

A. Missing auth_backends.1 = oauth line

B. Incorrect OAuth server URL in config

C. Setting auth_backends.1 = ldap instead of OAuth

D. Using auth_backends = oauth without numbering

Solution

1. Step 1: Check OAuth backend config requirements

   OAuth backend needs correct server URL to validate tokens properly.

2. Step 2: Identify cause of token rejection

   If the OAuth server URL is wrong, RabbitMQ cannot validate tokens, causing rejections.

3. Final Answer:

   Incorrect OAuth server URL in config -> Option B

4. Quick Check:

   OAuth token validation needs correct server URL [OK]

Hint: Verify OAuth server URL to fix token validation [OK]

Common Mistakes:

• Forgetting to enable OAuth backend
• Using LDAP backend config for OAuth
• Ignoring numbering in list syntax

5. You want RabbitMQ to authenticate users first with LDAP, then fallback to OAuth if LDAP fails. How should you configure auth_backends in rabbitmq.conf?

hard

A. auth_backends = {ldap, oauth}

B. auth_backends.1 = oauth
auth_backends.2 = ldap

C. auth_backends = ldap
auth_backends = oauth

D. auth_backends.1 = ldap
auth_backends.2 = oauth

Solution

1. Step 1: Understand auth_backends order

   RabbitMQ tries backends in the order listed in auth_backends.

2. Step 2: Set LDAP first, OAuth second

   To try LDAP first, then OAuth, configure auth_backends.1 = ldap
auth_backends.2 = oauth.

3. Final Answer:

   auth_backends.1 = ldap auth_backends.2 = oauth -> Option D

4. Quick Check:

   Backend order controls fallback sequence [OK]

Hint: List backends in order of priority with auth_backends.1, .2 [OK]

Common Mistakes:

• Reversing backend order
• Using multiple auth_backends lines
• Using curly braces instead of brackets