DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Stateless JWT Auth Microservice Architecture With Spring Boot 3 and Redis Sentinel
  • Securing Verifiable Credentials With DPoP: A Spring Boot Implementation
  • Prototype for a Java Database Application With REST and Security
  • MuleSoft OAuth 2.0 Provider: Password Grant Type

Trending

  • Why 200 OK Is the Most Dangerous Lie in Enterprise Integration
  • Mastering Load Balancers: Optimizing Traffic for High Availability and Performance
  • Testing AI-Infused Apps: A Dual-Layer Framework for AI Quality Assurance
  • 5 AI Security Incidents That Broke Things in Production (and What They Have in Common)

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Coding
  3. Java
  4. Securing URLs Using Spring Security

Securing URLs Using Spring Security

Securing URLs using Spring Security is a pretty straight forward job. Read on to find out how to do it!

By 
Martin Farrell
·
Nov. 19, 16 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
107.5K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

Typically when securing a URL you are looking to do one of the following:

  • Allow access to everyone to a given URL
  • Secure URL based on roles.
  • Secure URL based on multiple roles.
  • Secure URL based on IP Address.

This post shows how to do this using spring security

Specifying URLs

The most common approach to specifying a URL is through antMatchers. So if we want to secure:

http://www.example.com/static Open to everyone – CSS, JavaScript
http://www.example.com/register Open to everyone
http://www.example.com/login Open to everyone
http://www.example.com/user/ ROLE_USER or ROLE_ADMIN – User Area
http://www.example.com/admin/

ROLE_ADMIN only and restrict on IPADDRESS – Admin Area

We would simply use:

.antMatchers("/register")

Or with multiple:

.antMatchers("/register","/login","/user","/admin")

We also specify individual pages or directories –

.antMatchers("register.html"); // Individual
.antMatchers("/admin/**"); // Directory


Depending on the complexity of pattern you are securing, you can also consider:

  • mvcMatcher.
  • requestMatcher.
  • regexMatcher.

Securing the URLs

The methods to secure URL’s are defined in AuthorizedUrl. The most common methods are:

  • authenticated(): This is the URL you want to protect, and requires the user to login
  • permitAll(): This is used for URL’s with no security applied for example css, javascript
  • hasRole(String role): Restrict to single role. Note that the role will have “ROLE_” appended. So role=”ADMIN” has a comparison against “ROLE_ADMIN”. An alternatve is hasAuthority(String authority)
  • hasAnyRole(String… roles): Allows multiple roles. An alternative is hasAnyAuthority(String… authorities)

Other useful methods are:

  • access(String attribute): This method takes SPEL, so you can create more complex restrictions. For those who are interested a lot of the methods in  ExpressionUrlAuthorizationConfigurer.AuthorizedUrl ultimately call access with the required SPEL
  • hasIpAddress(String ipaddressExpression): Restrict on IP address or subnet

Putting it All Together

We can put this altogher and create a method like:

    @Override
    protected void configure(HttpSecurity http) throws Exception {
      http
        .authorizeRequests()
           .antMatchers("/static","/register").permitAll()
           .antMatchers("/user/**").hasRoles("USER", "ADMIN") // can pass multiple roles
           .antMatchers("/admin/**").access("hasRole('ADMIN') and hasIpAddress('123.123.123.123')") // pass SPEL using access method
           .anyRequest().authenticated()
           .and()
       .formLogin()
           .loginUrl("/login")
           .permitAll();
    }

The key points are:

  • permitAll gives everyone access to a file or directory.
  • hasRoles passes multiple roles.
  • access for more compicated access.

As a side note, I am currently working on a project to automatically generate this configuration with my spring-security-generator.

Spring Security

Published at DZone with permission of Martin Farrell. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Stateless JWT Auth Microservice Architecture With Spring Boot 3 and Redis Sentinel
  • Securing Verifiable Credentials With DPoP: A Spring Boot Implementation
  • Prototype for a Java Database Application With REST and Security
  • MuleSoft OAuth 2.0 Provider: Password Grant Type

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook