Spring Session provides an API and implementations for managing a user’s session information.
Spring Session provides an API and implementations for managing a user’s session information while also making it trivial to support clustered sessions without being tied to an application container-specific solution. It also provides transparent integration with:
HttpSession: Allows replacing the
HttpSessionin an application container-neutral way, with support for providing session IDs in headers to work with RESTful APIs.
WebSocket: Provides the ability to keep the
HttpSessionalive when receiving WebSocket messages
WebSession: Allows replacing the Spring WebFlux’s
WebSessionin an application container-neutral way.
We are glad to consider you a part of our community. The following sections provide additional about how to interact with the Spring Session community.
You can get help by asking questions on Stack Overflow with the
Similarly, we encourage helping others by answering questions on Stack Overflow.
You can find the source code on GitHub at https://github.com/spring-projects/spring-session/
We track issues in GitHub issues at https://github.com/spring-projects/spring-session/issues
We appreciate pull requests.
Spring Session is Open Source software released under the Apache 2.0 license.
Spring Session Infinispan
The minimum requirements for Spring Session are:
If you run in a Servlet Container (not required), Servlet 3.1+.
If you use other Spring libraries (not required), the minimum required version is Spring 5.0.x.
@EnableRedisHttpSessionrequires Redis 2.8+. This is necessary to support Session Expiration
@EnableHazelcastHttpSessionrequires Hazelcast 3.6+. This is necessary to support
At its core, Spring Session has a required dependency only on