Why authorization matters in Spring Boot - Visual Breakdown

Concept Flow - Why authorization matters

User sends request

↓

Authentication: Who are you?

↓

Authorization: What can you do?

Yes No↓

Allow access

↓

Resource accessed or blocked

This flow shows how a user request is first checked for identity (authentication), then checked for permissions (authorization) before access is granted or denied.

Execution Sample

Spring Boot

httpSecurity.authorizeHttpRequests()
  .requestMatchers("/admin/**").hasRole("ADMIN")
  .anyRequest().authenticated();

This code configures Spring Security to allow only users with ADMIN role to access /admin paths, and requires authentication for all other requests.

Execution Table

Step	Request URL	User Role	Authorization Check	Access Result
1	/admin/dashboard	ADMIN	User has ADMIN role? Yes	Access granted
2	/admin/settings	USER	User has ADMIN role? No	Access denied
3	/profile	USER	Authenticated? Yes	Access granted
4	/profile	Anonymous	Authenticated? No	Access denied

💡 Access is granted only if authorization rules match user roles and authentication status.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
Request URL	none	/admin/dashboard	/admin/settings	/profile	/profile
User Role	none	ADMIN	USER	USER	Anonymous
Authorization Result	none	granted	denied	granted	denied

Key Moments - 2 Insights

Why does a user with role USER get denied access to /admin/settings?

Because the authorization rule requires ADMIN role for /admin/** paths, as shown in execution_table step 2.

Why is authentication checked before authorization?

Authorization depends on knowing who the user is, so authentication must happen first to identify the user, as shown in the concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, what is the access result for a USER role requesting /admin/settings?

A Access granted

B Request redirected

C Access denied

D Access pending

💡 Hint

Check execution_table row 2 under Access Result column.

At which step does an anonymous user get denied access?

A Step 2

B Step 4

C Step 3

D Step 1

💡 Hint

Look at execution_table row 4 for User Role and Access Result.

If the authorization rule for /admin/** was removed, what would happen to step 2's access result?

A Access granted to USER

B Access denied to USER

C Access denied to ADMIN

D Request blocked for all

💡 Hint

Without role check, only authentication is required as per code in execution_sample.

Concept Snapshot

Authorization controls what a user can do after authentication.
In Spring Boot, use httpSecurity.authorizeHttpRequests() to set rules.
Example: .requestMatchers("/admin/**").hasRole("ADMIN") restricts admin paths.
Requests failing authorization are denied access.
Always check authentication first, then authorization.

Full Transcript

Authorization is the process that decides what a user can access or do after they have logged in. In Spring Boot, authorization rules are set using httpSecurity.authorizeHttpRequests(), where you specify which roles can access certain URL patterns. For example, only users with the ADMIN role can access URLs starting with /admin/. The flow starts with a user sending a request, then authentication checks who the user is, followed by authorization checking what the user is allowed to do. If the user meets the authorization rules, access is granted; otherwise, it is denied. This ensures that sensitive parts of an application are protected from unauthorized users.