Redis Ticket Registry
Redis integration is enabled by including the following dependency in the WAR overlay:
1
2
3
4
5
<dependency>
<groupId>org.apereo.cas</groupId>
<artifactId>cas-server-support-redis-ticket-registry</artifactId>
<version>${cas.version}</version>
</dependency>
1
implementation "org.apereo.cas:cas-server-support-redis-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-redis-ticket-registry"
}
1
2
3
4
5
6
7
8
9
10
dependencies {
/*
The following platform references are included automatically and are listed 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-redis-ticket-registry"
}
This registry stores tickets in one or more Redis instances. CAS presents and uses Redis as a
key/value store that accepts String keys and CAS ticket documents as values. The key is started with CAS_TICKET:.
The Redis ticket registry supports Redis Sentinel, which provides high availability for Redis. In practical terms this means that using Sentinel you can create a Redis deployment that resists without human intervention to certain kind of failures. Redis Sentinel also provides other collateral tasks such as monitoring, notifications and acts as a configuration provider for clients.
Configuration
The following settings and properties are available from the CAS configuration catalog:
cas.ticket.registry.redis.cluster.nodes[0].hostServer's host address.
Server's host address.
cas.ticket.registry.redis.cluster.nodes[0].portServer's port number.
Server's port number.
cas.ticket.registry.redis.cluster.nodes[0].replica-ofSet the id of the master node.
Set the id of the master node.
cas.ticket.registry.redis.cluster.nodes[0].typeIndicate the type/role of this node.
Indicate the type/role of this node. Accepted values are: MASTER, REPLICA.
cas.ticket.registry.redis.cluster.passwordThe cluster connection's password.
The cluster connection's password.
cas.ticket.registry.redis.cluster.usernameThe cluster connection's username.
The cluster connection's username.
cas.ticket.registry.redis.crypto.encryption.keyThe 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.redis.crypto.signing.keyThe signing key is a string whose length is defined by the signing key size setting.
The signing key is a string whose length is defined by the signing key size setting.
cas.ticket.registry.redis.databaseDatabase index used by the connection factory.
0Database index used by the connection factory.
cas.ticket.registry.redis.enabledWhether the module is enabled or not, defaults to true.
trueWhether the module is enabled or not, defaults to true.
cas.ticket.registry.redis.hostRedis server host.
localhostRedis server host.
cas.ticket.registry.redis.passwordLogin password of the redis server.
Login password of the redis server.
cas.ticket.registry.redis.pool.enabledEnable the pooling configuration.
falseEnable the pooling configuration.
cas.ticket.registry.redis.portRedis server port.
6379Redis server port.
cas.ticket.registry.redis.sentinel.masterName of Redis server.
Name of Redis server.
cas.ticket.registry.redis.usernameLogin username of the redis server.
Login username of the redis server.
cas.ticket.registry.redis.cache.cache-sizeThis cache size specifies the maximum number of entries the cache may contain.
10000This cache size specifies the maximum number of entries the cache may contain. Note that the cache may evict an entry before this limit is exceeded or temporarily exceed the threshold while evicting. As the cache size grows close to the maximum, the cache evicts entries that are less likely to be used again. For example, the cache may evict an entry because it hasn't been used recently or very often. Note: to disable the cache, you may choose a cache size of 0.
cas.ticket.registry.redis.cache.initial-capacityThis cache capacity sets the minimum total size for the internal data structures.
1000This cache capacity sets the minimum total size for the internal data structures. Providing a large enough estimate at construction time avoids the need for expensive resizing operations later, but setting this value unnecessarily high wastes memory.
cas.ticket.registry.redis.certificate-fileMay be used when making SSL connections to build the trust manager.
May be used when making SSL connections to build the trust manager. Sets the certificate file to use for client authentication. This is typically an X.509 certificate file (or chain file) in PEM format.
cas.ticket.registry.redis.cluster.dynamic-refresh-sourcesWhether to discover and query all cluster nodes for obtaining the cluster topology.
trueWhether to discover and query all cluster nodes for obtaining the cluster topology. When set to false, only the initial seed nodes are used as sources for topology discovery.
cas.ticket.registry.redis.cluster.max-redirectsThe max number of redirects to follow.
0The max number of redirects to follow.
cas.ticket.registry.redis.cluster.nodesList of nodes available in the redis cluster.
List of nodes available in the redis cluster.
cas.ticket.registry.redis.cluster.nodes[0].idIdentifier of this node.
Identifier of this node.
cas.ticket.registry.redis.cluster.nodes[0].nameName of this node.
Name of this node.
cas.ticket.registry.redis.cluster.topology-refresh-periodEnables periodic refresh of cluster topology and sets the refresh period.
Enables periodic refresh of cluster topology and sets the refresh period.
cas.ticket.registry.redis.connect-timeoutConnection timeout.
PT10SConnection timeout.
cas.ticket.registry.redis.crypto.algThe signing/encryption algorithm to use.
AESThe signing/encryption algorithm to use.
cas.ticket.registry.redis.crypto.enabledWhether crypto operations are enabled.
trueWhether crypto operations are enabled.
cas.ticket.registry.redis.crypto.encryption.key-sizeEncryption key size.
16Encryption key size.
cas.ticket.registry.redis.crypto.signing-enabledWhether signing encryption operations are enabled.
trueWhether signing encryption operations are enabled.
cas.ticket.registry.redis.crypto.signing.key-sizeThe signing key size.
512The signing key size.
cas.ticket.registry.redis.enable-redis-searchAllows the register to detect the presence of Redis modules, in particular RediSearch, which allows the registry to create specific indexes and search Redis documents to look up tickets.
trueAllows the register to detect the presence of Redis modules, in particular RediSearch, which allows the registry to create specific indexes and search Redis documents to look up tickets. Enabling indexing and searching capabilities may lead to significant performance improvements.
cas.ticket.registry.redis.keep-alive-countThe maximum number of keepalive probes TCP should send before dropping the connection.
0The maximum number of keepalive probes TCP should send before dropping the connection. By default, leaving this number at zero disables keepalive.
cas.ticket.registry.redis.keep-alive-idle-timeoutThe time the connection needs to remain idle before TCP starts sending keepalive probes if keepalive is enabled.
PT2HThe time the connection needs to remain idle before TCP starts sending keepalive probes if keepalive is enabled.
cas.ticket.registry.redis.keep-alive-intervalThe time the connection needs to remain idle before TCP starts sending keepalive probes.
PT60SThe time the connection needs to remain idle before TCP starts sending keepalive probes.
cas.ticket.registry.redis.key-certificate-chain-fileMay be used when making SSL connections to build the key manager.
May be used when making SSL connections to build the key manager. Sets the key certificate file to use for client authentication. This is typically an X.509 certificate file (or chain file) in PEM format.
cas.ticket.registry.redis.key-fileMay be used when making SSL connections.
May be used when making SSL connections. Sets the key file for client authentication. The key is reloaded on each connection attempt that allows CAS to replace certificates during runtime. This is typically a PKCS#8 private key file in PEM format.
cas.ticket.registry.redis.key-passwordThe password of the #keyFile , or null if it's not password-protected.
The password of the #keyFile, or null if it's not password-protected.
cas.ticket.registry.redis.pool.fairnessReturns whether or not the pool serves threads waiting to borrow objects fairly.
falseReturns whether or not the pool serves threads waiting to borrow objects fairly. True means that waiting threads are served as if waiting in a FIFO queue.
cas.ticket.registry.redis.pool.lifoReturns whether the pool has LIFO (last in, first out) behaviour with respect to idle objects - always returning the most recently used object from the pool, or as a FIFO (first in, first out) queue, where the pool al...
trueReturns whether the pool has LIFO (last in, first out) behaviour with respect to idle objects - always returning the most recently used object from the pool, or as a FIFO (first in, first out) queue, where the pool always returns the oldest object in the idle object pool.
cas.ticket.registry.redis.pool.max-activeMax number of connections that can be allocated by the pool at a given time.
8Max number of connections that can be allocated by the pool at a given time. Use a negative value for no limit.
cas.ticket.registry.redis.pool.max-idleMax number of "idle" connections in the pool.
8Max number of "idle" connections in the pool. Use a negative value to indicate an unlimited number of idle connections.
cas.ticket.registry.redis.pool.max-waitMaximum amount of time (in milliseconds) a connection allocation should block before throwing an exception when the pool is exhausted.
PT5SMaximum amount of time (in milliseconds) a connection allocation should block before throwing an exception when the pool is exhausted. Use a negative value to block indefinitely.
cas.ticket.registry.redis.pool.min-evictable-idle-time-millisSets the minimum amount of time an object may sit idle in the pool before it is eligible for eviction by the idle object evictor (if any - see setTimeBetweenEvictionRunsMillis(long)).
0Sets the minimum amount of time an object may sit idle in the pool before it is eligible for eviction by the idle object evictor (if any - see setTimeBetweenEvictionRunsMillis(long)). When non-positive, no objects will be evicted from the pool due to idle time alone.
cas.ticket.registry.redis.pool.min-idleTarget for the minimum number of idle connections to maintain in the pool.
0Target for the minimum number of idle connections to maintain in the pool. This setting only has an effect if it is positive.
cas.ticket.registry.redis.pool.num-tests-per-eviction-runSets the maximum number of objects to examine during each run (if any) of the idle object evictor thread.
0Sets the maximum number of objects to examine during each run (if any) of the idle object evictor thread. When positive, the number of tests performed for a run will be the minimum of the configured value and the number of idle instances in the pool. When negative, the number of tests performed will be ceil(getNumIdle()/ abs(getNumTestsPerEvictionRun())) which means that when the value is -n roughly one nth of the idle objects will be tested per run.
cas.ticket.registry.redis.pool.soft-min-evictable-idle-time-millisSets the minimum amount of time an object may sit idle in the pool before it is eligible for eviction by the idle object evictor (if any - see setTimeBetweenEvictionRunsMillis(long)), with the extra condition that at...
0Sets the minimum amount of time an object may sit idle in the pool before it is eligible for eviction by the idle object evictor (if any - see setTimeBetweenEvictionRunsMillis(long)), with the extra condition that at least minIdle object instances remain in the pool. This setting is overridden by getMinEvictableIdleTimeMillis() (that is, if getMinEvictableIdleTimeMillis() is positive, then getSoftMinEvictableIdleTimeMillis() is ignored).
cas.ticket.registry.redis.pool.test-on-borrowReturns whether objects borrowed from the pool will be validated before being returned from the borrowObject() method.
falseReturns whether objects borrowed from the pool will be validated before being returned from the borrowObject() method. Validation is performed by the validateObject() method of the factory associated with the pool. If the object fails to validate, it will be removed from the pool and destroyed, and a new attempt will be made to borrow an object from the pool.
cas.ticket.registry.redis.pool.test-on-createReturns whether objects created for the pool will be validated before being returned from the borrowObject() method.
falseReturns whether objects created for the pool will be validated before being returned from the borrowObject() method. Validation is performed by the validateObject() method of the factory associated with the pool. If the object fails to validate, then borrowObject() will fail.
cas.ticket.registry.redis.pool.test-on-returnReturns whether objects borrowed from the pool will be validated when they are returned to the pool via the returnObject() method.
falseReturns whether objects borrowed from the pool will be validated when they are returned to the pool via the returnObject() method. Validation is performed by the validateObject() method of the factory associated with the pool. Returning objects that fail validation are destroyed rather then being returned the pool.
cas.ticket.registry.redis.pool.test-while-idleReturns whether objects sitting idle in the pool will be validated by the idle object evictor ( if any - see setTimeBetweenEvictionRunsMillis(long)).
falseReturns whether objects sitting idle in the pool will be validated by the idle object evictor ( if any - see setTimeBetweenEvictionRunsMillis(long)). Validation is performed by the validateObject() method of the factory associated with the pool. If the object fails to validate, it will be removed from the pool and destroyed.
cas.ticket.registry.redis.pool.time-between-eviction-runs-millisSets the amount of time (in milliseconds) between runs of the idle object evictor thread.
-1Sets the amount of time (in milliseconds) between runs of the idle object evictor thread. When non-positive, no idle object evictor thread will be run. If positive, the idle object evictor thread will run at least once every timeBetweenEvictionRunsMillis milliseconds, and will attempt to evict objects from the pool that are idle longer than getMinEvictableIdleTimeMillis() (if positive) or getSoftMinEvictableIdleTimeMillis() (if positive).
cas.ticket.registry.redis.protocol-versionRedis protocol version.
RESP3Redis protocol version.
cas.ticket.registry.redis.queue-identifierIdentifier for this CAS server node that tags the sender/receiver in the queue and avoid processing of inbound calls.
Identifier for this CAS server node that tags the sender/receiver in the queue and avoid processing of inbound calls. If left blank, an identifier is generated automatically and kept in memory.
cas.ticket.registry.redis.read-fromSetting that describes how Lettuce routes read operations to replica nodes.
-
UPSTREAM: Read from the current upstream node. -
UPSTREAMPREFERRED: Read from the upstream node, but if it is unavailable, read from replica nodes. -
MASTER: Read from the current upstream node. -
MASTERPREFERRED: Read from the upstream node, but if it is unavailable, read from replica nodes. -
SLAVE: Read from replica nodes. -
SLAVEPREFERRED: Read from the replica nodes, but if none is unavailable, read from the upstream node. -
REPLICA: Read from replica nodes. -
REPLICAPREFERRED: Read from the replica nodes, but if none is unavailable, read from the upstream node. -
ANY: Read from any node of the cluster. -
ANYREPLICA: Read from any replica node of the cluster. -
NEAREST: Read from the nearest node.
cas.ticket.registry.redis.sentinel.nodelist of host:port pairs.
list of host:port pairs.
cas.ticket.registry.redis.sentinel.passwordLogin password of the sentinel server.
Login password of the sentinel server.
cas.ticket.registry.redis.share-native-connectionsThe shared native connection is never closed by Lettuce connection, therefore it is not validated by default when connections are retrieved.
The shared native connection is never closed by Lettuce connection, therefore it is not validated by default when connections are retrieved. If this setting is true, a shared connection will be used for regular operations and a connection provider will be used to select a connection for blocking and tx operations only, which should not share a connection. If native connection sharing is disabled, new (or pooled) connections will be used for all operations. By default, multiple connections share a single thread-safe native connection. If you enable connection pooling, then native connection sharing will be disabled and the connection pool will be used for all operations. You may however explicitly control connection sharing via this setting as an override.
cas.ticket.registry.redis.start-tlsStart mutual TLS.
falseStart mutual TLS. In order to support TLS, Redis should be configured with a X.509 certificate and a private key. In addition, it is necessary to specify a CA certificate bundle file or path to be used as a trusted root when validating certificates.
cas.ticket.registry.redis.timeoutCommand timeout.
PT60SCommand timeout.
cas.ticket.registry.redis.uriDatabase URI.
Database URI.
cas.ticket.registry.redis.use-sslWhether or not to use SSL for connection factory.
falseWhether or not to use SSL for connection factory.
cas.ticket.registry.redis.verify-peerControl how peer verification is handled with redis connections.
trueControl how peer verification is handled with redis connections. Peer verification is a security feature that checks if the host you're connecting to is who it says it is. This is often done by checking a digital certificate.
Required settings may be needed to activate or affect the feature; review them even when they have a default. Optional settings only need to be set to change a default or to turn on the behavior they control. Third party settings belong to libraries such as Spring Boot that CAS builds on; their own documentation may have more detail.
Signing & encryption
This CAS feature is able to accept signing and encryption crypto keys. In most scenarios if keys are not provided, CAS will auto-generate them. The following instructions apply if you wish to manually and beforehand create the signing and encryption keys.
Note that if you are asked to create a JWK of a certain size for the key, you are to use the following set of commands to generate the token:
1
2
wget https://raw.githubusercontent.com/apereo/cas/master/etc/jwk-gen.jar
java -jar jwk-gen.jar -t oct -s [size]
The outcome would be similar to:
1
2
3
4
5
{
"kty": "oct",
"kid": "...",
"k": "..."
}
The generated value for k needs to be assigned to the relevant CAS settings. Note that keys generated via
the above algorithm are processed by CAS using the Advanced Encryption Standard (AES) algorithm which is a
specification for the encryption of electronic data established by the U.S. National Institute of Standards and Technology.
Notes on configuration
Configuration Metadata
The collection of configuration properties listed in this section are automatically generated from the CAS source and components that contain the actual field definitions, types, descriptions, modules, etc. This metadata may not always be 100% accurate, or could be lacking details and sufficient explanations.
Be Selective
This section is meant as a guide only. Do NOT copy/paste the entire collection of settings into your CAS configuration; rather pick only the properties that you need. Do NOT enable settings unless you are certain of their purpose and do NOT copy settings into your configuration only to keep them as reference. All these ideas lead to upgrade headaches, maintenance nightmares and premature aging.
YAGNI
Note that for nearly ALL use cases, declaring and configuring properties listed here is sufficient. You should NOT have to explicitly massage a CAS XML/Java/etc configuration file to design an authentication handler, create attribute release policies, etc. CAS at runtime will auto-configure all required changes for you. If you are unsure about the meaning of a given CAS setting, do NOT turn it on without hesitation. Review the codebase or better yet, ask questions to clarify the intended behavior.
Naming Convention
Property names can be specified in very relaxed terms. For instance cas.someProperty, cas.some-property, cas.some_property are all valid names. While all
forms are accepted by CAS, there are certain components (in CAS and other frameworks used) whose activation at runtime is conditional on a property value, where
this property is required to have been specified in CAS configuration using kebab case. This is both true for properties that are owned by CAS as well as those
that might be presented to the system via an external library or framework such as Spring Boot, etc.
Note
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions) MUST remain in camelCase mode.
Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas. All other settings are controlled and provided
to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with
the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition
or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the
way you intend.
Validation
Configuration properties are automatically validated on CAS startup to report issues with configuration binding, especially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.
Indexed Settings
CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be
incremented by the adopter to allow for distinct multiple configuration blocks.
Indexing & Search
See this guide for more information.
Caching & Messaging
The Redis ticket registry layers an in-memory cache on top of Redis to assist with performance, particularly
when it comes to fetching ticket objects from Redis using SCAN or KEYS operations that execute pattern matching.
This cache is specific and isolated to the CAS server node’s memory, and is able to clean up after itself with a dedicated
expiration policy that is constructed off of the ticket’s expiration policy. Each cache inside an individual CAS server node
will attempt to synchronize ticket changes and updates with other CAS server nodes via a message-based mechanism backed by
Redis itself. Note that you can always entirely disable the caching mechanism by forcing its maximum capacity to be at zero
via dedicated CAS settings.
The following settings and properties are available from the CAS configuration catalog:
cas.ticket.registry.redis.cache.cache-sizeThis cache size specifies the maximum number of entries the cache may contain.
10000This cache size specifies the maximum number of entries the cache may contain. Note that the cache may evict an entry before this limit is exceeded or temporarily exceed the threshold while evicting. As the cache size grows close to the maximum, the cache evicts entries that are less likely to be used again. For example, the cache may evict an entry because it hasn't been used recently or very often. Note: to disable the cache, you may choose a cache size of 0.
cas.ticket.registry.redis.cache.initial-capacityThis cache capacity sets the minimum total size for the internal data structures.
1000This cache capacity sets the minimum total size for the internal data structures. Providing a large enough estimate at construction time avoids the need for expensive resizing operations later, but setting this value unnecessarily high wastes memory.
Required settings may be needed to activate or affect the feature; review them even when they have a default. Optional settings only need to be set to change a default or to turn on the behavior they control. Third party settings belong to libraries such as Spring Boot that CAS builds on; their own documentation may have more detail.
Notes on configuration
Configuration Metadata
The collection of configuration properties listed in this section are automatically generated from the CAS source and components that contain the actual field definitions, types, descriptions, modules, etc. This metadata may not always be 100% accurate, or could be lacking details and sufficient explanations.
Be Selective
This section is meant as a guide only. Do NOT copy/paste the entire collection of settings into your CAS configuration; rather pick only the properties that you need. Do NOT enable settings unless you are certain of their purpose and do NOT copy settings into your configuration only to keep them as reference. All these ideas lead to upgrade headaches, maintenance nightmares and premature aging.
YAGNI
Note that for nearly ALL use cases, declaring and configuring properties listed here is sufficient. You should NOT have to explicitly massage a CAS XML/Java/etc configuration file to design an authentication handler, create attribute release policies, etc. CAS at runtime will auto-configure all required changes for you. If you are unsure about the meaning of a given CAS setting, do NOT turn it on without hesitation. Review the codebase or better yet, ask questions to clarify the intended behavior.
Naming Convention
Property names can be specified in very relaxed terms. For instance cas.someProperty, cas.some-property, cas.some_property are all valid names. While all
forms are accepted by CAS, there are certain components (in CAS and other frameworks used) whose activation at runtime is conditional on a property value, where
this property is required to have been specified in CAS configuration using kebab case. This is both true for properties that are owned by CAS as well as those
that might be presented to the system via an external library or framework such as Spring Boot, etc.
Note
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions) MUST remain in camelCase mode.
Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas. All other settings are controlled and provided
to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with
the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition
or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the
way you intend.
Validation
Configuration properties are automatically validated on CAS startup to report issues with configuration binding, especially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.
Indexed Settings
CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be
incremented by the adopter to allow for distinct multiple configuration blocks.
Actuator Endpoints
The following endpoints are provided by CAS:
redisTicketsCache
| Name | In | Type | Description |
|---|---|---|---|
ticketIdrequired
|
query | – | The ticket id to fetch |
- Returns
ResponseEntity- Produces
application/json- Java method
fetchTicket(String)- Defined in
RedisTicketRegistryCacheEndpoint
| Name | In | Type | Description |
|---|---|---|---|
ticketIdrequired
|
query | – | The ticket id to invalidate |
- Returns
ResponseEntity- Produces
application/json- Java method
invalidateTicket(String)- Defined in
RedisTicketRegistryCacheEndpoint
Turn the endpoint on and expose it over the web.
One entry covers every operation. By default only info, health and status are exposed.
1
2
management.endpoint.redisTicketsCache.access=UNRESTRICTED
management.endpoints.web.exposure.include=redisTicketsCache
1
2
3
4
5
6
7
8
management:
endpoint:
redisTicketsCache:
access: "UNRESTRICTED"
endpoints:
web:
exposure:
include: "redisTicketsCache"
1
2
MANAGEMENT_ENDPOINT_REDISTICKETSCACHE_ACCESS=UNRESTRICTED
MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=redisTicketsCache
Endpoints may be mapped to other paths. For example, to serve health at healthcheck:
1
management.endpoints.web.path-mapping.health=healthcheck
Once exposed, every call goes through Spring Security,
and CAS decides access per endpoint. Without a rule, the special defaults endpoint applies, which denies access.
1
cas.monitor.endpoints.endpoint.redisTicketsCache.access=AUTHENTICATED
1
2
3
4
5
6
cas:
monitor:
endpoints:
endpoint:
redisTicketsCache:
access: "AUTHENTICATED"
1
CAS_MONITOR_ENDPOINTS_ENDPOINT_REDISTICKETSCACHE_ACCESS=AUTHENTICATED
1
2
cas.monitor.endpoints.endpoint.redisTicketsCache.access=ROLE
cas.monitor.endpoints.endpoint.redisTicketsCache.required-roles=ADMIN
1
2
3
4
5
6
7
cas:
monitor:
endpoints:
endpoint:
redisTicketsCache:
access: "ROLE"
required-roles: "ADMIN"
1
2
CAS_MONITOR_ENDPOINTS_ENDPOINT_REDISTICKETSCACHE_ACCESS=ROLE
CAS_MONITOR_ENDPOINTS_ENDPOINT_REDISTICKETSCACHE_REQUIREDROLES=ADMIN
1
2
cas.monitor.endpoints.endpoint.redisTicketsCache.access=IP_ADDRESS
cas.monitor.endpoints.endpoint.redisTicketsCache.required-ip-addresses=127.0.0.1
1
2
3
4
5
6
7
cas:
monitor:
endpoints:
endpoint:
redisTicketsCache:
access: "IP_ADDRESS"
required-ip-addresses: "127.0.0.1"
1
2
CAS_MONITOR_ENDPOINTS_ENDPOINT_REDISTICKETSCACHE_ACCESS=IP_ADDRESS
CAS_MONITOR_ENDPOINTS_ENDPOINT_REDISTICKETSCACHE_REQUIREDIPADDRESSES=127.0.0.1
1
cas.monitor.endpoints.endpoint.redisTicketsCache.access=PERMIT
1
2
3
4
5
6
cas:
monitor:
endpoints:
endpoint:
redisTicketsCache:
access: "PERMIT"
1
CAS_MONITOR_ENDPOINTS_ENDPOINT_REDISTICKETSCACHE_ACCESS=PERMIT
A single user defined in CAS settings. If the name and password are left undefined, CAS generates them at startup.
spring.security.user.nameDefault user name.
userDefault user name.
spring.security.user.passwordPassword for the default user name.
Password for the default user name.
spring.security.user.rolesGranted roles for the default user name.
Granted roles for the default user name.
cas.monitor.endpoints.jaas.login-configJAAS login resource file.
JAAS login resource file.
cas.monitor.endpoints.jaas.login-context-nameThe login context name should coincide with a given index in the login config specified.
The login context name should coincide with a given index in the login config specified. This name is used as the index to the configuration specified in the login config property.
JAASTest { org.springframework.security.authentication.jaas.TestLoginModule required; }; In the above example, JAASTest should be set as the context name.cas.monitor.endpoints.jaas.refresh-configuration-on-startupIf set, a call to Configuration#refresh() will be made by #configureJaas(Resource) method.
trueIf set, a call to Configuration#refresh() will be made by #configureJaas(Resource) method.
cas.monitor.endpoints.ldap.base-dnBase DN to use.
Base DN to use. There may be scenarios where different parts of a single LDAP tree could be considered as base-dns. Rather than duplicating the LDAP configuration block for each individual base-dn, each entry can be specified and joined together using a special delimiter character. The user DN is retrieved using the combination of all base-dn and DN resolvers in the order defined. DN resolution should fail if multiple DNs are found. Otherwise the first DN found is returned. Usual syntax is: subtreeA,dc=example,dc=net|subtreeC,dc=example,dc=net.
cas.monitor.endpoints.ldap.bind-credentialThe bind credential to use when connecting to LDAP.
The bind credential to use when connecting to LDAP.
cas.monitor.endpoints.ldap.bind-dnThe bind DN to use when connecting to LDAP.
-
bindDn/bindCredentialprovided - Use the provided credentials to bind when initializing connections. -
bindDn/bindCredentialset to*- Use a fast-bind strategy to initialize the pool. -
bindDn/bindCredentialset to blank - Skip connection initializing; perform operations anonymously. - SASL mechanism provided - Use the given SASL mechanism to bind when initializing connections.
cas.monitor.endpoints.ldap.ldap-urlThe LDAP url to the server.
The LDAP url to the server. More than one may be specified, separated by space and/or comma.
cas.monitor.endpoints.ldap.search-filterUser filter to use for searching.
User filter to use for searching. Syntax is cn={user} or cn={0}.
You may also provide an external groovy script in the syntax of file:/path/to/GroovyScript.groovy to fully build the final filter template dynamically.
cas.monitor.endpoints.ldap.typeThe authentication type.
AUTHENTICATED-
AD- Users authenticate withsAMAccountName. -
AUTHENTICATED- Manager bind/search type of authentication. If {@code} principalAttributePassword} is empty then a user simple bind is done to validate credentials. Otherwise the given attribute is compared with the givenprincipalAttributePasswordusing theSHAencrypted value of it. -
ANONYMOUS: Similar semantics asAUTHENTICATEDexcept nobindDnandbindCredentialmay be specified to initialize the connection. IfprincipalAttributePasswordis empty then a user simple bind is done to validate credentials. Otherwise the given attribute is compared with the givenprincipalAttributePasswordusing theSHAencrypted value of it. - DIRECT: Direct Bind - Compute user DN from format string and perform simple bind. This is relevant when no search is required to compute the DN needed for a bind operation. Use cases for this type are: 1) All users are under a single branch in the directory,
e.g. ou=Users,dc=example,dc=org.2) The username provided on the CAS login form is part of the DN, e.g.uid=%s,ou=Users,dc=example,dc=org.
-
AD: Active Directory. -
AUTHENTICATED: Authenticated Search. -
DIRECT: Direct Bind. -
ANONYMOUS: Anonymous Search.
cas.monitor.endpoints.ldap.allow-multiple-dnsWhether search/query results are allowed to match on multiple DNs, or whether a single unique DN is expected for the result.
falseWhether search/query results are allowed to match on multiple DNs, or whether a single unique DN is expected for the result.
cas.monitor.endpoints.ldap.allow-multiple-entriesSet if multiple Entries are allowed.
falseSet if multiple Entries are allowed.
cas.monitor.endpoints.ldap.binary-attributesIndicate the collection of attributes that are to be tagged and processed as binary attributes by the underlying search resolver.
Indicate the collection of attributes that are to be tagged and processed as binary attributes by the underlying search resolver.
cas.monitor.endpoints.ldap.block-wait-timeThe length of time the pool will block.
PT3SThe length of time the pool will block. By default the pool will block indefinitely and there is no guarantee that waiting threads will be serviced in the order in which they made their request. This option should be used with a blocking connection pool when you need to control the exact number of connections that can be created
cas.monitor.endpoints.ldap.connect-timeoutSets the maximum amount of time that connects will block.
PT5SSets the maximum amount of time that connects will block.
cas.monitor.endpoints.ldap.connection-strategyIf multiple URLs are provided as the ldapURL this describes how each URL will be processed.
-
ACTIVE_PASSIVEFirst LDAP will be used for every request unless it fails and then the next shall be used. -
ROUND_ROBINFor each new connection the next url in the list will be used. -
RANDOMFor each new connection a random LDAP url will be selected. -
DNS_SRVLDAP urls based on DNS SRV records of the configured/given LDAP url will be used.
cas.monitor.endpoints.ldap.deref-aliasesDefine how aliases are de-referenced.
NEVER-
SEARCHING: dereference when searching the entries beneath the starting point but not when searching for the starting entry. -
FINDING: dereference when searching for the starting entry but not when searching the entries beneath the starting point. -
ALWAYS: dereference when searching for the starting entry and when searching the entries beneath the starting point.
cas.monitor.endpoints.ldap.disable-poolingWhether to use a pooled connection factory in components.
falseWhether to use a pooled connection factory in components.
cas.monitor.endpoints.ldap.dn-formatSpecify the dn format accepted by the AD authenticator, etc.
Specify the dn format accepted by the AD authenticator, etc. Example format might be uid=%s,ou=people,dc=example,dc=org.
cas.monitor.endpoints.ldap.enhance-with-entry-resolverWhether specific search entry resolvers need to be set on the authenticator, or the default should be used.
trueWhether specific search entry resolvers need to be set on the authenticator, or the default should be used.
cas.monitor.endpoints.ldap.fail-fastAttempt to populate the connection pool early on startup and fail quickly if something goes wrong.
trueAttempt to populate the connection pool early on startup and fail quickly if something goes wrong.
cas.monitor.endpoints.ldap.follow-referralsSet if search referrals should be followed.
trueSet if search referrals should be followed.
cas.monitor.endpoints.ldap.hostname-verifierHostname verification options.
DEFAULT-
DEFAULT: Default option, forcing verification. -
ANY: Skip hostname verification and allow all.
cas.monitor.endpoints.ldap.idle-timeRemoves connections from the pool based on how long they have been idle in the available queue.
PT10MRemoves connections from the pool based on how long they have been idle in the available queue. Prunes connections that have been idle for more than the indicated amount.
cas.monitor.endpoints.ldap.keystorePath to the keystore used for SSL connections.
Path to the keystore used for SSL connections. Typically contains SSL certificates for the LDAP server.
cas.monitor.endpoints.ldap.keystore-passwordKeystore password.
Keystore password.
cas.monitor.endpoints.ldap.keystore-typeThe type of keystore.
The type of keystore. PKCS12 or JKS. If left blank, defaults to the default keystore type indicated by the underlying Java platform.
cas.monitor.endpoints.ldap.ldap-authz.allow-multiple-resultsIndicate whether the LDAP search query is allowed to return multiple entries.
falseIndicate whether the LDAP search query is allowed to return multiple entries.
cas.monitor.endpoints.ldap.ldap-authz.base-dnBase DN to start the search.
Base DN to start the search.
cas.monitor.endpoints.ldap.ldap-authz.group-attributeAttribute expected to be found on the entry resulting from the group search whose value is going to be used to construct roles.
Attribute expected to be found on the entry resulting from the group search whose value is going to be used to construct roles. The final value is always prefixed with #groupPrefix. This is useful in scenarios where you wish to grant access to a resource to all users who a member of a given group.
cas.monitor.endpoints.ldap.ldap-authz.group-base-dnBase DN to start the search looking for groups.
Base DN to start the search looking for groups.
cas.monitor.endpoints.ldap.ldap-authz.group-filterSearch filter to begin looking for groups.
Search filter to begin looking for groups.
cas.monitor.endpoints.ldap.ldap-authz.group-prefixA prefix that is prepended to the group attribute value to construct an authorized role.
A prefix that is prepended to the group attribute value to construct an authorized role.
cas.monitor.endpoints.ldap.ldap-authz.role-attributeAttribute expected to be found on the entry whose value is going to be used to construct roles.
uugidAttribute expected to be found on the entry whose value is going to be used to construct roles. The final value is always prefixed with #rolePrefix. This is useful in scenarios where you wish to grant access to a resource to all users who carry a special attribute.
cas.monitor.endpoints.ldap.ldap-authz.role-prefixPrefix for the role.
ROLE_Prefix for the role.
cas.monitor.endpoints.ldap.ldap-authz.search-filterLDAP search filter to locate accounts.
LDAP search filter to locate accounts.
cas.monitor.endpoints.ldap.max-pool-sizeMaximum LDAP connection pool size which the pool can use to grow.
10Maximum LDAP connection pool size which the pool can use to grow.
cas.monitor.endpoints.ldap.min-pool-sizeMinimum LDAP connection pool size.
3Minimum LDAP connection pool size. Size the pool should be initialized to and pruned to
cas.monitor.endpoints.ldap.nameName of the LDAP handler.
Name of the LDAP handler.
cas.monitor.endpoints.ldap.page-sizeRequest that the server return results in batches of a specific size.
0Request that the server return results in batches of a specific size. See RFC 2696. This control is often used to work around server result size limits. A negative/zero value disables paged requests.
cas.monitor.endpoints.ldap.pool-passivatorYou may receive unexpected LDAP failures, when CAS is configured to authenticate using DIRECT or AUTHENTICATED types and LDAP is locked down to not allow anonymous binds/searches.
BINDDIRECT or AUTHENTICATED types and LDAP is locked down to not allow anonymous binds/searches. Every second attempt with a given LDAP connection from the pool would fail if it was on the same connection as a failed login attempt, and the regular connection validator would similarly fail. When a connection is returned back to a pool, it still may contain the principal and credentials from the previous attempt. Before the next bind attempt using that connection, the validator tries to validate the connection again but fails because it’s no longer trying with the configured bind credentials but with whatever user DN was used in the previous step. Given the validation failure, the connection is closed and CAS would deny access by default. Passivators attempt to reconnect to LDAP with the configured bind credentials, effectively resetting the connection to what it should be after each bind request. Furthermore if you are seeing errors in the logs that resemble a 'Operation exception encountered, reopening connection' type of message, this usually is an indication that the connection pool’s validation timeout established and created by CAS is greater than the timeout configured in the LDAP server, or more likely, in the load balancer in front of the LDAP servers. You can adjust the LDAP server session’s timeout for connections, or you can teach CAS to use a validity period that is equal or less than the LDAP server session’s timeout. Accepted values are: -
NONE: No passivation takes place. -
BIND: The default behavior which passivates a connection by performing a bind operation on it. This option requires the availability of bind credentials when establishing connections to LDAP.
cas.monitor.endpoints.ldap.principal-attribute-passwordIf principalAttributePassword is empty then a user simple bind is done to validate credentials otherwise the given attribute is compared with the given principalAttributePassword using the SHA encrypted value of it.
If principalAttributePassword is empty then a user simple bind is done to validate credentials otherwise the given attribute is compared with the given principalAttributePassword using the SHA encrypted value of it.
For the anonymous authentication type, if principalAttributePassword is empty then a user simple bind is done to validate credentials otherwise the given attribute is compared with the given principalAttributePassword using the SHA encrypted value of it.
cas.monitor.endpoints.ldap.prune-periodRemoves connections from the pool based on how long they have been idle in the available queue.
PT2HRemoves connections from the pool based on how long they have been idle in the available queue. Run the pruning process at the indicated interval.
cas.monitor.endpoints.ldap.resolve-from-attributeIf this attribute is set, the value found in the first attribute value will be used in place of the DN.
If this attribute is set, the value found in the first attribute value will be used in place of the DN.
cas.monitor.endpoints.ldap.response-timeoutDuration of time to wait for responses.
PT5SDuration of time to wait for responses.
cas.monitor.endpoints.ldap.sasl-authorization-idSASL authorization id.
SASL authorization id.
cas.monitor.endpoints.ldap.sasl-mechanismThe SASL mechanism.
The SASL mechanism.
cas.monitor.endpoints.ldap.sasl-mutual-authWhether SASL mutual authentication is enabled.
Whether SASL mutual authentication is enabled.
cas.monitor.endpoints.ldap.sasl-quality-of-protectionSASL quality of protected.
SASL quality of protected.
cas.monitor.endpoints.ldap.sasl-realmThe SASL realm.
The SASL realm.
cas.monitor.endpoints.ldap.sasl-security-strengthSASL security strength.
SASL security strength.
cas.monitor.endpoints.ldap.search-entry-handlersSearch handlers.
Search handlers.
cas.monitor.endpoints.ldap.search-entry-handlers[0].case-change.attribute-name-case-changeThe Attribute name case change.
The Attribute name case change.
cas.monitor.endpoints.ldap.search-entry-handlers[0].case-change.attribute-namesThe Attribute names.
The Attribute names.
cas.monitor.endpoints.ldap.search-entry-handlers[0].case-change.attribute-value-case-changeThe Attribute value case change.
The Attribute value case change.
cas.monitor.endpoints.ldap.search-entry-handlers[0].case-change.dn-case-changeThe Dn case change.
The Dn case change.
cas.monitor.endpoints.ldap.search-entry-handlers[0].dn-attribute.add-if-existsThe Add if exists.
The Add if exists.
cas.monitor.endpoints.ldap.search-entry-handlers[0].dn-attribute.dn-attribute-nameThe Dn attribute name.
entryDNThe Dn attribute name.
cas.monitor.endpoints.ldap.search-entry-handlers[0].merge-attribute.attribute-namesThe Attribute names.
The Attribute names.
cas.monitor.endpoints.ldap.search-entry-handlers[0].merge-attribute.merge-attribute-nameThe Merge attribute name.
The Merge attribute name.
cas.monitor.endpoints.ldap.search-entry-handlers[0].primary-group-id.base-dnThe Base dn.
The Base dn.
cas.monitor.endpoints.ldap.search-entry-handlers[0].primary-group-id.group-filterThe Group filter.
(&(objectClass=group)(objectSid={0}))The Group filter.
cas.monitor.endpoints.ldap.search-entry-handlers[0].recursive.merge-attributesThe Merge attributes.
The Merge attributes.
cas.monitor.endpoints.ldap.search-entry-handlers[0].recursive.search-attributeThe Search attribute.
The Search attribute.
cas.monitor.endpoints.ldap.search-entry-handlers[0].search-referral.limitThe default referral limit.
10The default referral limit.
cas.monitor.endpoints.ldap.search-entry-handlers[0].search-result.limitThe default referral limit.
10The default referral limit.
cas.monitor.endpoints.ldap.search-entry-handlers[0].typeThe type of search entry handler to choose.
-
FOLLOW_SEARCH_REFERRAL: Provides handling of an ldap referral for search operations. -
FOLLOW_SEARCH_RESULT_REFERENCE: Provides handling of an ldap continuation reference for search operations. -
ACTIVE_DIRECTORY: Process the entry results fetched from active directory and check for account status controls for disabled/expired accounts, etc. -
OBJECT_GUID: Object guid search entry handler. Handles theobjectGUIDattribute fetching and conversion. -
OBJECT_SID: Object sid search entry handler. Handles theobjectSidattribute fetching and conversion. -
CASE_CHANGE: Case change search entry handler. Provides the ability to modify the case of search entry DNs, attribute names, and attribute values. -
DN_ATTRIBUTE_ENTRY: DN attribute entry handler. Adds the entry DN as an attribute to the result set. Provides a client side implementation of RFC 5020. -
MERGE: Merge search entry handler. Merges the values of one or more attributes into a single attribute. -
PRIMARY_GROUP: Primary group search handler. Constructs the primary group SID and then searches for that group and puts it's DN in thememberOfattribute of the original search entry. -
RANGE_ENTRY: Range entry search handler. Rewrites attributes returned from Active Directory to include all values by performing additional searches. -
RECURSIVE_ENTRY: Recursive entry search handler. This recursively searches based on a supplied attribute and merges those results into the original entry. -
MERGE_ENTRIES: Merge entries handler. Merges the values of one or more attributes in all entries into a single attribute. The merged attribute may or may not already exist on the entry. If it does exist it's existing values will remain intact.
cas.monitor.endpoints.ldap.subtree-searchWhether subtree searching is allowed.
trueWhether subtree searching is allowed.
cas.monitor.endpoints.ldap.trust-certificatesPath of the trust certificates to use for the SSL connection.
Path of the trust certificates to use for the SSL connection. Ignores keystore-related settings when activated and used.
cas.monitor.endpoints.ldap.trust-managerTrust Manager options.
-
DEFAULT: Enable and force the default JVM trust managers. -
ANY: Trust any client or server.
cas.monitor.endpoints.ldap.trust-storePath to the keystore used to determine which certificates or certificate authorities should be trusted.
Path to the keystore used to determine which certificates or certificate authorities should be trusted. Used when connecting to an LDAP server via LDAPS or startTLS connection. If left blank, the default truststore for the Java runtime is used.
cas.monitor.endpoints.ldap.trust-store-passwordPassword needed to open the truststore.
Password needed to open the truststore.
cas.monitor.endpoints.ldap.trust-store-typeThe type of trust keystore that determines which certificates or certificate authorities are trusted.
The type of trust keystore that determines which certificates or certificate authorities are trusted. Types depend on underlying java platform, typically PKCS12 or JKS. If left blank, defaults to the default keystore type indicated by the underlying Java platform.
cas.monitor.endpoints.ldap.use-start-tlsWhether TLS should be used and enabled when establishing the connection.
falseWhether TLS should be used and enabled when establishing the connection.
cas.monitor.endpoints.ldap.validate-on-checkoutWhether connections should be validated when loaned out from the pool.
trueWhether connections should be validated when loaned out from the pool.
cas.monitor.endpoints.ldap.validate-periodPeriod at which pool should be validated.
PT5MPeriod at which pool should be validated.
cas.monitor.endpoints.ldap.validate-periodicallyWhether connections should be validated periodically when the pool is idle.
trueWhether connections should be validated periodically when the pool is idle.
cas.monitor.endpoints.ldap.validate-timeoutPeriod at which validation operations may time out.
PT5SPeriod at which validation operations may time out.
cas.monitor.endpoints.ldap.validator.attribute-nameAttribute name to use for the compare validator.
objectClassAttribute name to use for the compare validator.
cas.monitor.endpoints.ldap.validator.attribute-valueAttribute values to use for the compare validator.
topAttribute values to use for the compare validator.
cas.monitor.endpoints.ldap.validator.base-dnBase DN to use for the search request of the search validator.
Base DN to use for the search request of the search validator.
cas.monitor.endpoints.ldap.validator.dnDN to compare to use for the compare validator.
DN to compare to use for the compare validator.
cas.monitor.endpoints.ldap.validator.scopeSearch scope to use for the search request of the search validator.
OBJECTSearch scope to use for the search request of the search validator.
cas.monitor.endpoints.ldap.validator.search-filterSearch filter to use for the search request of the search validator.
(objectClass=*)Search filter to use for the search request of the search validator.
cas.monitor.endpoints.ldap.validator.typeDetermine the LDAP validator type.
searchDetermine the LDAP validator type.
-
search: Validates a connection is healthy by performing a search operation. Validation is considered successful if the search result size is greater than zero. -
none: No validation takes place. -
compare: Validates a connection is healthy by performing a compare operation.
LDAP & Active Directory
LDAP Scriptable Search Filter
LDAP search filters can point to an external Groovy script to dynamically construct the final filter template.
The script itself may be designed as:
1
2
3
4
5
6
7
8
9
import org.ldaptive.*
import org.springframework.context.*
def run(Object[] args) {
def (filter,parameters,applicationContext,logger) = args
logger.info("Configuring LDAP filter")
filter.setFilter("uid=something")
}
The following parameters are passed to the script:
| Parameter | Description |
|---|---|
filter |
FilterTemplate to be updated by the script and used for the LDAP query. |
parameters |
Map of query parameters which may be used to construct the final filter. |
applicationContext |
Reference to the Spring ApplicationContext reference. |
logger |
The object responsible for issuing log messages such as logger.info(...). |
To prepare CAS to support and integrate with Apache Groovy, please review this guide.
cas.monitor.endpoints.jdbc.driver-classThe JDBC driver used to connect to the database.
org.hsqldb.jdbcDriverThe JDBC driver used to connect to the database.
cas.monitor.endpoints.jdbc.passwordThe database connection password.
The database connection password.
cas.monitor.endpoints.jdbc.password-encoder.encoding-algorithmThe encoding algorithm to use such as MD5 .
The encoding algorithm to use such as MD5. Relevant when the type used is DEFAULT or GLIBC_CRYPT. When used with PasswordEncoderTypes#PBKDF2, it should be one of PBKDF2WithHmacSHA1, PBKDF2WithHmacSHA256 or PBKDF2WithHmacSHA512.
cas.monitor.endpoints.jdbc.password-encoder.typeDefine the password encoder type to use.
NONEDefine the password encoder type to use. Type may be specified as blank or NONE to disable password encoding. It may also refer to a fully-qualified class name that implements the Spring Security's PasswordEncoder interface if you wish you define your own encoder.
-
NONE: No password encoding (i.e. plain-text) takes place. -
DEFAULT: Use theDefaultPasswordEncoderof CAS. For message-digest algorithms viacharacter-encodingandencoding-algorithm. -
BCRYPT: Use theBCryptPasswordEncoderbased on the strength provided and an optional secret. -
SCRYPT: Use theSCryptPasswordEncoder. -
PBKDF2: Use thePbkdf2PasswordEncoderbased on the strength provided and an optional secret. -
STANDARD: Use theStandardPasswordEncoderbased on the secret provided. -
SSHA: Use theLdapShaPasswordEncodersupports Ldap SHA and SSHA (salted-SHA). The values are base-64 encoded and have the label {SHA} or {SSHA} prepended to the encoded hash. -
GLIBC_CRYPT: Use theGlibcCryptPasswordEncoderbased on theencoding-algorithm, strength provided and an optional secret. -
org.example.MyEncoder: An implementation ofPasswordEncoderof your own choosing. -
file:///path/to/script.groovy: Path to a Groovy script charged with handling password encoding operations.
cas.monitor.endpoints.jdbc.urlThe database connection URL.
jdbc:hsqldb:mem:cas-hsql-databaseThe database connection URL.
cas.monitor.endpoints.jdbc.userThe database user.
saThe database user.
The database user must have sufficient permissions to be able to handle schema changes and updates, when needed.
cas.monitor.endpoints.jdbc.autocommitThe default auto-commit behavior of connections in the pool.
falseThe default auto-commit behavior of connections in the pool. Determined whether queries such as update/insert should be immediately executed without waiting for an underlying transaction.
cas.monitor.endpoints.jdbc.batch-sizeA non-zero value enables use of JDBC2 batch updates by Hibernate. e.g. recommended values between 5 and 30.
100A non-zero value enables use of JDBC2 batch updates by Hibernate. e.g. recommended values between 5 and 30.
cas.monitor.endpoints.jdbc.connection-timeoutIndicates the maximum number of milliseconds that the service can wait to obtain a connection.
PT30SIndicates the maximum number of milliseconds that the service can wait to obtain a connection.
cas.monitor.endpoints.jdbc.data-source-nameAttempts to do a JNDI data source look up for the data source name specified.
Attempts to do a JNDI data source look up for the data source name specified. Will attempt to locate the data source object as is.
cas.monitor.endpoints.jdbc.ddl-autoHibernate feature to automatically validate and exports DDL to the schema.
updatevalidate or none may be more desirable for production, but any of the following options can be used: -
validate: Validate the schema, but make no changes to the database. -
update: Update the schema. -
create: Create the schema, destroying previous data. -
create-drop: Drop the schema at the end of the session. -
none: Do nothing.
Note that during a version migration where any schema has changed create-drop will result in the loss of all data as soon as CAS is started. For transient data like tickets this is probably not an issue, but in cases like the audit table important data could be lost. Using `update`, while safe for data, is confirmed to result in invalid database state. validate or none settings are likely the only safe options for production use.
For more info, see this.
cas.monitor.endpoints.jdbc.default-catalogQualifies unqualified table names with the given catalog in generated SQL.
Qualifies unqualified table names with the given catalog in generated SQL.
cas.monitor.endpoints.jdbc.default-schemaQualify unqualified table names with the given schema/tablespace in generated SQL.
Qualify unqualified table names with the given schema/tablespace in generated SQL.
cas.monitor.endpoints.jdbc.dialectThe database dialect is a configuration setting for platform independent software (JPA, Hibernate, etc) which allows such software to translate its generic SQL statements into vendor specific DDL, DML.
org.hibernate.dialect.HSQLDialectThe database dialect is a configuration setting for platform independent software (JPA, Hibernate, etc) which allows such software to translate its generic SQL statements into vendor specific DDL, DML.
cas.monitor.endpoints.jdbc.fail-fast-timeoutSet the pool initialization failure timeout.
1- Any value greater than zero will be treated as a timeout for pool initialization. The calling thread will be blocked from continuing until a successful connection to the database, or until the timeout is reached. If the timeout is reached, then a
PoolInitializationExceptionwill be thrown. - A value of zero will not prevent the pool from starting in the case that a connection cannot be obtained. However, upon start the pool will attempt to obtain a connection and validate that the
connectionTestQueryandconnectionInitSqlare valid. If those validations fail, an exception will be thrown. If a connection cannot be obtained, the validation is skipped and the pool will start and continue to try to obtain connections in the background. This can mean that callers toDataSource#getConnection()may encounter exceptions. - A value less than zero will not bypass any connection attempt and validation during startup, and therefore the pool will start immediately. The pool will continue to try to obtain connections in the background. This can mean that callers to
DataSource#getConnection()may encounter exceptions.
connectionTimeout or validationTimeout; they will be honored before this timeout is applied. The default value is one millisecond.cas.monitor.endpoints.jdbc.fetch-sizeUsed to specify number of rows to be fetched in a select query.
100Used to specify number of rows to be fetched in a select query.
cas.monitor.endpoints.jdbc.generate-statisticsAllow hibernate to generate query statistics.
falseAllow hibernate to generate query statistics.
cas.monitor.endpoints.jdbc.health-queryThe SQL query to be executed to test the validity of connections.
The SQL query to be executed to test the validity of connections. This is for "legacy" databases that do not support the JDBC4 Connection.isValid() API.
cas.monitor.endpoints.jdbc.idle-timeoutControls the maximum amount of time that a connection is allowed to sit idle in the pool.
PT10MControls the maximum amount of time that a connection is allowed to sit idle in the pool.
cas.monitor.endpoints.jdbc.isolate-internal-queriesThis property determines whether data source isolates internal pool queries, such as the connection alive test, in their own transaction.
falseThis property determines whether data source isolates internal pool queries, such as the connection alive test, in their own transaction.
Since these are typically read-only queries, it is rarely necessary to encapsulate them in their own transaction. This property only applies if #autocommit is disabled.
cas.monitor.endpoints.jdbc.isolation-level-nameDefines the isolation level for transactions.
ISOLATION_READ_COMMITTEDDefines the isolation level for transactions. @see org.springframework.transaction.TransactionDefinition
cas.monitor.endpoints.jdbc.leak-thresholdControls the amount of time that a connection can be out of the pool before a message is logged indicating a possible connection leak.
PT6SControls the amount of time that a connection can be out of the pool before a message is logged indicating a possible connection leak.
cas.monitor.endpoints.jdbc.password-encoder.character-encodingThe encoding algorithm to use such as 'UTF-8'.
UTF-8The encoding algorithm to use such as 'UTF-8'. Relevant when the type used is DEFAULT.
cas.monitor.endpoints.jdbc.password-encoder.hash-lengthWhen used by PasswordEncoderTypes#ARGON2 , it indicates the hash strength/length.
16When used by PasswordEncoderTypes#ARGON2, it indicates the hash strength/length.
cas.monitor.endpoints.jdbc.password-encoder.iterationsWhen used by PasswordEncoderTypes#PBKDF2 , it indicates the required number of iterations.
310000When used by PasswordEncoderTypes#PBKDF2, it indicates the required number of iterations.
cas.monitor.endpoints.jdbc.password-encoder.secretSecret to use with PasswordEncoderTypes#STANDARD , PasswordEncoderTypes#PBKDF2 , PasswordEncoderTypes#BCRYPT , PasswordEncoderTypes#GLIBC_CRYPT password encoders.
Secret to use with PasswordEncoderTypes#STANDARD, PasswordEncoderTypes#PBKDF2, PasswordEncoderTypes#BCRYPT, PasswordEncoderTypes#GLIBC_CRYPT password encoders. Secret usually is an optional setting.
cas.monitor.endpoints.jdbc.password-encoder.strengthStrength or number of iterations to use for password hashing.
16Strength or number of iterations to use for password hashing. Usually relevant when dealing with PasswordEncoderTypes#BCRYPT, PasswordEncoderTypes#PBKDF2 or PasswordEncoderTypes#GLIBC_CRYPT. When used by PasswordEncoderTypes#ARGON2 or PasswordEncoderTypes#PBKDF2, it indicates the salt strength.
cas.monitor.endpoints.jdbc.physical-naming-strategy-class-nameFully-qualified name of the class that can control the physical naming strategy of hibernate.
org.apereo.cas.hibernate.CasHibernatePhysicalNamingStrategyFully-qualified name of the class that can control the physical naming strategy of hibernate.
cas.monitor.endpoints.jdbc.pool.keep-alive-timeThis property controls the keepalive interval for a connection in the pool.
0This property controls the keepalive interval for a connection in the pool. An in-use connection will never be tested by the keepalive thread, only when it is idle will it be tested. Default is zero, which disables this feature.
cas.monitor.endpoints.jdbc.pool.max-sizeControls the maximum number of connections to keep in the pool, including both idle and in-use connections.
18Controls the maximum number of connections to keep in the pool, including both idle and in-use connections.
cas.monitor.endpoints.jdbc.pool.max-waitSets the maximum time in seconds that this data source will wait while attempting to connect to a database.
PT2SSets the maximum time in seconds that this data source will wait while attempting to connect to a database.
A value of zero specifies that the timeout is the default system timeout if there is one; otherwise, it specifies that there is no timeout.
cas.monitor.endpoints.jdbc.pool.maximum-lifetimeThis property controls the maximum lifetime of a connection in the pool.
PT10MThis property controls the maximum lifetime of a connection in the pool. When a connection reaches this timeout, even if recently used, it will be retired from the pool. An in-use connection will never be retired, only when it is idle will it be removed.
cas.monitor.endpoints.jdbc.pool.min-sizeControls the minimum size that the pool is allowed to reach, including both idle and in-use connections.
6Controls the minimum size that the pool is allowed to reach, including both idle and in-use connections.
cas.monitor.endpoints.jdbc.pool.nameSet the name of the connection pool.
Set the name of the connection pool. This is primarily used for the MBean to uniquely identify the pool configuration.
cas.monitor.endpoints.jdbc.pool.suspensionWhether or not pool suspension is allowed.
falseWhether or not pool suspension is allowed.
There is a performance impact when pool suspension is enabled. Unless you need it (for a redundancy system for example) do not enable it.
cas.monitor.endpoints.jdbc.pool.timeout-millisThe maximum number of milliseconds that the pool will wait for a connection to be validated as alive.
1000The maximum number of milliseconds that the pool will wait for a connection to be validated as alive.
cas.monitor.endpoints.jdbc.propagation-behavior-nameDefines the propagation behavior for transactions.
PROPAGATION_REQUIREDDefines the propagation behavior for transactions. @see org.springframework.transaction.TransactionDefinition
cas.monitor.endpoints.jdbc.propertiesAdditional settings provided by Hibernate (or the connection provider) in form of key-value pairs.
Additional settings provided by Hibernate (or the connection provider) in form of key-value pairs.
cas.monitor.endpoints.jdbc.queryQuery to execute in order to authenticate users via JDBC.
Query to execute in order to authenticate users via JDBC. Example: SELECT username,password,enabled FROM users WHERE username=?
cas.monitor.endpoints.jdbc.read-onlyConfigures the Connections to be added to the pool as read-only Connections.
falseConfigures the Connections to be added to the pool as read-only Connections.
cas.monitor.endpoints.jdbc.role-prefixPrefix to add to the role.
Prefix to add to the role.
Hibernate & JDBC
Control global properties that are relevant to Hibernate, when CAS attempts to employ and utilize database resources, connections and queries.
cas.jdbc.gen-ddlWhether to generate DDL after the EntityManagerFactory has been initialized creating/updating all relevant tables.
trueWhether to generate DDL after the EntityManagerFactory has been initialized creating/updating all relevant tables.
cas.jdbc.physical-table-namesIndicate a physical table name to be used by the hibernate naming strategy in case table names need to be customized for the specific type of database.
Indicate a physical table name to be used by the hibernate naming strategy in case table names need to be customized for the specific type of database. The key here indicates the CAS-provided table name and the value is the translate physical name for the database. If a match is not found for the CAS-provided table name, then that name will be used by default.
cas.jdbc.show-sqlWhether SQL queries should be displayed in the console/logs.
falseWhether SQL queries should be displayed in the console/logs.
Password encoding
If you need to design your own password encoding scheme where the type is specified as a fully qualified Java class name, the structure of the class would be similar to the following:
1
2
3
4
5
6
7
8
9
10
11
package org.example.cas;
import org.springframework.security.crypto.codec.*;
import org.springframework.security.crypto.password.*;
public class MyEncoder extends AbstractPasswordEncoder {
@Override
protected byte[] encode(CharSequence rawPassword, byte[] salt) {
return ...
}
}
If you need to design your own password encoding scheme where the type is specified as a path to a Groovy script, the structure of the script would be similar to the following:
1
2
3
4
5
6
7
8
9
10
11
12
import java.util.*
byte[] run(final Object... args) {
def (rawPassword,generatedSalt,logger,applicationContext) = args
logger.debug("Encoding password...")
return ...
}
Boolean matches(final Object... args) {
def (rawPassword,encodedPassword,logger,applicationContext) = args
logger.debug("Does match or not ?");
return ...
To prepare CAS to support and integrate with Apache Groovy, please review this guide.
A static list of users, passwords and roles in a JSON file.
Supported password encodings are {sha512}, {sha256}, {bcrypt},
{noop}, {pbkdf2}, {scrypt} and {argon2}.
1
2
3
4
5
6
7
[
{
"username": "casuser",
"password": "{sha512}<hashed-password>",
"authorities": [ "ROLE_ADMIN" ]
}
]
cas.monitor.endpoints.json.locationThe location of the resource.
The location of the resource. Resources can be URLs, or files found either on the classpath or outside somewhere in the file system.
In the event the configured resource is a Groovy script, especially if the script is set to reload on changes, you may need to adjust the total number of inotify instances. On Linux, you may need to add the following line to /etc/sysctl.conf: fs.inotify.max_user_instances = 256.
You can check the current value via cat /proc/sys/fs/inotify/max_user_instances.
In situations and scenarios where CAS is able to automatically watch the underlying resource for changes and detect updates and modifications dynamically, you may be able to specify the following setting as either an environment variable or system property with a value of false to disable the resource watcher: org.apereo.cas.util.io.PathWatcherService.
cas.monitor.endpoints.endpoint.redisTicketsCache.accessDefine the security access level of the endpoint.
DENY-
PERMIT: Allow open access to the endpoint. -
ANONYMOUS: Allow anonymous access to the endpoint. -
DENY: Block access to the endpoint. -
AUTHENTICATED: Require authenticated access to the endpoint. -
ROLE: Require authenticated access to the endpoint along with a role requirement. -
AUTHORITY: Require authenticated access to the endpoint along with an authority requirement. -
IP_ADDRESS: Require authenticated access to the endpoint using a collection of IP addresses.
cas.monitor.endpoints.endpoint.redisTicketsCache.required-authoritiesRequired user authorities.
Required user authorities.
cas.monitor.endpoints.endpoint.redisTicketsCache.required-ip-addressesRequired IP addresses.
Required IP addresses. CIDR ranges are accepted.
cas.monitor.endpoints.endpoint.redisTicketsCache.required-rolesRequired user roles.
Required user roles.
cas.monitor.endpoints.form-login-enabledControl whether access to endpoints can be controlled via form-based login over the web via a special admin login endpoint.
falseControl whether access to endpoints can be controlled via form-based login over the web via a special admin login endpoint.
management.endpoint.health.accessPermitted level of access for the health endpoint.
unrestrictedPermitted level of access for the health endpoint.
management.endpoint.health.cache.time-to-liveMaximum time that a response can be cached.
0msMaximum time that a response can be cached.
management.endpoint.health.groupHealth endpoint groups.
Health endpoint groups.
management.endpoint.health.logging.slow-indicator-thresholdThreshold after which a warning will be logged for slow health indicators.
10sThreshold after which a warning will be logged for slow health indicators.
management.endpoint.health.probes.add-additional-pathsWhether to make the liveness and readiness health groups available on the main server port.
falseWhether to make the liveness and readiness health groups available on the main server port.
management.endpoint.health.probes.enabledWhether to enable liveness and readiness probes.
trueWhether to enable liveness and readiness probes.
management.endpoint.health.rolesRoles used to determine whether a user is authorized to be shown details.
Roles used to determine whether a user is authorized to be shown details. When empty, all authenticated users are authorized.
management.endpoint.health.show-componentsWhen to show components.
When to show components. If not specified the 'show-details' setting will be used.
management.endpoint.health.show-detailsWhen to show full health details.
neverWhen to show full health details.
management.endpoint.health.status.http-mappingMapping of health statuses to HTTP status codes.
Mapping of health statuses to HTTP status codes. By default, registered health statuses map to sensible defaults (for example, UP maps to 200).
management.endpoint.health.status.orderList of health statuses in order of severity.
["DOWN", "OUT_OF_SERVICE", "UP", "UNKNOWN"]List of health statuses in order of severity.
management.endpoint.health.validate-group-membershipWhether to validate health group membership on startup.
trueWhether to validate health group membership on startup. Validation fails if a group includes or excludes a health contributor that does not exist.
management.endpoints.access.defaultDefault access level for all endpoints.
Default access level for all endpoints.
management.endpoints.access.max-permittedMaximum level of endpoint access that is permitted.
unrestrictedMaximum level of endpoint access that is permitted. Caps an endpoint's individual access level (management.endpoint.<id>.access) and the default access (management.endpoints.access.default).'
management.endpoints.enabled-by-defaultWhether to enable or disable all endpoints by default.
Whether to enable or disable all endpoints by default.
management.endpoints.jackson.isolated-json-mapperWhether to use an isolated JsonMapper to serialize endpoint JSON.
trueWhether to use an isolated JsonMapper to serialize endpoint JSON.
management.endpoints.jackson2.isolated-object-mapperWhether to use an isolated object mapper to serialize endpoint JSON.
trueWhether to use an isolated object mapper to serialize endpoint JSON.
management.endpoints.jmx.domainEndpoints JMX domain name.
org.springframework.bootEndpoints JMX domain name. Fallback to 'spring.jmx.default-domain' if set.
management.endpoints.jmx.exposure.excludeEndpoint IDs that should be excluded or '*' for all.
Endpoint IDs that should be excluded or '*' for all.
management.endpoints.jmx.exposure.includeEndpoint IDs that should be included or '*' for all.
healthEndpoint IDs that should be included or '*' for all.
management.endpoints.jmx.static-namesAdditional static properties to append to all ObjectNames of MBeans representing Endpoints.
Additional static properties to append to all ObjectNames of MBeans representing Endpoints.
management.endpoints.jmx.unique-namesWhether unique runtime object names should be ensured.
Whether unique runtime object names should be ensured.
management.endpoints.migrate-legacy-idsWhether to transparently migrate legacy endpoint IDs.
falseWhether to transparently migrate legacy endpoint IDs.
management.endpoints.web.base-pathBase path for Web endpoints.
/actuatorBase path for Web endpoints. Relative to the servlet context path (server.servlet.context-path) or WebFlux base path (spring.webflux.base-path) when the management server is sharing the main server port. Relative to the management server base path (management.server.base-path) when a separate management server port (management.server.port) is configured.
management.endpoints.web.cors.allow-credentialsWhether credentials are supported.
Whether credentials are supported. When not set, credentials are not supported.
management.endpoints.web.cors.allowed-headersList of headers to allow in a request. '*' allows all headers.
List of headers to allow in a request. '*' allows all headers.
management.endpoints.web.cors.allowed-methodsList of methods to allow. '*' allows all methods.
List of methods to allow. '*' allows all methods. When not set, defaults to GET.
management.endpoints.web.cors.allowed-origin-patternsList of origin patterns to allow.
List of origin patterns to allow. Unlike allowed origins which only supports '*', origin patterns are more flexible (for example 'https://*.example.com') and can be used when credentials are allowed. When no allowed origin patterns or allowed origins are set, CORS support is disabled.
management.endpoints.web.cors.allowed-originsList of origins to allow. '*' allows all origins.
List of origins to allow. '*' allows all origins. When credentials are allowed, '*' cannot be used and origin patterns should be configured instead. When no allowed origins or allowed origin patterns are set, CORS support is disabled.
management.endpoints.web.cors.exposed-headersList of headers to include in a response.
List of headers to include in a response.
management.endpoints.web.cors.max-ageHow long the response from a pre-flight request can be cached by clients.
1800sHow long the response from a pre-flight request can be cached by clients. If a duration suffix is not specified, seconds will be used.
management.endpoints.web.discovery.enabledWhether the discovery page is enabled.
trueWhether the discovery page is enabled.
management.endpoints.web.exposure.excludeEndpoint IDs that should be excluded or '*' for all.
Endpoint IDs that should be excluded or '*' for all.
management.endpoints.web.exposure.includeEndpoint IDs that should be included or '*' for all.
["health"]Endpoint IDs that should be included or '*' for all.
management.endpoints.web.path-mappingMapping between endpoint IDs and the path that should expose them.
Mapping between endpoint IDs and the path that should expose them.
management.health.binders.enabledAllows to enable/disable binder's' health indicators.
trueAllows to enable/disable binder's' health indicators. If you want to disable health indicator completely, then set it to `false`.
management.health.db.enabledWhether to enable database health check.
trueWhether to enable database health check.
management.health.db.ignore-routing-data-sourcesWhether to ignore AbstractRoutingDataSources when creating database health indicators.
falseWhether to ignore AbstractRoutingDataSources when creating database health indicators.
management.health.defaults.enabledWhether to enable default health indicators.
trueWhether to enable default health indicators.
management.health.diskspace.enabledWhether to enable disk space health check.
trueWhether to enable disk space health check.
management.health.diskspace.pathPath used to compute the available disk space.
Path used to compute the available disk space.
management.health.diskspace.thresholdMinimum disk space that should be available.
10MBMinimum disk space that should be available.
management.health.influxdb.enabled
management.health.livenessstate.enabledWhether to enable liveness state health check.
falseWhether to enable liveness state health check.
management.health.mail.enabledWhether to enable Mail health check.
trueWhether to enable Mail health check.
management.health.mongo.enabled
management.health.mongodb.enabledWhether to enable MongoDB health check.
trueWhether to enable MongoDB health check.
management.health.ping.enabledWhether to enable ping health check.
trueWhether to enable ping health check.
management.health.probes.enabledWhether to enable liveness and readiness probes.
falseWhether to enable liveness and readiness probes.
management.health.pubsub.enabledWhether to enable the Pub/Sub health indicator when used with Spring Boot Actuator.
trueWhether to enable the Pub/Sub health indicator when used with Spring Boot Actuator.
management.health.rabbit.enabledWhether to enable RabbitMQ health check.
trueWhether to enable RabbitMQ health check.
management.health.readinessstate.enabledWhether to enable readiness state health check.
falseWhether to enable readiness state health check.
management.health.redis.enabledWhether to enable Redis health check.
trueWhether to enable Redis health check.
management.health.refresh.enabledEnable the health endpoint for the refresh scope.
trueEnable the health endpoint for the refresh scope.
management.health.ssl.certificate-validity-warning-thresholdIf an SSL Certificate will be invalid within the time span defined by this threshold, it should trigger a warning.
14dIf an SSL Certificate will be invalid within the time span defined by this threshold, it should trigger a warning.
management.health.ssl.enabledWhether to enable SSL certificate health check.
trueWhether to enable SSL certificate health check.
management.health.zookeeper.enabledEnable the health endpoint for zookeeper.
trueEnable the health endpoint for zookeeper.
-
404: the endpoint is not enabled or not exposed; check the Enable & expose tab. -
401or403: the access rule or the credentials rejected the call; check the Security tab.
For more detail, raise these log levels in the log4j configuration:
1
2
3
4
5
6
7
8
<Logger name="org.apereo.cas.ticket.registry" level="debug" additivity="false">
<AppenderRef ref="console" />
<AppenderRef ref="file" />
</Logger>
<Logger name="org.springframework.security" level="debug" additivity="false">
<AppenderRef ref="console" />
<AppenderRef ref="file" />
</Logger>
Design & Performance
The Redis ticket registry treats Redis as the shared source of truth for CAS tickets, while each CAS node may keep a local in-memory cache as a first-level optimization. The local cache is per-node and is intended to reduce Redis reads and ticket deserialization for hot tickets. It should not be treated as authoritative. Ticket lookups may be served from the local cache, but ticket lifecycle operations still need to keep Redis and all node-local caches coherent.
Cache keys are derived from the Redis ticket key format, not simply from the clear ticket id in all cases. This matters when registry cryptography is enabled. In that mode, ticket identifiers and principal identifiers are digested before being used in Redis keys, so the local cache key for a ticket is also the digested form. Any cache invalidation mechanism must use the same canonical cache key that the registry uses for reads and writes. Invalidating by the clear ticket id will miss encrypted/digested cache entries and can leave stale tickets alive on other nodes.
Cluster cache coherence is handled through Redis-backed pub/sub messages. When one CAS node adds, updates, deletes, or clears tickets, it publishes a notification. Other CAS nodes receive that notification and update or invalidate their local cache. Nodes should ignore their own messages because the local registry operation has already updated the local cache directly. For deletes, the notification does not need to carry the full ticket object; it only needs enough information to identify the local cache entry, such as the Redis key or derived cache key. This avoids unnecessary Redis fetches, deserialization, and decryption during delete-heavy operations.
From a performance perspective, the important distinction is between operations that need the ticket body and operations that only need to remove state. Add and update messages naturally carry a ticket because peer caches may be populated with that object. Delete messages should avoid materializing the ticket when the registry already knows the Redis key being removed. Bulk user/session deletion paths are especially sensitive: scanning Redis, fetching each ticket, deserializing it, and decrypting it just to publish a cache invalidation can be very expensive. A better design is to scan only the required metadata, unlink matching Redis keys in batches, invalidate the local cache by canonical key, and publish delete notifications by key.
There are several operational caveats. Redis pub/sub is not durable; a node that is down, disconnected, or misconfigured when a message is published can miss the notification and retain stale local cache entries until expiration or manual cache clearing. CAS node queue identifiers must be unique per node, or left unset so they are generated uniquely; if multiple nodes share the same identifier, they may incorrectly treat each other’s notifications as self-published messages and ignore them. Administrative logout cannot remove a user’s browser cookie directly, so correctness depends on the server-side ticket deletion being authoritative across Redis and all local caches. For highly conservative deployments, disabling the local cache or setting its size to zero trades performance for simpler consistency semantics.
Eviction Policy
Redis manages the internal eviction policy of cached objects via its time-alive settings.
The timeout is the ticket’s timeToLive value. So you need to ensure the cache is alive long enough to support the
individual expiration policy of tickets, and let CAS clean the tickets as part of its own cleaner if necessary.
Redis removes expired keys in two ways. Passive expiration happens when CAS accesses a key and Redis notices that its TTL has elapsed; the key is deleted before the command proceeds. Active expiration runs periodically in the background: Redis samples keys that have TTLs, deletes the ones that are already expired, and repeats this work within a CPU-time budget. This means expired keys are usually removed quickly, but deletion is not a continuous full scan of the keyspace.
Ticket Registry Locking
This ticket registry implementation automatically supports distributed locking. The schemas and structures that track locking operations should be automatically created by CAS using Spring Integration Redis support.