Method-level security in Spring Boot - Step-by-Step Execution

Concept Flow - Method-level security

User sends request

↓

Spring Security Intercepts

↓

Check method annotation

↓

Evaluate security expression

Yes No↓

Allow method

↓

Execute method

When a user calls a method, Spring Security checks the method's security annotation, evaluates if the user has permission, then allows or denies access accordingly.

Execution Sample

Spring Boot

@PreAuthorize("hasRole('ADMIN')")
public String adminOnly() {
    return "Secret Data";
}

This method only runs if the user has the ADMIN role; otherwise, access is denied.

Execution Table

Step	Action	Security Check	Result	Method Execution
1	User calls adminOnly()	Check @PreAuthorize("hasRole('ADMIN')")	User roles: USER	Access Denied, method NOT executed
2	User calls adminOnly()	Check @PreAuthorize("hasRole('ADMIN')")	User roles: ADMIN	Access Allowed, method executed, returns "Secret Data"

💡 Execution stops if user lacks ADMIN role; method runs only if user has ADMIN role.

Variable Tracker

Variable	Start	After Step 1	After Step 2
userRoles	[]	[USER]	[ADMIN]
accessGranted	false	false	true
methodOutput	null	null	"Secret Data"

Key Moments - 3 Insights

Why does the method not run when the user role is USER?

Because the @PreAuthorize annotation requires ADMIN role. Execution_table row 1 shows access denied due to missing ADMIN role.

What happens if the user has the ADMIN role?

The security check passes, allowing method execution. Execution_table row 2 shows method runs and returns data.

Is the method code executed before or after the security check?

The security check happens first. If it fails, the method is never executed, as shown in execution_table row 1.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of accessGranted at step 2?

A null

B false

C true

D undefined

💡 Hint

Check the 'accessGranted' column in variable_tracker after Step 2.

At which step does the method execution get blocked?

A Step 1

B Step 2

C Both steps

D Never blocked

💡 Hint

Look at execution_table row 1 where access is denied and method is not executed.

If the user role changes from USER to ADMIN, what changes in the execution table?

A Security check is skipped

B Access changes from denied to allowed

C Method output becomes null

D User roles become empty

💡 Hint

Compare rows 1 and 2 in execution_table for access and method execution.

Concept Snapshot

Method-level security in Spring Boot uses annotations like @PreAuthorize.
Spring Security checks user roles before running a method.
If the user lacks permission, the method is blocked.
If allowed, the method runs and returns its result.
This protects sensitive methods easily and clearly.

Full Transcript

Method-level security in Spring Boot means protecting individual methods by checking user permissions before running them. When a user calls a method annotated with @PreAuthorize, Spring Security intercepts the call and checks if the user has the required role or permission. If the user does not have the right role, the method is not executed and access is denied. If the user has the role, the method runs normally and returns its result. This approach helps keep sensitive parts of the application safe by controlling access at the method level.