Server-side Sessions - Ticket Registry

If you don’t wish to use the native container’s strategy for session replication, and the session storage backend of your choice is not natively supported by Spring Session, you can use CAS’ support for the Ticket Registry to store sessions.

This option translates session data and attributes into a TST ticket, and stores it in the configured ticket registry. Note that by Session, we mean the HTTP session that is created by the container such as Apache Tomcat specific to the runtime environment, and is represented by the jakarta.servlet.http.HttpSession object.

1
2
3
4
5

<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-session-ticket-registry</artifactId>
    <version>${cas.version}</version>
</dependency>

1

implementation "org.apereo.cas:cas-server-support-session-ticket-registry:${project.'cas.version'}"

1
2
3
4
5
6
7
8
9

dependencyManagement {
    imports {
        mavenBom "org.apereo.cas:cas-server-support-bom:${project.'cas.version'}"
    }
}

dependencies {
    implementation "org.apereo.cas:cas-server-support-session-ticket-registry"
}

1
2
3
4
5
6
7
8
9
10

dependencies {
    /*
        The following platform references should be included automatically and are listed here for reference only.

        implementation enforcedPlatform("org.apereo.cas:cas-server-support-bom:${project.'cas.version'}")
        implementation platform(org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES)
        
    */
    implementation "org.apereo.cas:cas-server-support-session-ticket-registry"
}