This library provides cookie-based implementations of SecurityContextRepository, CsrfTokenRepository, and RequestCache for Spring Security. This allows you to use Spring Security for authentication in your JVM-based application without using HttpSession, eliminating server-side non-persistent user state and simplifying deployments.
HttpSession is standard way to maintain user state in server memory between requests in Java-based web applications. They are easy to use as long as certain precautions are taken, and many frameworks and libraries are based on using HttpSession. If your application takes care of its own authentication (rather than delegating to some access manager reverse proxy), it most likely uses HttpSession to track users' authentication state.
From an operational point of view, using sessions in server memory is problematic since it typically means that each user is must be pegged to the application instance that maintains their session. This is typically implemented using "sticky sessions" or "session persistence" at the load balancer level based on the JSESSIONID cookie.
Performing application deployments without disrupting end users becomes trickier even if techniques such as blue-green deployments are used. An instance can't be stopped until it no longer maintains any user sessions. Solutions exist, such as session replication or persisting user sessions in a database, but these have other drawbacks which means that operations are not necessarily simplified.
This library allows you to use Spring Security for authentication without using HttpSession. Authentication state is kept in an encrypted and signed cookie instead. Specificially, this library provides cookie-based implementations of SecurityContextRepository, CsrfTokenRepository, and RequestCache. These can be used all together or independently.
See the sample Spring Boot application in the src/sampleapp directory for an example of an application using all three implementations and not using HttpSession at all.
This library has been extracted from an application that has been using it in production since January 2016: AusDTO/citizenship-appointment-server
- Java 8 or later
- Java Cryptography Extension unlimited strength policy files
- Servlet API 3.0 or later
- Spring Security 3.2.0 or later
Check the Releases tab for the latest version.
Add https://jitpack.io as a repository to your Gradle build file (likely build.gradle):
repositories {
...
maven { url 'https://jitpack.io' }
}
Then add the dependency:
dependencies {
...
compile 'com.github.AusDTO:spring-security-stateless:v1.2.3'
}
Add https://jitpack.io as a repository to your Maven POM file (likely pom.xml):
<repositories>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
</repositories>
Then add the dependency:
<dependency>
<groupId>com.github.AusDTO</groupId>
<artifactId>spring-security-stateless</artifactId>
<version>v1.2.3</version>
</dependency>
See JitPack.io for instructions
Instructions coming soon. In the meantime, see the example application in the directory src/sampleapp.
To generate a key for encrypting and signing use this command on Unix and macOS:
openssl rand 32 | base64
Alternatively you can use the following Java code:
java.security.SecureRandom secureRandom = new java.security.SecureRandom();
byte[] key = new byte[32];
secureRandom.nextBytes(key);
String encodedKey = java.util.Base64.getEncoder().encodeToString(key);
System.out.println(encodedKey);
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent