User and permission management in RabbitMQ - Step-by-Step Execution

Process Flow - User and permission management

Create User

↓

Set User Password

↓

Assign Permissions

↓

User Tries Access

↓

Permission Check

↓

Allow

This flow shows creating a user, setting a password, assigning permissions, and how access is allowed or denied based on those permissions.

Execution Sample

RabbitMQ

rabbitmqctl add_user alice secret123
rabbitmqctl set_permissions -p / alice ".*" ".*" ".*"
rabbitmqctl list_users

This code creates a user 'alice' with password 'secret123', grants full permissions on the default virtual host, and lists all users.

Process Table

Step	Command	Action	Result	System State Change
1	rabbitmqctl add_user alice secret123	Create user 'alice' with password	User 'alice' created	User 'alice' added to user list
2	rabbitmqctl set_permissions -p / alice ".*" ".*" ".*"	Set permissions for 'alice' on '/' vhost	Permissions set	'alice' can configure, write, read all resources on '/'
3	rabbitmqctl list_users	List all users	Listing users: alice	Shows 'alice'
4	User 'alice' tries to access queue	Check permissions	Access granted	Access allowed due to permissions
5	User 'bob' tries to access queue	Check permissions	Access denied	No user 'bob' found, access denied

💡 Execution stops after permission checks for users 'alice' and 'bob'.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5
Users	{}	{alice: password set}	{alice: permissions set}	{alice: permissions set}	{alice: permissions set}	{alice: permissions set}
Permissions for alice	N/A	N/A	Full on '/'	Full on '/'	Full on '/'	Full on '/'
Access attempt by alice	N/A	N/A	N/A	N/A	Granted	N/A
Access attempt by bob	N/A	N/A	N/A	N/A	N/A	Denied

Key Moments - 3 Insights

Why does 'alice' have access but 'bob' does not?

Because 'alice' was created and given permissions (see steps 1 and 2 in execution_table), while 'bob' does not exist in the system (step 5).

What does the permission pattern ".*" mean in set_permissions?

It means 'alice' can configure, write, and read all resources on the specified virtual host (step 2). This is a wildcard allowing full access.

Why do we need to set permissions after creating a user?

Creating a user only adds them to the system (step 1). Permissions define what they can do (step 2). Without permissions, access is denied.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of step 3?

A User 'alice' is deleted

B List of users including 'alice' is shown

C Permissions for 'alice' are removed

D Access denied for 'alice'

💡 Hint

Check the 'Result' column in step 3 of execution_table.

At which step does 'alice' get full permissions on the '/' virtual host?

A Step 2

B Step 1

C Step 4

D Step 5

💡 Hint

Look at the 'Action' and 'System State Change' columns in step 2.

If we try to access with a user not created, what happens according to the execution_table?

A Access granted

B User is automatically created

C Access denied

D Permissions are set automatically

💡 Hint

See step 5 in execution_table for 'bob' access attempt.

Concept Snapshot

rabbitmqctl add_user <user> <password>  # Create user
rabbitmqctl set_permissions -p <vhost> <user> <conf> <write> <read>  # Set permissions
Permissions control what user can do on resources
Without permissions, user cannot access
List users with rabbitmqctl list_users

Full Transcript

This visual execution shows how to manage users and permissions in RabbitMQ. First, a user is created with a password using 'rabbitmqctl add_user'. Then, permissions are assigned with 'rabbitmqctl set_permissions' specifying what the user can configure, write, and read on a virtual host. The system state updates to include the new user and their permissions. When the user tries to access resources, the system checks permissions and allows or denies access accordingly. If a user does not exist, access is denied. Listing users shows all created users and their tags. This step-by-step trace helps beginners understand how user creation and permission assignment work together to control access in RabbitMQ.

Practice

1. What is the primary purpose of RabbitMQ user management?

easy

A. To monitor message queue performance

B. To configure network settings for RabbitMQ

C. To control who can access RabbitMQ and what they can do

D. To backup RabbitMQ data automatically

Solution

1. Step 1: Understand user management role

   User management in RabbitMQ controls access by defining users who can connect.

2. Step 2: Understand permission role

   Permissions define what actions users can perform on queues and exchanges.

3. Final Answer:

   To control who can access RabbitMQ and what they can do -> Option C

4. Quick Check:

   User management = Access control [OK]

Hint: User management = who can do what in RabbitMQ [OK]

Common Mistakes:

• Confusing user management with monitoring
• Thinking permissions configure network
• Assuming user management handles backups

2. Which command correctly adds a new user named alice with password secret123 in RabbitMQ?

easy

A. rabbitmqctl new_user alice secret123

B. rabbitmqctl add_user alice secret123

C. rabbitmqctl user_add alice secret123

D. rabbitmqctl create_user alice secret123

Solution

1. Step 1: Recall RabbitMQ user creation syntax

   The correct command to add a user is rabbitmqctl add_user username password.

2. Step 2: Match command with options

   Only rabbitmqctl add_user alice secret123 matches the correct syntax exactly.

3. Final Answer:

   rabbitmqctl add_user alice secret123 -> Option B

4. Quick Check:

   add_user command adds user [OK]

Hint: Use add_user to create users, not create_user [OK]

Common Mistakes:

• Using create_user instead of add_user
• Swapping username and password order
• Using commands that don't exist

3. What will be the output of the following command if user bob has permissions to configure and write to all queues but no read permission?

rabbitmqctl list_user_permissions bob

medium

A. Config: .* Write: .* Read: ""

B. Config: "" Write: "" Read: ""

C. Config: .* Write: .* Read: .*

D. Config: .* Write: "" Read: .*

Solution

1. Step 1: Understand permission patterns

   Permissions use regex patterns: .* means all, "" means none.

2. Step 2: Match permissions to output

   Bob has configure and write permissions to all queues, so those are .*. No read permission means empty string "".

3. Final Answer:

   Config: .* Write: .* Read: "" -> Option A

4. Quick Check:

   Permissions regex = C [OK]

Hint: Empty quotes mean no permission, .* means full permission [OK]

Common Mistakes:

• Assuming missing permission shows as .*
• Confusing read and write permissions
• Misreading empty string as no permission

4. You run rabbitmqctl set_permissions -p / myuser ".*" ".*" ".*" but get an error saying user myuser does not exist. What is the most likely fix?

medium

A. Restart RabbitMQ server before setting permissions

B. Change the virtual host name from / to default

C. Remove the -p option from the command

D. Create the user first using rabbitmqctl add_user myuser password

Solution

1. Step 1: Understand error cause

   Setting permissions requires the user to exist first; error means user missing.

2. Step 2: Fix by creating user

   Use rabbitmqctl add_user myuser password to create the user before setting permissions.

3. Final Answer:

   Create the user first using rabbitmqctl add_user myuser password -> Option D

4. Quick Check:

   User must exist before permissions [OK]

Hint: Add user before setting permissions [OK]

Common Mistakes:

• Trying to set permissions on non-existent user
• Changing virtual host unnecessarily
• Restarting server without fixing user

5. You want to create a user carol who can only read from queues in the virtual host vhost1. Which sequence of commands correctly achieves this?

hard

A. rabbitmqctl add_user carol pass123rabbitmqctl set_permissions -p vhost1 carol "" "" ".*"

B. rabbitmqctl add_user carol pass123rabbitmqctl set_permissions -p vhost1 carol ".*" ".*" ".*"

C. rabbitmqctl add_user carol pass123rabbitmqctl set_permissions -p vhost1 carol ".*" "" ""

D. rabbitmqctl add_user carol pass123rabbitmqctl set_permissions -p vhost1 carol "" ".*" ""

Solution

1. Step 1: Create user carol

   Use rabbitmqctl add_user carol pass123 to add the user.

2. Step 2: Set read-only permissions

   Set configure and write permissions to empty string "", and read permission to ".*" for all queues in vhost1.

3. Final Answer:

   rabbitmqctl add_user carol pass123
   rabbitmqctl set_permissions -p vhost1 carol "" "" ".*" -> Option A

4. Quick Check:

   Read-only = config "", write "", read ".*" [OK]

Hint: Set empty config/write, full read permission for read-only user [OK]

Common Mistakes:

• Giving full permissions instead of read-only
• Mixing up permission order (config, write, read)
• Forgetting to specify virtual host