Role-based access control in Spring Boot - Step-by-Step Execution

Concept Flow - Role-based access control

User sends request

↓

Spring Security intercepts

↓

Check user authentication

Yes↓

Check user roles

↓

Role matches

↓

Allow access

↓

Send response

The flow shows how Spring Security checks if a user is authenticated and has the right role before allowing access.

Execution Sample

Spring Boot

@PreAuthorize("hasRole('ADMIN')")
public String adminPage() {
  return "Admin content";
}

This code allows only users with the ADMIN role to access the adminPage method.

Execution Table

Step	Action	User Role	Check	Result	Access Outcome
1	User sends request to adminPage	USER	Is user authenticated?	Yes	Continue
2	Check if user has ADMIN role	USER	Does user have ADMIN role?	No	Access Denied
3	User sends request to adminPage	ADMIN	Is user authenticated?	Yes	Continue
4	Check if user has ADMIN role	ADMIN	Does user have ADMIN role?	Yes	Access Granted

💡 Access denied if user lacks ADMIN role; access granted only if role matches.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
User Role	None	USER	USER	ADMIN	ADMIN	ADMIN
Access Outcome	None	Pending	Denied	Pending	Granted	Granted

Key Moments - 2 Insights

Why does a user with role USER get denied access even if authenticated?

Because the role check in step 2 fails as USER role does not match required ADMIN role, so access is denied.

What happens if the user is not authenticated?

Spring Security blocks access before role check; authentication is required first as shown in step 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the access outcome at step 2 for a USER role?

A Pending

B Access Granted

C Access Denied

D Authentication Failed

💡 Hint

Check the 'Access Outcome' column at step 2 in the execution_table.

At which step does the system confirm the user has the ADMIN role?

A Step 4

B Step 2

C Step 1

D Step 3

💡 Hint

Look for the role check result 'Yes' for ADMIN role in the execution_table.

If the user role changed from USER to ADMIN at step 2, how would the access outcome change?

A It would remain Access Denied

B It would change to Access Granted

C It would become Pending

D Authentication would fail

💡 Hint

Refer to the variable_tracker and execution_table rows where ADMIN role leads to Access Granted.

Concept Snapshot

Role-based access control in Spring Boot:
- Use @PreAuthorize("hasRole('ROLE_NAME')") to restrict methods.
- Spring Security checks authentication first.
- Then it checks if user has required role.
- Access is granted only if role matches.
- Otherwise, access is denied.

Full Transcript

Role-based access control in Spring Boot works by intercepting user requests with Spring Security. First, it checks if the user is authenticated. If not, access is blocked immediately. If authenticated, it checks the user's roles against the required role for the resource or method. For example, a method annotated with @PreAuthorize("hasRole('ADMIN')") allows only users with the ADMIN role. If the user has the role, access is granted; otherwise, it is denied. This ensures only authorized users can access protected parts of the application.

Practice

1. What is the main purpose of role-based access control (RBAC) in a Spring Boot application?

easy

A. To restrict access to resources based on user roles

B. To improve application performance by caching data

C. To automatically generate user interfaces

D. To handle database transactions efficiently

Solution

1. Step 1: Understand RBAC concept

   RBAC limits access to parts of an application depending on the roles assigned to users.

2. Step 2: Identify the purpose in Spring Boot

   In Spring Boot, RBAC is used to protect resources by checking user roles before allowing access.

3. Final Answer:

   To restrict access to resources based on user roles -> Option A

4. Quick Check:

   RBAC controls access by roles = A [OK]

Hint: RBAC controls who can do what by roles [OK]

Common Mistakes:

• Confusing RBAC with performance optimization
• Thinking RBAC generates UI automatically
• Mixing RBAC with database transaction handling

2. Which annotation is used in Spring Boot to enforce role-based access control on a method?

easy

A. @PreAuthorize

B. @Autowired

C. @RequestMapping

D. @Entity

Solution

1. Step 1: Identify role enforcement annotation

   Spring Security uses @PreAuthorize to check roles before method execution.

2. Step 2: Differentiate from other annotations

   @RequestMapping handles URL mapping, @Autowired injects beans, @Entity marks database entities.

3. Final Answer:

   @PreAuthorize -> Option A

4. Quick Check:

   @PreAuthorize controls access by roles [OK]

Hint: Use @PreAuthorize to check roles on methods [OK]

Common Mistakes:

• Using @RequestMapping for access control
• Confusing @Autowired with security annotations
• Mistaking @Entity for access control

3. Given the method annotation @PreAuthorize("hasRole('ADMIN')"), what will happen if a user with role USER tries to access this method?

medium

A. Access is granted because USER is a valid role

B. Method throws a syntax error

C. Access is denied because the user lacks ADMIN role

D. Access is granted only if the user is authenticated

Solution

1. Step 1: Understand the @PreAuthorize expression

   The expression requires the user to have the ADMIN role to access the method.

2. Step 2: Check user role against requirement

   A user with only USER role does not meet the ADMIN role requirement, so access is denied.

3. Final Answer:

   Access is denied because the user lacks ADMIN role -> Option C

4. Quick Check:

   Role check fails without ADMIN role = B [OK]

Hint: User must have exact role in @PreAuthorize to access [OK]

Common Mistakes:

• Assuming any authenticated user can access
• Thinking USER role is enough for ADMIN-only methods
• Confusing syntax error with access denial

4. Consider this method in a Spring Boot controller:

@PreAuthorize("hasRole('ADMIN')")
public String adminPage() {
    return "Welcome Admin";
}

What is the likely cause if users with ADMIN role still get access denied errors?

medium

A. The method must be static to work with @PreAuthorize

B. The role prefix 'ROLE_' is missing in the role check

C. The return type should be ResponseEntity<String>

D. The method should be annotated with @GetMapping instead

Solution

1. Step 1: Understand Spring Security role prefix

   Spring Security by default adds 'ROLE_' prefix to roles internally.

2. Step 2: Check role naming in @PreAuthorize

   Using hasRole('ADMIN') expects the granted authority to be 'ROLE_ADMIN'. If roles lack this prefix, access is denied.

3. Final Answer:

   The role prefix 'ROLE_' is missing in the role check -> Option B

4. Quick Check:

   Missing 'ROLE_' prefix causes access denial = D [OK]

Hint: Remember Spring Security adds 'ROLE_' prefix by default [OK]

Common Mistakes:

• Thinking @GetMapping affects access control
• Believing return type affects security
• Assuming method must be static for @PreAuthorize

5. You want to restrict access to a service method so that only users with either ADMIN or MANAGER roles can call it. Which @PreAuthorize expression correctly enforces this?

hard

A. @PreAuthorize("hasRole('ADMIN,MANAGER')")

B. @PreAuthorize("hasRole('ADMIN', 'MANAGER')")

C. @PreAuthorize("hasRole('ADMIN') and hasRole('MANAGER')")

D. @PreAuthorize("hasAnyRole('ADMIN', 'MANAGER')")

Solution

1. Step 1: Understand role checks for multiple roles

   To allow access if user has either ADMIN or MANAGER, use hasAnyRole('ADMIN', 'MANAGER').

2. Step 2: Analyze each option

   @PreAuthorize("hasRole('ADMIN') and hasRole('MANAGER')") requires both roles (AND), which is too strict. @PreAuthorize("hasRole('ADMIN', 'MANAGER')") is invalid as hasRole accepts only one role. @PreAuthorize("hasAnyRole('ADMIN', 'MANAGER')") uses hasAnyRole which is concise and correct. @PreAuthorize("hasRole('ADMIN,MANAGER')") is invalid syntax.

3. Final Answer:

   @PreAuthorize("hasAnyRole('ADMIN', 'MANAGER')") -> Option D

4. Quick Check:

   Use hasAnyRole for multiple allowed roles = A [OK]

Hint: Use hasAnyRole for OR conditions on roles [OK]

Common Mistakes:

• Using AND instead of OR for multiple roles
• Passing multiple roles as a single string
• Not using hasAnyRole for multiple roles