WORKERS AHEAD!
You are viewing the development documentation for the Apereo CAS server. The functionality presented here is not officially released yet. This is a work in progress and will be continually updated as development moves forward. To view the documentation for a specific Apereo CAS server release, please choose an appropriate version. The release schedule is also available here.
Default Ticket Registry
The default registry uses a memory-backed internal concurrent map for ticket storage and retrieval, though there is also the option to use an implementation that is backed by a caching engine to gain slightly better performance when it comes to evicting expired tickets.
This component does not preserve ticket state across restarts and is not a suitable solution for clustered CAS environments that are deployed in active/active mode.
The following settings and properties are available from the CAS configuration catalog:
cas.ticket.registry.in-memory.crypto.encryption.key=
The encryption key. The encryption key by default and unless specified otherwise must be randomly-generated string whose length is defined by the encryption key size setting. |
cas.ticket.registry.in-memory.crypto.signing.key=
The signing key is a JWT whose length is defined by the signing key size setting. |
cas.ticket.registry.in-memory.crypto.alg=AES
The signing/encryption algorithm to use. |
cas.ticket.registry.in-memory.crypto.enabled=true
Whether crypto operations are enabled. |
cas.ticket.registry.in-memory.crypto.encryption.key-size=16
Encryption key size. |
cas.ticket.registry.in-memory.crypto.signing.key-size=512
The signing key size. |