Ticket Registry Replication Encryption

The following ticket registries are able to support secure ticket replication by encrypting and signing tickets:

Default Behavior

Encryption by default is turned off when you use the above ticket registries. It requires explicit configuration before it can be used.


Each ticket registry configuration supports a cipher component that needs to be configured by the deployer. The settings, algorithms and secret keys used for the cipher may be controlled via CAS settings. Refer to the settings allotted for each registry to learn more about ticket encryption.

Additionally, Ignite may be configured to use TLS for replication transport.