Luke Taylor

Luke Taylor

Alumni
Blog posts by Luke Taylor

Spring Security Configuration with Scala

Engineering | August 01, 2011 | ...

In a previous article, Behind the Spring Security Namespace, I talked about how the Spring Security namespace has been very successful in providing a simple alternative to plain Spring bean configuration, but how there is still a steep learning curve when you want to start customizing its behaviour. Behind the XML elements and attributes, various filters and helper strategies are created and wired together, but, short of reading the code which handles the XML parsing, there is no easy way of working out which classes are involved or the details of how they interact.

For some time now, we've been trying to come up with an alternative Java-based solution using Spring's @Configuration classes that retains the simplicity of the XML namespace but also makes the underlying behavior more transparent and easier to customize. While theoretically possible, no Java-based solution seemed to meet…

Spring Security 2.0.6 and 3.0.4 Released

Releases | October 28, 2010 | ...

We're pleased to an announce the release of Spring Security 3.0.4.

This release provides a fix for the vulnerability CVE-2010-3700. A 2.0.6 release has also been provided for users who have not yet to upgraded to Spring Security 3.

Please see the changelog for a full list of issues which have been addressed.

Both releases are available from the Spring Community Downloads area and also from the Maven Central repository.

Download | Changelog | Reference Manual | FAQ

Spring Security in Google App Engine

Engineering | August 02, 2010 | ...

Spring Security is well-known for being highly customizable, so for my first attempt at working with Google App Engine, I decided to create a simple application which would explore the use of GAE features by implementing some core Spring Security interfaces. In this article we'll see how to:

  • Authenticate using Google Accounts.
  • Implement "on-demand" authentication when a user accesses a secured resource.
  • Supplement the information from Google Accounts with application-specific roles.
  • Store user account data in an App Engine datastore using the native API.
  • Setup access-control restrictions based on the roles assigned to users.
  • Disable the accounts of specific users to prevent access.

You should already be familiar with deploying applications to GAE. It doesn't take long to get a basic application up and running and you'll find lots of guidance on this on the GAE website.

Sample Application

The application is very simple and is built using Spring MVC. There is a welcome page deployed at the application root, and you can progress to a "home page", but only after authenticating and registering with the application. You can try out a version deployed in GAE here.

The registered users are stored as GAE datastore entities. On first authenticating, new users are redirected to a…

Behind the Spring Security Namespace

Engineering | March 06, 2010 | ...

With the introduction of the security schema in Spring Security 2, it became much easier to get a simple secured application up and running. In older versions, users had to declare and wire-up all the implementation beans individually, resulting in large and complicated Spring application context files which were difficult to understand and maintain. There was a pretty steep learning curve and I can still remember that it took me some time to get my head round it all when I started working on the project (then Acegi Security), back in 2004. On the positive side, this exposure to the basic…

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

Tanzu Spring offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all