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.
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.cache=false
Allow the ticket registry to cache ticket items for period of time and auto-evict and clean up, removing the need to running a ticket registry cleaner in the background.
|
cas.ticket.registry.in-memory.concurrency=20
The estimated number of concurrently updating threads. The implementation performs internal sizing to try to accommodate this many threads.
|
cas.ticket.registry.in-memory.initial-capacity=1000
The initial capacity of the underlying memory store. The implementation performs internal sizing to accommodate this many elements.
|
cas.ticket.registry.in-memory.load-factor=1
The load factor threshold, used to control resizing. Resizing may be performed when the average number of elements per bin exceeds this threshold.
|
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.
|
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.
|
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.
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.
![:information_source: :information_source:](https://github.githubassets.com/images/icons/emoji/unicode/2139.png)
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, specially 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.
Eviction Policy
This ticket registry relies on a background job that is automatically scheduled to clean up after the registry and remove expired tickets. The cleaner will periodically examine the state of the registry to identify expired tickets, remove them from the registry and then execute relevant logout operations.
In the event that the ticket registry is configured to use a caching engine, CAS configures the cache store automatically such that each ticket put into the cache is given the ability to automatically expire based on the expiration policies defined for each ticket. The cache is constantly on its own monitoring for eviction events and once an item is deemed expired and evicted, CAS will take over to run logout operations. This means that running the default registry in this mode does not require CAS to schedule and maintain a background job to look after ticket state given the cache cleans up after itself.
Clustering
This registry does not by default preserve ticket state across restarts and is not a suitable solution
for clustered CAS environments that are deployed in active/active mode. Tickets are managed and stored
in the runtime memory that is bound to the CAS server node, which means a ticket object created and managed
by CAS server A
cannot be found and accepted when a request for the same ticket is received by CAS server B
.
The registry does however provide extension points for broadcasting the results of ticket operations. A Pub/Sub type of setup can tap into such extension points to allow the registry to operate in clustered environments, and to share ticket state across all CAS server nodes keeping them all in sync. Some ticket registries such as the AMQP Ticket Registry are able to do so.