Authorization strategies (Matrix, role-based) in Jenkins - Step-by-Step Execution

Process Flow - Authorization strategies (Matrix, role-based)

Start: User Access Request

↓

Check Authorization Strategy

↓

Matrix Strategy

↓

Check User Permissions

↓

Allow or Deny Access

↓

Access Granted or Denied

When a user requests access, Jenkins checks which authorization strategy is active. It either checks detailed permissions per user (Matrix) or checks user roles (Role-Based) to allow or deny access.

Execution Sample

Jenkins

matrixAuthorizationStrategy {
  permission('hudson.model.Item.Build', 'alice')
  permission('hudson.model.Item.Read', 'bob')
}
roleBasedAuthorizationStrategy {
  role('admin', ['alice'])
  role('developer', ['bob'])
}

Defines permissions for users using matrix and roles for role-based authorization.

Process Table

Step	User	Authorization Strategy	Check	Result	Access Outcome
1	alice	Matrix	Check if 'Build' permission granted	Yes	Access Allowed
2	bob	Matrix	Check if 'Build' permission granted	No	Access Denied
3	bob	Matrix	Check if 'Read' permission granted	Yes	Access Allowed
4	alice	Role-Based	Check if user in 'admin' role	Yes	Access Allowed
5	bob	Role-Based	Check if user in 'admin' role	No	Access Denied
6	bob	Role-Based	Check if user in 'developer' role	Yes	Access Allowed
7	charlie	Matrix	Check permissions	No	Access Denied
8	charlie	Role-Based	Check roles	No	Access Denied

💡 Access is granted only if the user has the required permission (Matrix) or belongs to the required role (Role-Based).

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 6	Final
alice_permissions	{}	{Build}	{Build}	{Build}	{Build}
bob_permissions	{}	{}	{Read}	{Read}	{Read}
alice_roles	{}	{admin}	{admin}	{admin}	{admin}
bob_roles	{}	{}	{}	{developer}	{developer}
charlie_permissions	{}	{}	{}	{}	{}
charlie_roles	{}	{}	{}	{}	{}

Key Moments - 3 Insights

Why does bob get denied access when checking 'Build' permission in Matrix strategy?

Because bob only has 'Read' permission, not 'Build'. The execution_table row 2 shows the check fails and access is denied.

How does Role-Based strategy simplify permission management?

It groups users into roles with predefined permissions. For example, alice is in 'admin' role (row 4), so she gets access without checking individual permissions.

What happens if a user is not assigned any permissions or roles?

They are denied access by default, as shown for charlie in rows 7 and 8.

Visual Quiz - 3 Questions

Look at the execution table, what permission does alice have in the Matrix strategy at step 1?

A 'Read'

B 'Build'

C 'Admin'

D No permissions

💡 Hint

Check the 'Check' and 'Result' columns in row 1 of the execution_table.

At which step does bob get access denied in Role-Based strategy?

A Step 5

B Step 6

C Step 2

D Step 3

💡 Hint

Look at the 'Access Outcome' column for bob in Role-Based rows.

If charlie was added to the 'developer' role, which step's outcome would change?

A Step 1

B Step 7

C Step 8

D Step 4

💡 Hint

Check the Role-Based strategy rows for charlie in the execution_table.

Concept Snapshot

Authorization strategies in Jenkins:
- Matrix: Assign specific permissions per user.
- Role-Based: Assign users to roles with grouped permissions.
- Access allowed if user has required permission or role.
- Deny by default if no permission or role.
- Choose strategy based on complexity and team size.

Full Transcript

This visual execution shows how Jenkins handles user access with two authorization strategies: Matrix and Role-Based. When a user requests access, Jenkins checks which strategy is active. For Matrix, it looks at specific permissions assigned to the user, like 'Build' or 'Read'. For Role-Based, it checks if the user belongs to a role like 'admin' or 'developer'. The execution table traces checks for users alice, bob, and charlie, showing when access is allowed or denied. Variables track permissions and roles assigned. Key moments clarify why some users get denied and how roles simplify management. The quiz tests understanding by referencing specific steps. The snapshot summarizes key points for quick recall.