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.