WORKERS AHEAD!

You are viewing the development documentation for the Apereo CAS server. The functionality presented here is not officially released yet. This is a work in progress and will be continually updated as development moves forward. You are most encouraged to test the changes presented.

Configure Service Replication

In the event that CAS service definitions are not managed globally via a centralized store, definitions need to be kept in sync throughout all CAS nodes in a cluster when more than one node is deployed. When the management strategy of such definitions is to store them on disk local to each node (such as JSON or YAML) files, the following mechanisms may be used to copy files from one host to another.

Native

A background task can be scheduled with the likes of rsync to copy files from from host to another. The job needs to of course run periodically to ensure configuration is kept in sync. This is the simplest option as CAS is completely ignorant of extra process in the background.

On Linux machines, rsync may be installed as:

# yum install rsync (On Red Hat based systems)
# apt-get install rsync (On Debian based systems)

As an example, this command will sync a directory /etc/cas/services from a local machine to a remote server:

rsync -avz /etc/cas/services root@192.168.0.101:/etc/cas/services

The exact opposite of the above command may be carried as such:

rsync -avzh root@192.168.0.100:/etc/cas/services /etc/cas/services

To execute the transfer operation over ssh, use the ssh --progress flags.
To test the command execution in mock mode, use the --dry-run flag.

Configuration

The following settings control the common and cor behavior of service registry replication:

The following settings and properties are available from the CAS configuration catalog:

_{The configuration settings listed below are tagged as Required in the CAS configuration metadata. This flag indicates that the presence of the setting may be needed to activate or affect the behavior of the CAS feature and generally should be reviewed, possibly owned and adjusted. If the setting is assigned a default value, you do not need to strictly put the setting in your copy of the configuration, but should review it nonetheless to make sure it matches your deployment expectations.}

_{The configuration settings listed below are tagged as Optional in the CAS configuration metadata. This
flag indicates that the presence of the setting
is not immediately necessary in the end-user CAS configuration, because a default value is assigned or
the activation of the feature is not conditionally controlled by the setting value. In other words, you should only include this field in your
configuration if you need to modify the default value or if you need to turn on the feature controlled by the setting.}

cas.service-registry.stream.core.enabled=true

Whether service registry events should be streamed and published across a CAS cluster. One typical workflow is to enable the publisher on one master node and have others consume definitions and changes from the upstream master node in order to avoid overrides and timing issues as changes may step over each other if the service registry schedule is not timed correctly.

org.apereo.cas.configuration.model.support.services.stream.StreamingServicesCoreProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

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.

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.core.enabled=true

This is the most common form of property configuration that is recognized by CAS, regardless of the actual property source, which might in fact be managed separately outside the CAS environment, by another system or cloud framework.

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      core: 
        enabled: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.core.enabled="true" -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. Note the placement of the system property which must be specified before the CAS web application is launched.

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_CORE_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.core.enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.core.replication-mode=PASSIVE

Indicates the replication mod. Available values are as follows:

ACTIVE: In this replication mode, all CAS nodes will try to sync copies of service definition files individually on each node.
PASSIVE: In this replication mode, one CAS service is designated to be the master that contains all service definition files locally, and will stream changes to other CAS passive nodes. Passive CAS nodes only access the replication cache to retrieve services, and will not individually keep copies of the service definition files on disk.

org.apereo.cas.configuration.model.support.services.stream.StreamingServicesCoreProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.core.replication-mode=PASSIVE

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      core: 
        replication-mode: "PASSIVE"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.core.replication-mode="PASSIVE" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_CORE_REPLICATION_MODE="PASSIVE"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.core.replication-mode="PASSIVE"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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

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.

Replication strategies may be configured using one the methods listed below.

Hazelcast

If you’d rather not resort to outside tooling and processes or if the native options for your deployment are not that attractive, you can take advantage of CAS’ own tooling that provides a distributed cache via Hazelcast to broadcast service definition files across the cluster and add/remove/update each node as needed. As service definitions are loaded by CAS, events are broadcasted to all CAS nodes in the cluster to pick up the changes and keep definitions in sync.

Support is enabled by including the following dependency in the overlay:

<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-service-registry-stream-hazelcast</artifactId>
    <version>${cas.version}</version>
</dependency>

implementation "org.apereo.cas:cas-server-support-service-registry-stream-hazelcast:${project.'cas.version'}"

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

dependencies {
    implementation "org.apereo.cas:cas-server-support-service-registry-stream-hazelcast"
}

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

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

The following settings and properties are available from the CAS configuration catalog:

cas.service-registry.stream.hazelcast.config.cluster.core.instance-name=

The instance name.

This setting supports the Spring Expression Language.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.instance-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              instance-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.instance-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_INSTANCE_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.instance-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.members=

Sets the well known members. If members is empty, calling this method will have the same effect as calling clear(). A member can be a comma separated string, e..g 10.11.12.1,10.11.12.2 which indicates multiple members are going to be added. The list of members must include ALL CAS server node, including the current node that owns this configuration.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.members=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              members: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.members="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_MEMBERS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.members="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.port=5701

You can specify the ports which Hazelcast will use to communicate between cluster members. The name of the parameter for this is port and its default value is 5701. By default, Hazelcast will try 100 ports to bind. Meaning that, if you set the value of port as 5701, as members are joining to the cluster, Hazelcast tries to find ports between 5701 and 5801.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.port=5701

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              port: "5701"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.port="5701" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_PORT="5701"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.port="5701"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.access-key=

AWS access key.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.access-key=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                access-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.access-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_ACCESS_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.access-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.secret-key=

AWS secret key.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.secret-key=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                secret-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.secret-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_SECRET_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.secret-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-id=

The Azure Active Directory Service Principal client ID.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAzureDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-id=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              azure: 
                client-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AZURE_CLIENT_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-secret=

The Azure Active Directory Service Principal client secret.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAzureDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-secret=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              azure: 
                client-secret: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-secret="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AZURE_CLIENT_SECRET="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-secret="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.cluster-id=

The name of the tag on the hazelcast vm resources. With every Hazelcast Virtual Machine you deploy in your resource group, you need to ensure that each VM is tagged with the value of cluster-id defined in your Hazelcast configuration. The only requirement is that every VM can access each other either by private or public IP address.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAzureDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.cluster-id=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              azure: 
                cluster-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.azure.cluster-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AZURE_CLUSTER_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.cluster-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.group-name=

The Azure resource group name of the cluster. You can find this in the Azure portal or CLI.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAzureDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.group-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              azure: 
                group-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.azure.group-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AZURE_GROUP_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.group-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.subscription-id=

The Azure subscription ID.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAzureDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.subscription-id=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              azure: 
                subscription-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.azure.subscription-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AZURE_SUBSCRIPTION_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.subscription-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.tenant-id=

The Azure Active Directory tenant ID.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAzureDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.tenant-id=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              azure: 
                tenant-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.azure.tenant-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AZURE_TENANT_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.tenant-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential=

Cloud Provider credential, can be thought of as a password for cloud services.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                credential: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_CREDENTIAL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.identity=

Cloud Provider identity, can be thought of as a user name for cloud services.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.identity=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                identity: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.identity="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_IDENTITY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.identity="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.provider=

String value that is used to identify ComputeService provider. For example, "google-compute-engine" is used for Google Cloud services. See here for more info.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.provider=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                provider: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.provider="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_PROVIDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.provider="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.group=

Name of this Hazelcast cluster. You can have multiple distinct clusters to use the same ZooKeeper installation

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastZooKeeperDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.group=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              zookeeper: 
                group: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.group="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_ZOOKEEPER_GROUP="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.group="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.path=/discovery/hazelcast

Path in zookeeper to be used for auto-discovery of members where members are tracked.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastZooKeeperDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.path=/discovery/hazelcast

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              zookeeper: 
                path: "/discovery/hazelcast"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.path="/discovery/hazelcast" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_ZOOKEEPER_PATH="/discovery/hazelcast"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.path="/discovery/hazelcast"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.url=

Zookeeper url address typically in the format of ip-address:port.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastZooKeeperDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.url=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              zookeeper: 
                url: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.url="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_ZOOKEEPER_URL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.url="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

# The instance name.
# cas.service-registry.stream.hazelcast.config.cluster.core.instance-name=

# Sets the well known members.
# cas.service-registry.stream.hazelcast.config.cluster.network.members=

# You can specify the ports which Hazelcast will use to communicate between cluster members.
# cas.service-registry.stream.hazelcast.config.cluster.network.port=5701

# AWS access key.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.access-key=

# AWS secret key.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.secret-key=

# The Azure Active Directory Service Principal client ID.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-id=

# The Azure Active Directory Service Principal client secret.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.client-secret=

# The name of the tag on the hazelcast vm resources.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.cluster-id=

# The Azure resource group name of the cluster.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.group-name=

# The Azure subscription ID.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.subscription-id=

# The Azure Active Directory tenant ID.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.azure.tenant-id=

# Cloud Provider credential, can be thought of as a password for cloud services.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential=

# Cloud Provider identity, can be thought of as a user name for cloud services.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.identity=

# String value that is used to identify ComputeService provider.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.provider=

# Name of this Hazelcast cluster.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.group=

# Path in zookeeper to be used for auto-discovery of members where members are tracked.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.path=/discovery/hazelcast

# Zookeeper url address typically in the format of {@code ip-address:port}.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.zookeeper.url=

cas.service-registry.stream.hazelcast.config.cluster.core.async-backup-count=0

Hazelcast supports both synchronous and asynchronous backups. By default, backup operations are synchronous. In this case, backup operations block operations until backups are successfully copied to backup members (or deleted from backup members in case of remove) and acknowledgements are received. Therefore, backups are updated before a put operation is completed, provided that the cluster is stable. Asynchronous backups, on the other hand, do not block operations. They are fire and forget and do not require acknowledgements; the backup operations are performed at some point in time.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.async-backup-count=0

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              async-backup-count: "0"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.async-backup-count="0" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_ASYNC_BACKUP_COUNT="0"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.async-backup-count="0"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.async-fillup=true

Used when replication is turned on with #isReplicated().

If a new member joins the cluster, there are two ways you can handle the initial provisioning that is executed to replicate all existing values to the new member. Each involves how you configure the async fill up.

First, you can configure async fill up to true, which does not block reads while the fill up operation is underway. That way, you have immediate access on the new member, but it will take time until all the values are eventually accessible. Not yet replicated values are returned as non-existing (null).
Second, you can configure for a synchronous initial fill up (by configuring the async fill up to false), which blocks every read or write access to the map until the fill up operation is finished. Use this with caution since it might block your application from operating.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.async-fillup=true

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              async-fillup: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.async-fillup="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_ASYNC_FILLUP="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.async-fillup="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.backup-count=1

To provide data safety, Hazelcast allows you to specify the number of backup copies you want to have. That way, data on a cluster member will be copied onto other member(s). To create synchronous backups, select the number of backup copies. When this count is 1, a map entry will have its backup on one other member in the cluster. If you set it to 2, then a map entry will have its backup on two other members. You can set it to 0 if you do not want your entries to be backed up, e.g., if performance is more important than backing up. The maximum value for the backup count is 6. Sync backup operations have a blocking cost which may lead to latency issues.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.backup-count=1

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              backup-count: "1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.backup-count="1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_BACKUP_COUNT="1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.backup-count="1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.cp-member-count=0

CP Subsystem is a component of a Hazelcast cluster that builds a strongly consistent layer for a set of distributed data structures. Its data structures are CP with respect to the CAP principle, i.e., they always maintain linearizability and prefer consistency over availability during network partitions. Besides network partitions, CP Subsystem withstands server and client failures. All members of a Hazelcast cluster do not necessarily take part in CP Subsystem. The number of Hazelcast members that take part in CP Subsystem is specified here. CP Subsystem must have at least 3 CP members.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.cp-member-count=0

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              cp-member-count: "0"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.cp-member-count="0" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_CP_MEMBER_COUNT="0"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.cp-member-count="0"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.eviction-policy=LRU

Hazelcast supports policy-based eviction for distributed maps. Currently supported policies are LRU (Least Recently Used) and LFU (Least Frequently Used) and NONE. See this for more info.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.eviction-policy=LRU

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              eviction-policy: "LRU"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.eviction-policy="LRU" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_EVICTION_POLICY="LRU"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.eviction-policy="LRU"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.logging-type=slf4j

Hazelcast has a flexible logging configuration and doesn't depend on any logging framework except JDK logging. It has in-built adaptors for a number of logging frameworks and also supports custom loggers by providing logging interfaces. To use built-in adaptors you should set this setting to one of predefined types below.

jdk: JDK logging
log4j: Log4j
slf4j: Slf4j
none: Disable logging

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.logging-type=slf4j

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              logging-type: "slf4j"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.logging-type="slf4j" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_LOGGING_TYPE="slf4j"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.logging-type="slf4j"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.map-merge-policy=PUT_IF_ABSENT

Define how data items in Hazelcast maps are merged together from source to destination. By default, merges map entries from source to destination if they don't exist in the destination map. Accepted values are:

PUT_IF_ABSENT: Merges data structure entries from source to destination if they don't exist in the destination data structure.
HIGHER_HITS: * Merges data structure entries from source to destination data structure if the source entry has more hits than the destination one.
DISCARD: Merges only entries from the destination data structure and discards all entries from the source data structure.
PASS_THROUGH: Merges data structure entries from source to destination directly unless the merging entry is null
EXPIRATION_TIME: Merges data structure entries from source to destination data structure if the source entry will expire later than the destination entry. This policy can only be used if the clocks of the nodes are in sync.
LATEST_UPDATE: Merges data structure entries from source to destination data structure if the source entry was updated more frequently than the destination entry. This policy can only be used if the clocks of the nodes are in sync.
LATEST_ACCESS: Merges data structure entries from source to destination data structure if the source entry has been accessed more recently than the destination entry. This policy can only be used if the clocks of the nodes are in sync.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.map-merge-policy=PUT_IF_ABSENT

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              map-merge-policy: "PUT_IF_ABSENT"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.map-merge-policy="PUT_IF_ABSENT" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_MAP_MERGE_POLICY="PUT_IF_ABSENT"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.map-merge-policy="PUT_IF_ABSENT"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.max-no-heartbeat-seconds=300

Max timeout of heartbeat in seconds for a node to assume it is dead.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.max-no-heartbeat-seconds=300

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              max-no-heartbeat-seconds: "300"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.max-no-heartbeat-seconds="300" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_MAX_NO_HEARTBEAT_SECONDS="300"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.max-no-heartbeat-seconds="300"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.max-size=85

Sets the maximum size of the map.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.max-size=85

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              max-size: "85"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.max-size="85" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_MAX_SIZE="85"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.max-size="85"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.max-size-policy=USED_HEAP_PERCENTAGE

FREE_HEAP_PERCENTAGE: Policy based on minimum free JVM heap memory percentage per JVM.
FREE_HEAP_SIZE: Policy based on minimum free JVM heap memory in megabytes per JVM.
FREE_NATIVE_MEMORY_PERCENTAGE: Policy based on minimum free native memory percentage per Hazelcast instance.
FREE_NATIVE_MEMORY_SIZE: Policy based on minimum free native memory in megabytes per Hazelcast instance.
PER_NODE: Policy based on maximum number of entries stored per data structure (map, cache etc) on each Hazelcast instance.
PER_PARTITION: Policy based on maximum number of entries stored per data structure (map, cache etc) on each partition.
USED_HEAP_PERCENTAGE: Policy based on maximum used JVM heap memory percentage per data structure (map, cache etc) on each Hazelcast instance .
USED_HEAP_SIZE: Policy based on maximum used JVM heap memory in megabytes per data structure (map, cache etc) on each Hazelcast instance.
USED_NATIVE_MEMORY_PERCENTAGE: Policy based on maximum used native memory percentage per data structure (map, cache etc) on each Hazelcast instance.
USED_NATIVE_MEMORY_SIZE: Policy based on maximum used native memory in megabytes per data structure (map, cache etc) on each Hazelcast instance .

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.max-size-policy=USED_HEAP_PERCENTAGE

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              max-size-policy: "USED_HEAP_PERCENTAGE"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.max-size-policy="USED_HEAP_PERCENTAGE" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_MAX_SIZE_POLICY="USED_HEAP_PERCENTAGE"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.max-size-policy="USED_HEAP_PERCENTAGE"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.partition-member-group-type=

With PartitionGroupConfig, you can control how primary and backup partitions are mapped to physical Members. Hazelcast will always place partitions on different partition groups so as to provide redundancy. Accepted value are: PER_MEMBER, HOST_AWARE, CUSTOM, ZONE_AWARE, SPI. In all cases a partition will never be created on the same group. If there are more partitions defined than there are partition groups, then only those partitions, up to the number of partition groups, will be created. For example, if you define 2 backups, then with the primary, that makes 3. If you have only two partition groups only two will be created.

{}PER_MEMBER Partition Groups}: This is the default partition scheme and is used if no other scheme is defined. Each Member is in a group of its own.</li>
{}HOST_AWARE Partition Groups}: In this scheme, a group corresponds to a host, based on its IP address. Partitions will not be written to any other members on the same host. This scheme provides good redundancy when multiple instances are being run on the same host.</li>
{}CUSTOM Partition Groups}: In this scheme, IP addresses, or IP address ranges, are allocated to groups. Partitions are not written to the same group. This is very useful for ensuring partitions are written to different racks or even availability zones.</li>
{}ZONE_AWARE Partition Groups}: In this scheme, groups are allocated according to the metadata provided by Discovery SPI Partitions are not written to the same group. This is very useful for ensuring partitions are written to availability zones or different racks without providing the IP addresses to the config ahead.</li>
{}SPI Partition Groups}: In this scheme, groups are allocated according to the implementation provided by Discovery SPI.</li> </ul> </p> org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties. _{How can I configure this property?} CAS Property: cas.service-registry.stream.hazelcast.config.cluster.core.partition-member-group-type Configuration properties can be included and activated using the following strategies. :information_source: 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. Java Property YAML Property System Property Environment Variable Command-line Argument CAS properties can be specified using the Java configuration property syntax in any and all .properties files: 1 cas.service-registry.stream.hazelcast.config.cluster.core.partition-member-group-type=... This is the most common form of property configuration that is recognized by CAS, regardless of the actual property source, which might in fact be managed separately outside the CAS environment, by another system or cloud framework. CAS properties can be specified using the YAML syntax: 1 cas: service-registry: stream: hazelcast: config: cluster: core: partition-member-group-type: "..." Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice. CAS properties can be passed to the CAS web application as system properties, when the application is launched: 1 java -Dcas.service-registry.stream.hazelcast.config.cluster.core.partition-member-group-type="..." -jar build/libs/cas.war The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. Note the placement of the system property which must be specified before the CAS web application is launched. CAS properties can specified as system environment variables before the CAS web application is launched: 1 2 3 export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_PARTITION_MEMBER_GROUP_TYPE="..." java -jar build/libs/cas.war The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched: 1 java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.partition-member-group-type="..." The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. </div></td> </tr>

cas.service-registry.stream.hazelcast.config.cluster.core.replicated=false

A Replicated Map is a distributed key-value data structure where the data is replicated to all members in the cluster. It provides full replication of entries to all members for high speed access. A Replicated Map does not partition data (it does not spread data to different cluster members); instead, it replicates the data to all members. Replication leads to higher memory consumption. However, a Replicated Map has faster read and write access since the data is available on all members. Writes could take place on local/remote members in order to provide write-order, eventually being replicated to all other members.

If you have a large cluster or very high occurrences of updates, the Replicated Map may not scale linearly as expected since it has to replicate update operations to all members in the cluster. Since the replication of updates is performed in an asynchronous manner, Hazelcast recommends you enable back pressure in case your system has high occurrences of updates.

Note that Replicated Map does not guarantee eventual consistency because there are some edge cases that fail to provide consistency.

Replicated Map uses the internal partition system of Hazelcast in order to serialize updates happening on the same key at the same time. This happens by sending updates of the same key to the same Hazelcast member in the cluster.

Due to the asynchronous nature of replication, a Hazelcast member could die before successfully replicating a "write" operation to other members after sending the "write completed" response to its caller during the write process. In this scenario, Hazelcast’s internal partition system promotes one of the replicas of the partition as the primary one. The new primary partition does not have the latest "write" since the dead member could not successfully replicate the update.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.replicated=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              replicated: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.replicated="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_REPLICATED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.replicated="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.core.timeout=5

Connection timeout in seconds for the TCP/IP config and members joining the cluster.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.core.timeout=5

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            core: 
              timeout: "5"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.core.timeout="5" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_CORE_TIMEOUT="5"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.core.timeout="5"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.enabled=false

Whether discovery should be enabled via the configured strategies below.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.enabled=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.enabled=false

Enables a multicast configuration using a group address and port. Contains the configuration for the multicast discovery mechanism. With the multicast discovery mechanism Hazelcast allows Hazelcast members to find each other using multicast. So Hazelcast members do not need to know concrete addresses of members, they just multicast to everyone listening. It depends on your environment if multicast is possible or allowed; otherwise you need to have a look at the tcp/ip cluster

org.apereo.cas.configuration.model.support.hazelcast.HazelcastClusterMulticastProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.enabled=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              multicast: 
                enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_MULTICAST_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.group=

The multicast group address used for discovery. With the multicast auto-discovery mechanism, Hazelcast allows cluster members to find each other using multicast communication. The cluster members do not need to know the concrete addresses of the other members, as they just multicast to all the other members for listening. Whether multicast is possible or allowed depends on your environment.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastClusterMulticastProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.group=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              multicast: 
                group: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.group="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_MULTICAST_GROUP="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.group="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.port=0

The multicast port used for discovery.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastClusterMulticastProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.port=0

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              multicast: 
                port: "0"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.port="0" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_MULTICAST_PORT="0"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.port="0"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.time-to-live=32

Gets the time to live for the multicast package in seconds. This is the default time-to-live for multicast packets sent out on the socket

org.apereo.cas.configuration.model.support.hazelcast.HazelcastClusterMulticastProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.time-to-live=32

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              multicast: 
                time-to-live: "32"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.time-to-live="32" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_MULTICAST_TIME_TO_LIVE="32"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.time-to-live="32"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.timeout=2

specifies the time in seconds that a member should wait for a valid multicast response from another member running in the network before declaring itself the leader member (the first member joined to the cluster) and creating its own cluster. This only applies to the startup of members where no leader has been assigned yet. If you specify a high value, such as 60 seconds, it means that until a leader is selected, each member will wait 60 seconds before moving on. Be careful when providing a high value. Also, be careful not to set the value too low, or the members might give up too early and create their own cluster.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastClusterMulticastProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.timeout=2

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              multicast: 
                timeout: "2"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.timeout="2" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_MULTICAST_TIMEOUT="2"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.timeout="2"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.trusted-interfaces=

Multicast trusted interfaces for discovery. With the multicast auto-discovery mechanism, Hazelcast allows cluster members to find each other using multicast communication. The cluster members do not need to know the concrete addresses of the other members, as they just multicast to all the other members for listening. Whether multicast is possible or allowed depends on your environment.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastClusterMulticastProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.trusted-interfaces=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              multicast: 
                trusted-interfaces: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.trusted-interfaces="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_MULTICAST_TRUSTED_INTERFACES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.trusted-interfaces="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ipv4-enabled=true

IPv6 support has been switched off by default, since some platforms have issues in use of IPv6 stack. And some other platforms such as Amazon AWS have no support at all. To enable IPv6 support set this setting to false.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ipv4-enabled=true

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ipv4-enabled: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ipv4-enabled="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_IPV4_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ipv4-enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.local-address=

If this property is set, then this is the address where the server socket is bound to.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.local-address=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              local-address: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.local-address="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_LOCAL_ADDRESS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.local-address="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.network-interfaces=

You can specify which network interfaces that Hazelcast should use. Servers mostly have more than one network interface, so you may want to list the valid IPs. Range characters ('*' and '-') can be used for simplicity. For instance, 10.3.10.* refers to IPs between 10.3.10.0 and 10.3.10.255. Interface 10.3.10.4-18 refers to IPs between 10.3.10.4 and 10.3.10.18 (4 and 18 included). If network interface configuration is enabled (it is disabled by default) and if Hazelcast cannot find an matching interface, then it will print a message on the console and will not start on that node.

Interfaces can be separated by a comma.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.network-interfaces=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              network-interfaces: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.network-interfaces="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_NETWORK_INTERFACES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.network-interfaces="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.outbound-ports=

The outbound ports for the Hazelcast configuration.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.outbound-ports=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              outbound-ports: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.outbound-ports="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_OUTBOUND_PORTS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.outbound-ports="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.port-auto-increment=true

You may also want to choose to use only one port. In that case, you can disable the auto-increment feature of port.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.port-auto-increment=true

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              port-auto-increment: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.port-auto-increment="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_PORT_AUTO_INCREMENT="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.port-auto-increment="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.public-address=

The default public address to be advertised to other cluster members and clients.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.public-address=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              public-address: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.public-address="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_PUBLIC_ADDRESS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.public-address="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.cipher-suites=

Comma-separated list of cipher suite names allowed to be used. Its default value are all supported suites in your Java runtime.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.cipher-suites=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                cipher-suites: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.cipher-suites="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_CIPHER_SUITES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.cipher-suites="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-manager-algorithm=

Name of the algorithm based on which the authentication keys are provided.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-manager-algorithm=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                key-manager-algorithm: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-manager-algorithm="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_KEY_MANAGER_ALGORITHM="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-manager-algorithm="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-store-type=JKS

Type of the keystore. Its default value is JKS. Another commonly used type is the PKCS12. Available keystore/truststore types depend on your Operating system and the Java runtime. Only needed when the mutual authentication is used.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-store-type=JKS

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                key-store-type: "JKS"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-store-type="JKS" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_KEY_STORE_TYPE="JKS"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-store-type="JKS"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore=

Path of your keystore file. Only needed when the mutual authentication is used.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                keystore: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_KEYSTORE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore-password=

Password to access the key from your keystore file. Only needed when the mutual authentication is used.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore-password=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                keystore-password: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore-password="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_KEYSTORE_PASSWORD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore-password="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.mutual-authentication=

Mutual authentication configuration. It’s empty by default which means the client side of connection is not authenticated. Available values are:

REQUIRED - server forces usage of a trusted client certificate
OPTIONAL - server asks for a client certificate, but it doesn't require it

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.mutual-authentication=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                mutual-authentication: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.mutual-authentication="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_MUTUAL_AUTHENTICATION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.mutual-authentication="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.protocol=TLS

Name of the algorithm which is used in your TLS/SSL. For the protocol property, we recommend you to provide TLS with its version information, e.g., TLSv1.2. Note that if you write only TLS, your application chooses the TLS version according to your Java version.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.protocol=TLS

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                protocol: "TLS"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.protocol="TLS" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_PROTOCOL="TLS"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.protocol="TLS"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-manager-algorithm=

Name of the algorithm based on which the trust managers are provided.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-manager-algorithm=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                trust-manager-algorithm: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-manager-algorithm="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_TRUST_MANAGER_ALGORITHM="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-manager-algorithm="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store=

Path of your truststore file. The file truststore is a keystore file that contains a collection of certificates trusted by your application.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                trust-store: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_TRUST_STORE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-password=

Password to unlock the truststore file.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-password=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                trust-store-password: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-password="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_TRUST_STORE_PASSWORD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-password="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-type=JKS

Type of the truststore. Its default value is JKS. Another commonly used type is the PKCS12. Available keystore/truststore types depend on your Operating system and the Java runtime.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-type=JKS

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                trust-store-type: "JKS"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-type="JKS" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_TRUST_STORE_TYPE="JKS"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-type="JKS"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.validate-identity=false

Flag which allows enabling endpoint identity validation. It means, during the TLS handshake client verifies if the server’s hostname (or IP address) matches the information in X.509 certificate (Subject Alternative Name extension).

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkSslProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.ssl.validate-identity=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              ssl: 
                validate-identity: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.ssl.validate-identity="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_SSL_VALIDATE_IDENTITY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.ssl.validate-identity="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.network.tcpip-enabled=true

Enable TCP/IP config. Contains the configuration for the Tcp/Ip join mechanism. The Tcp/Ip join mechanism relies on one or more well known members. So when a new member wants to join a cluster, it will try to connect to one of the well known members. If it is able to connect, it will now about all members in the cluster and doesn't rely on these well known members anymore.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastNetworkClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.network.tcpip-enabled=true

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            network: 
              tcpip-enabled: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.network.tcpip-enabled="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_NETWORK_TCPIP_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.network.tcpip-enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.enabled=false

Whether WAN should be enabled.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.enabled=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.replication-name=apereo-cas

Name of this replication group.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.replication-name=apereo-cas

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              replication-name: "apereo-cas"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.replication-name="apereo-cas" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_REPLICATION_NAME="apereo-cas"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.replication-name="apereo-cas"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets=

List of target clusters to be used for synchronization and replication.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].acknowledge-type=ACK_ON_OPERATION_COMPLETE

Accepted values are:

ACK_ON_RECEIPT: ACK after WAN operation is received by the target cluster (without waiting the result of actual operation invocation).
ACK_ON_OPERATION_COMPLETE: Wait till the operation is complete on target cluster.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].acknowledge-type=ACK_ON_OPERATION_COMPLETE

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                acknowledge-type: "ACK_ON_OPERATION_COMPLETE"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].acknowledge-type="ACK_ON_OPERATION_COMPLETE" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_ACKNOWLEDGE_TYPE="ACK_ON_OPERATION_COMPLETE"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].acknowledge-type="ACK_ON_OPERATION_COMPLETE"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-maximum-delay-milliseconds=1000

Maximum amount of time, in milliseconds, to be waited before sending a batch of events in case batch.size is not reached.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-maximum-delay-milliseconds=1000

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                batch-maximum-delay-milliseconds: "1000"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-maximum-delay-milliseconds="1000" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_BATCH_MAXIMUM_DELAY_MILLISECONDS="1000"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-maximum-delay-milliseconds="1000"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-size=500

Maximum size of events that are sent to the target cluster in a single batch.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-size=500

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                batch-size: "500"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-size="500" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_BATCH_SIZE="500"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-size="500"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].cluster-name=

Sets the cluster name used as an endpoint group password for authentication on the target endpoint. If there is no separate publisher ID property defined, this cluster name will also be used as a WAN publisher ID. This ID is then used for identifying the publisher.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].cluster-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                cluster-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].cluster-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_CLUSTER_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].cluster-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].consistency-check-strategy=NONE

Strategy for checking the consistency of data between replicas.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].consistency-check-strategy=NONE

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                consistency-check-strategy: "NONE"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].consistency-check-strategy="NONE" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_CONSISTENCY_CHECK_STRATEGY="NONE"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].consistency-check-strategy="NONE"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].endpoints=

Comma separated list of endpoints in this replication group. IP addresses and ports of the cluster members for which the WAN replication is implemented. These endpoints are not necessarily the entire target cluster and WAN does not perform the discovery of other members in the target cluster. It only expects that these IP addresses (or at least some of them) are available.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].endpoints=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                endpoints: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].endpoints="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_ENDPOINTS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].endpoints="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].executor-thread-count=2

The number of threads that the replication executor will have. The executor is used to send WAN events to the endpoints and ideally you want to have one thread per endpoint. If this property is omitted and you have specified the endpoints property, this will be the case. If necessary you can manually define the number of threads that the executor will use. Once the executor has been initialized there is thread affinity between the discovered endpoints and the executor threads - all events for a single endpoint will go through a single executor thread, preserving event order. It is important to determine which number of executor threads is a good value. Failure to do so can lead to performance issues - either contention on a too small number of threads or wasted threads that will not be performing any work.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].executor-thread-count=2

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                executor-thread-count: "2"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].executor-thread-count="2" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_EXECUTOR_THREAD_COUNT="2"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].executor-thread-count="2"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].properties=

The WAN publisher properties.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].properties=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                properties: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].properties="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_PROPERTIES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].properties="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-class-name=com.hazelcast.enterprise.wan.replication.WanBatchReplication

Publisher class name for WAN replication.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-class-name=com.hazelcast.enterprise.wan.replication.WanBatchReplication

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                publisher-class-name: "com.hazelcast.enterprise.wan.replication.WanBatchReplication"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-class-name="com.hazelcast.enterprise.wan.replication.WanBatchReplication" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_PUBLISHER_CLASS_NAME="com.hazelcast.enterprise.wan.replication.WanBatchReplication"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-class-name="com.hazelcast.enterprise.wan.replication.WanBatchReplication"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-id=

Returns the publisher ID used for identifying the publisher.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-id=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                publisher-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_PUBLISHER_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-capacity=10000

For huge clusters or high data mutation rates, you might need to increase the replication queue size. The default queue size for replication queues is 10,000. This means, if you have heavy put/update/remove rates, you might exceed the queue size so that the oldest, not yet replicated, updates might get lost.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-capacity=10000

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                queue-capacity: "10000"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-capacity="10000" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_QUEUE_CAPACITY="10000"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-capacity="10000"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-full-behavior=THROW_EXCEPTION

Accepted values are:

THROW_EXCEPTION: Instruct WAN replication implementation to throw an exception and doesn't allow further processing.
DISCARD_AFTER_MUTATION: Instruct WAN replication implementation to drop new events when WAN event queues are full.
THROW_EXCEPTION_ONLY_IF_REPLICATION_ACTIVE: Similar to THROW_EXCEPTION but only throws exception when WAN replication is active. * Discards the new events if WAN replication is stopped.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-full-behavior=THROW_EXCEPTION

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                queue-full-behavior: "THROW_EXCEPTION"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-full-behavior="THROW_EXCEPTION" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_QUEUE_FULL_BEHAVIOR="THROW_EXCEPTION"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-full-behavior="THROW_EXCEPTION"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].response-timeout-milliseconds=60000

Time, in milliseconds, to be waited for the acknowledgment of a sent WAN event to target cluster.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].response-timeout-milliseconds=60000

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                response-timeout-milliseconds: "60000"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].response-timeout-milliseconds="60000" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_RESPONSE_TIMEOUT_MILLISECONDS="60000"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].response-timeout-milliseconds="60000"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].snapshot-enabled=

When set to true, only the latest events (based on key) are selected and sent in a batch.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastWANReplicationTargetClusterProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].snapshot-enabled=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            wan-replication: 
              targets[0]: 
                snapshot-enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].snapshot-enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_WAN_REPLICATION_TARGETS[0]_SNAPSHOT_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].snapshot-enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.core.enable-compression=false

Enables compression when default java serialization is used.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.core.enable-compression=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          core: 
            enable-compression: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.core.enable-compression="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CORE_ENABLE_COMPRESSION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.core.enable-compression="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.core.enable-jet=true

Enable Jet configuration/service on the hazelcast instance. Hazelcast Jet is a distributed batch and stream processing system that can do stateful computations over massive amounts of data with consistent low latency. Jet service is required when executing SQL queries with the SQL service.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.core.enable-jet=true

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          core: 
            enable-jet: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.core.enable-jet="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CORE_ENABLE_JET="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.core.enable-jet="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.core.enable-management-center-scripting=true

Enables scripting from Management Center.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.core.enable-management-center-scripting=true

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          core: 
            enable-management-center-scripting: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.core.enable-management-center-scripting="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CORE_ENABLE_MANAGEMENT_CENTER_SCRIPTING="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.core.enable-management-center-scripting="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.core.license-key=

Hazelcast enterprise license key.

org.apereo.cas.configuration.model.support.hazelcast.HazelcastCoreProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.core.license-key=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          core: 
            license-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.core.license-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CORE_LICENSE_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.core.license-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.cluster=

ECS cluster short name or ARN; default is the current cluster.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.cluster=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                cluster: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.cluster="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_CLUSTER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.cluster="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.connection-timeout-seconds=5

The maximum amount of time Hazelcast will try to connect to a well known member before giving up. Setting this value too low could mean that a member is not able to connect to a cluster. Setting the value too high means that member startup could slow down because of longer timeouts (for example, when a well known member is not up). Increasing this value is recommended if you have many IPs listed and the members cannot properly build up the cluster. Its default value is 5.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.connection-timeout-seconds=5

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                connection-timeout-seconds: "5"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.connection-timeout-seconds="5" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_CONNECTION_TIMEOUT_SECONDS="5"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.connection-timeout-seconds="5"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.family=

Filter to look only for ECS tasks with the given family name; mutually exclusive with #getServiceName().

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.family=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                family: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.family="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_FAMILY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.family="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.host-header=

Host header. i.e. ec2.amazonaws.com. The URL that is the entry point for a web service.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.host-header=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                host-header: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.host-header="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_HOST_HEADER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.host-header="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.iam-role=

If you do not want to use access key and secret key, you can specify iam-role. Hazelcast fetches your credentials by using your IAM role. This setting only affects deployments on Amazon EC2. If you are deploying CAS in an Amazon ECS environment, the role should not be specified. The role is fetched from the task definition that is assigned to run CAS.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.iam-role=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                iam-role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.iam-role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_IAM_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.iam-role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.port=-1

Hazelcast port. Typically may be set to 5701. You can set searching for other ports rather than 5701 if you've members on different ports.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.port=-1

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                port: "-1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.port="-1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_PORT="-1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.port="-1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.region=us-east-1

AWS region. i.e. us-east-1. The region where your members are running.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.region=us-east-1

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                region: "us-east-1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.region="us-east-1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_REGION="us-east-1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.region="us-east-1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.security-group-name=

If a security group is configured, only instances within that security group are selected.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.security-group-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                security-group-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.security-group-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_SECURITY_GROUP_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.security-group-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.service-name=

Filter to look only for ECS tasks from the given service; mutually exclusive with #getFamily().

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.service-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                service-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.service-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_SERVICE_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.service-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-key=

If a tag key/value is set, only instances with that tag key/value will be selected.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-key=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                tag-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_TAG_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-value=

If a tag key/value is set, only instances with that tag key/value will be selected.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastAwsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-value=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              aws: 
                tag-value: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-value="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_AWS_TAG_VALUE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-value="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.hz-port=5701-5708

A range of ports where the plugin looks for Hazelcast members.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastGoogleCloudPlatformDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.hz-port=5701-5708

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              gcp: 
                hz-port: "5701-5708"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.hz-port="5701-5708" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_GCP_HZ_PORT="5701-5708"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.hz-port="5701-5708"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.label=

A filter to look only for instances labeled as specified; property format: key=value.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastGoogleCloudPlatformDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.label=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              gcp: 
                label: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.label="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_GCP_LABEL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.label="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.private-key-path=

A filesystem path to the private key for GCP service account in the JSON format; if not set, the access token is fetched from the GCP VM instance.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastGoogleCloudPlatformDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.private-key-path=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              gcp: 
                private-key-path: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.private-key-path="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_GCP_PRIVATE_KEY_PATH="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.private-key-path="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.projects=

A list of projects where the plugin looks for instances; if not set, the current project is used.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastGoogleCloudPlatformDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.projects=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              gcp: 
                projects: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.projects="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_GCP_PROJECTS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.projects="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.region=

A region where the plugin looks for instances; if not set, the #getZones() property is used; if it and #getZones() property not set, all zones of the current region are used.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastGoogleCloudPlatformDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.region=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              gcp: 
                region: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.region="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_GCP_REGION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.region="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.zones=

A list of zones where the plugin looks for instances; if not set, all zones of the current region are used.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastGoogleCloudPlatformDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.zones=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              gcp: 
                zones: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.zones="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_GCP_ZONES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.zones="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential-path=

Used for cloud providers which require an extra JSON or P12 key file. This denotes the path of that file. Only tested with Google Compute Engine. (Required if Google Compute Engine is used.)

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential-path=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                credential-path: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential-path="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_CREDENTIAL_PATH="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential-path="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.endpoint=

Defines the endpoint for a generic API such as OpenStack or CloudStack (optional).

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.endpoint=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                endpoint: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.endpoint="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_ENDPOINT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.endpoint="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.group=

Filters instance groups (optional). When used with AWS it maps to security group.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.group=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                group: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.group="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_GROUP="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.group="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.port=-1

Port which the hazelcast instance service uses on the cluster member. Default value is 5701. (optional)

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.port=-1

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                port: "-1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.port="-1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_PORT="-1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.port="-1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.regions=

Defines region for a cloud service (optional). Can be used with comma separated values for multiple values.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.regions=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                regions: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.regions="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_REGIONS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.regions="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.role-name=

Used for IAM role support specific to AWS (optional, but if defined, no identity or credential should be defined in the configuration).

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.role-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                role-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.role-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_ROLE_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.role-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-keys=

Filters cloud instances with tags (optional). Can be used with comma separated values for multiple values.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-keys=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                tag-keys: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-keys="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_TAG_KEYS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-keys="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-values=

Filters cloud instances with tags (optional) Can be used with comma separated values for multiple values.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-values=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                tag-values: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-values="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_TAG_VALUES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-values="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.zones=

Defines zone for a cloud service (optional). Can be used with comma separated values for multiple values.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastJCloudsDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.zones=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              jclouds: 
                zones: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.zones="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_JCLOUDS_ZONES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.zones="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-retries=3

Defines the number of retries to Kubernetes API. Defaults to: 3.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-retries=3

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                api-retries: "3"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-retries="3" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_API_RETRIES="3"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-retries="3"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-token=

Defines an oauth token for the kubernetes client to access the kubernetes REST API. Defaults to reading the token from the auto-injected file at: /var/run/secrets/kubernetes.io/serviceaccount/token.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-token=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                api-token: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-token="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_API_TOKEN="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-token="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.ca-certificate=

CA Authority certificate from Kubernetes Master. Defaults to reading the certificate from the auto-injected file at: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.ca-certificate=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                ca-certificate: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.ca-certificate="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_CA_CERTIFICATE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.ca-certificate="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.kubernetes-master=

Defines an alternative address for the kubernetes master. Defaults to: https://kubernetes.default.svc

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.kubernetes-master=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                kubernetes-master: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.kubernetes-master="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_KUBERNETES_MASTER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.kubernetes-master="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.namespace=

Defines the namespace of the application POD through the Service Discovery REST API of Kubernetes.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.namespace=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                namespace: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.namespace="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_NAMESPACE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.namespace="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-name=

Defines the pod label to lookup through the Service Discovery REST API of Kubernetes.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                pod-label-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_POD_LABEL_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-value=

Defines the pod label value to lookup through the Service Discovery REST API of Kubernetes.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-value=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                pod-label-value: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-value="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_POD_LABEL_VALUE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-value="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.resolve-not-ready-addresses=false

Defines if not ready addresses should be evaluated to be discovered on startup.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.resolve-not-ready-addresses=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                resolve-not-ready-addresses: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.resolve-not-ready-addresses="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_RESOLVE_NOT_READY_ADDRESSES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.resolve-not-ready-addresses="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns=

Defines the DNS service lookup domain. This is defined as something similar to my-svc.my-namespace.svc.cluster.local.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                service-dns: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_SERVICE_DNS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns-timeout=-1

Defines the DNS service lookup timeout in seconds. Defaults to 5 secs.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns-timeout=-1

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                service-dns-timeout: "-1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns-timeout="-1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_SERVICE_DNS_TIMEOUT="-1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns-timeout="-1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-name=

Defines the service label to lookup through the Service Discovery REST API of Kubernetes.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                service-label-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_SERVICE_LABEL_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-value=

Defines the service label value to lookup through the Service Discovery REST API of Kubernetes.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-value=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                service-label-value: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-value="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_SERVICE_LABEL_VALUE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-value="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-name=

Defines the service name of the POD to lookup through the Service Discovery REST API of Kubernetes.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                service-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_SERVICE_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-port=0

If specified with a value greater than 0, its value defines the endpoint port of the service (overriding the default).

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-port=0

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                service-port: "0"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-port="0" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_SERVICE_PORT="0"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-port="0"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.use-node-name-as-external-address=false

Defines if the node name should be used as external address, instead of looking up the external IP using the /nodes resource. Default is false.

org.apereo.cas.configuration.model.support.hazelcast.discovery.HazelcastKubernetesDiscoveryProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.use-node-name-as-external-address=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        config: 
          cluster: 
            discovery: 
              kubernetes: 
                use-node-name-as-external-address: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.use-node-name-as-external-address="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_CONFIG_CLUSTER_DISCOVERY_KUBERNETES_USE_NODE_NAME_AS_EXTERNAL_ADDRESS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.use-node-name-as-external-address="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.hazelcast.duration=PT1M

Duration that indicates how long should items be kept in the hazelcast cache. Note that generally this number needs to be short as once an item is delivered to a target, it is explicitly removed from the cache/queue. This duration needs to be adjusted if the latency between the CAS nodes in the cluster is too large. Having too short a value will cause the record to expire before it reaches other members of the cluster.

This settings supports the java.time.Duration syntax ^[?].

org.apereo.cas.configuration.model.support.services.stream.hazelcast.StreamServicesHazelcastProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.hazelcast.duration=PT1M

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      hazelcast: 
        duration: "PT1M"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.hazelcast.duration="PT1M" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_HAZELCAST_DURATION="PT1M"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.hazelcast.duration="PT1M"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

# Hazelcast supports both synchronous and asynchronous backups.
# cas.service-registry.stream.hazelcast.config.cluster.core.async-backup-count=0

# Used when replication is turned on with {@link #isReplicated()}.
# cas.service-registry.stream.hazelcast.config.cluster.core.async-fillup=true

# To provide data safety, Hazelcast allows you to specify the number of backup copies you want to have.
# cas.service-registry.stream.hazelcast.config.cluster.core.backup-count=1

# CP Subsystem is a component of a Hazelcast cluster that builds a strongly consistent layer for a set of distributed data structures.
# cas.service-registry.stream.hazelcast.config.cluster.core.cp-member-count=0

# Hazelcast supports policy-based eviction for distributed maps.
# cas.service-registry.stream.hazelcast.config.cluster.core.eviction-policy=LRU

# Hazelcast has a flexible logging configuration and doesn't depend on any logging framework except JDK logging.
# cas.service-registry.stream.hazelcast.config.cluster.core.logging-type=slf4j

# Define how data items in Hazelcast maps are merged together from source to destination.
# cas.service-registry.stream.hazelcast.config.cluster.core.map-merge-policy=PUT_IF_ABSENT

# Max timeout of heartbeat in seconds for a node to assume it is dead.
# cas.service-registry.stream.hazelcast.config.cluster.core.max-no-heartbeat-seconds=300

# Sets the maximum size of the map.
# cas.service-registry.stream.hazelcast.config.cluster.core.max-size=85

#  {@code FREE_HEAP_PERCENTAGE}: Policy based on minimum free JVM heap memory percentage per JVM.
# cas.service-registry.stream.hazelcast.config.cluster.core.max-size-policy=USED_HEAP_PERCENTAGE

# With {@code PartitionGroupConfig}, you can control how primary and backup partitions are mapped to physical Members.
# cas.service-registry.stream.hazelcast.config.cluster.core.partition-member-group-type=

# A Replicated Map is a distributed key-value data structure where the data is replicated to all members in the cluster.
# cas.service-registry.stream.hazelcast.config.cluster.core.replicated=false

# Connection timeout in seconds for the TCP/IP config and members joining the cluster.
# cas.service-registry.stream.hazelcast.config.cluster.core.timeout=5

# Whether discovery should be enabled via the configured strategies below.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.enabled=false

# Enables a multicast configuration using a group address and port.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.enabled=false

# The multicast group address used for discovery.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.group=

# The multicast port used for discovery.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.port=0

# Gets the time to live for the multicast package in seconds.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.time-to-live=32

# specifies the time in seconds that a member should wait for a valid multicast response from another member running in the network before declaring itself the leader member (the first member joined to the cluster) and creating its own cluster.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.timeout=2

# Multicast trusted interfaces for discovery.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.multicast.trusted-interfaces=

# IPv6 support has been switched off by default, since some platforms have issues in use of IPv6 stack.
# cas.service-registry.stream.hazelcast.config.cluster.network.ipv4-enabled=true

# If this property is set, then this is the address where the server socket is bound to.
# cas.service-registry.stream.hazelcast.config.cluster.network.local-address=

# You can specify which network interfaces that Hazelcast should use.
# cas.service-registry.stream.hazelcast.config.cluster.network.network-interfaces=

# The outbound ports for the Hazelcast configuration.
# cas.service-registry.stream.hazelcast.config.cluster.network.outbound-ports=

# You may also want to choose to use only one port.
# cas.service-registry.stream.hazelcast.config.cluster.network.port-auto-increment=true

# The default public address to be advertised to other cluster members and clients.
# cas.service-registry.stream.hazelcast.config.cluster.network.public-address=

# Comma-separated list of cipher suite names allowed to be used.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.cipher-suites=

# Name of the algorithm based on which the authentication keys are provided.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-manager-algorithm=

# Type of the keystore.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.key-store-type=JKS

# Path of your keystore file.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore=

# Password to access the key from your keystore file.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.keystore-password=

# Mutual authentication configuration.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.mutual-authentication=

# Name of the algorithm which is used in your TLS/SSL.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.protocol=TLS

# Name of the algorithm based on which the trust managers are provided.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-manager-algorithm=

# Path of your truststore file.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store=

# Password to unlock the truststore file.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-password=

# Type of the truststore.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.trust-store-type=JKS

# Flag which allows enabling endpoint identity validation.
# cas.service-registry.stream.hazelcast.config.cluster.network.ssl.validate-identity=false

# Enable TCP/IP config.
# cas.service-registry.stream.hazelcast.config.cluster.network.tcpip-enabled=true

# Whether WAN should be enabled.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.enabled=false

# Name of this replication group.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.replication-name=apereo-cas

# List of target clusters to be used for synchronization and replication.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets=

# Accepted values are:  {@code ACK_ON_RECEIPT}: ACK after WAN operation is received by the target cluster (without waiting the result of actual operation invocation).
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].acknowledge-type=ACK_ON_OPERATION_COMPLETE

# Maximum amount of time, in milliseconds, to be waited before sending a batch of events in case batch.size is not reached.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-maximum-delay-milliseconds=1000

# Maximum size of events that are sent to the target cluster in a single batch.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].batch-size=500

# Sets the cluster name used as an endpoint group password for authentication on the target endpoint.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].cluster-name=

# Strategy for checking the consistency of data between replicas.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].consistency-check-strategy=NONE

# Comma separated list of endpoints in this replication group.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].endpoints=

# The number of threads that the replication executor will have.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].executor-thread-count=2

# The WAN publisher properties.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].properties=

# Publisher class name for WAN replication.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-class-name=com.hazelcast.enterprise.wan.replication.WanBatchReplication

# Returns the publisher ID used for identifying the publisher.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].publisher-id=

# For huge clusters or high data mutation rates, you might need to increase the replication queue size.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-capacity=10000

# Accepted values are:  {@code THROW_EXCEPTION}: Instruct WAN replication implementation to throw an exception and doesn't allow further processing.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].queue-full-behavior=THROW_EXCEPTION

# Time, in milliseconds, to be waited for the acknowledgment of a sent WAN event to target cluster.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].response-timeout-milliseconds=60000

# When set to true, only the latest events (based on key) are selected and sent in a batch.
# cas.service-registry.stream.hazelcast.config.cluster.wan-replication.targets[0].snapshot-enabled=

# Enables compression when default java serialization is used.
# cas.service-registry.stream.hazelcast.config.core.enable-compression=false

# Enable Jet configuration/service on the hazelcast instance.
# cas.service-registry.stream.hazelcast.config.core.enable-jet=true

# Enables scripting from Management Center.
# cas.service-registry.stream.hazelcast.config.core.enable-management-center-scripting=true

# Hazelcast enterprise license key.
# cas.service-registry.stream.hazelcast.config.core.license-key=

# ECS cluster short name or ARN; default is the current cluster.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.cluster=

# The maximum amount of time Hazelcast will try to connect to a well known member before giving up.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.connection-timeout-seconds=5

# Filter to look only for ECS tasks with the given family name; mutually exclusive with {@link #getServiceName()}.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.family=

# Host header. i.e.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.host-header=

# If you do not want to use access key and secret key, you can specify iam-role.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.iam-role=

# Hazelcast port.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.port=-1

# AWS region. i.e.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.region=us-east-1

# If a security group is configured, only instances within that security group are selected.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.security-group-name=

# Filter to look only for ECS tasks from the given service; mutually exclusive with {@link #getFamily()}.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.service-name=

# If a tag key/value is set, only instances with that tag key/value will be selected.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-key=

# If a tag key/value is set, only instances with that tag key/value will be selected.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.aws.tag-value=

# A range of ports where the plugin looks for Hazelcast members.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.hz-port=5701-5708

# A filter to look only for instances labeled as specified; property format: {@code key=value}.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.label=

# A filesystem path to the private key for GCP service account in the JSON format; if not set, the access token is fetched from the GCP VM instance.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.private-key-path=

# A list of projects where the plugin looks for instances; if not set, the current project is used.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.projects=

# A region where the plugin looks for instances; if not set, the {@link #getZones()} property is used; if it and {@link #getZones()} property not set, all zones of the current region are used.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.region=

# A list of zones where the plugin looks for instances; if not set, all zones of the current region are used.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.gcp.zones=

# Used for cloud providers which require an extra JSON or P12 key file.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.credential-path=

# Defines the endpoint for a generic API such as OpenStack or CloudStack (optional).
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.endpoint=

# Filters instance groups (optional).
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.group=

# Port which the hazelcast instance service uses on the cluster member.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.port=-1

# Defines region for a cloud service (optional).
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.regions=

# Used for IAM role support specific to AWS (optional, but if defined, no identity or credential should be defined in the configuration).
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.role-name=

# Filters cloud instances with tags (optional).
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-keys=

# Filters cloud instances with tags (optional) Can be used with comma separated values for multiple values.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.tag-values=

# Defines zone for a cloud service (optional).
# cas.service-registry.stream.hazelcast.config.cluster.discovery.jclouds.zones=

# Defines the number of retries to Kubernetes API.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-retries=3

# Defines an oauth token for the kubernetes client to access the kubernetes REST API.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.api-token=

# CA Authority certificate from Kubernetes Master.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.ca-certificate=

# Defines an alternative address for the kubernetes master.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.kubernetes-master=

# Defines the namespace of the application POD through the Service Discovery REST API of Kubernetes.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.namespace=

# Defines the pod label to lookup through the Service Discovery REST API of Kubernetes.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-name=

# Defines the pod label value to lookup through the Service Discovery REST API of Kubernetes.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.pod-label-value=

# Defines if not ready addresses should be evaluated to be discovered on startup.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.resolve-not-ready-addresses=false

# Defines the DNS service lookup domain.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns=

# Defines the DNS service lookup timeout in seconds.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-dns-timeout=-1

# Defines the service label to lookup through the Service Discovery REST API of Kubernetes.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-name=

# Defines the service label value to lookup through the Service Discovery REST API of Kubernetes.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-label-value=

# Defines the service name of the POD to lookup through the Service Discovery REST API of Kubernetes.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-name=

# If specified with a value greater than 0, its value defines the endpoint port of the service (overriding the default).
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.service-port=0

# Defines if the node name should be used as external address, instead of looking up the external IP using the {@code /nodes} resource.
# cas.service-registry.stream.hazelcast.config.cluster.discovery.kubernetes.use-node-name-as-external-address=false

# Duration that indicates how long should items be kept in the hazelcast cache.
# cas.service-registry.stream.hazelcast.duration=PT1M

CAS takes advantage of Apache Groovy in forms of either embedded or external scripts that allow one to, by default, dynamically build constructs, attributes, access strategies and a lot more. To activate the functionality described here, you may need to prepare CAS to support and integrate with Apache Groovy.

Please review this guide to configure your build.

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Apache Kafka

If you’d rather not resort to outside tooling and processes or if the native options for your deployment are not that attractive, you can take advantage of CAS’ own tooling that provides a distributed cache via Apache Kafka to broadcast service definition files across the cluster and add/remove/update each node as needed. As service definitions are loaded by CAS, events are broadcasted to all CAS nodes in the cluster to pick up the changes and keep definitions in sync.

Support is enabled by including the following dependency in the overlay:

<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-service-registry-stream-kafka</artifactId>
    <version>${cas.version}</version>
</dependency>

implementation "org.apereo.cas:cas-server-support-service-registry-stream-kafka:${project.'cas.version'}"

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

dependencies {
    implementation "org.apereo.cas:cas-server-support-service-registry-stream-kafka"
}

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

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

The following settings and properties are available from the CAS configuration catalog:

cas.service-registry.stream.kafka.topic.compression-type=gzip

Specify the final compression type for a given topic. This configuration accepts the standard compression codecs ('gzip', 'snappy', 'lz4', 'zstd'). It additionally accepts 'uncompressed' which is equivalent to no compression; and 'producer' which means retain the original compression codec set by the producer.

org.apereo.cas.configuration.model.support.kafka.KafkaSingleTopicProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.kafka.topic.compression-type=gzip

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      kafka: 
        topic: 
          compression-type: "gzip"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.kafka.topic.compression-type="gzip" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_KAFKA_TOPIC_COMPRESSION_TYPE="gzip"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.kafka.topic.compression-type="gzip"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.kafka.topic.config=

Additional configuration options, as pointed out by TopicConfig.

org.apereo.cas.configuration.model.support.kafka.KafkaSingleTopicProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.kafka.topic.config=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      kafka: 
        topic: 
          config: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.kafka.topic.config="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_KAFKA_TOPIC_CONFIG="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.kafka.topic.config="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.kafka.topic.name=

Set the name of the topic.

org.apereo.cas.configuration.model.support.kafka.KafkaSingleTopicProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.kafka.topic.name=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      kafka: 
        topic: 
          name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.kafka.topic.name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_KAFKA_TOPIC_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.kafka.topic.name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.kafka.topic.partitions=1

Set the number of partitions (default 1).

org.apereo.cas.configuration.model.support.kafka.KafkaSingleTopicProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.kafka.topic.partitions=1

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      kafka: 
        topic: 
          partitions: "1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.kafka.topic.partitions="1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_KAFKA_TOPIC_PARTITIONS="1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.kafka.topic.partitions="1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.kafka.topic.replicas=1

Set the number of replicas (default 1).

org.apereo.cas.configuration.model.support.kafka.KafkaSingleTopicProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.kafka.topic.replicas=1

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      kafka: 
        topic: 
          replicas: "1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.kafka.topic.replicas="1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_KAFKA_TOPIC_REPLICAS="1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.kafka.topic.replicas="1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

cas.service-registry.stream.kafka.bootstrap-address=

Kafka bootstrapping server address (i.e. localhost:9092).

org.apereo.cas.configuration.model.support.services.stream.hazelcast.StreamServicesKafkaProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

cas.service-registry.stream.kafka.bootstrap-address=...

CAS properties can be specified using the YAML syntax:

cas: 
  service-registry: 
    stream: 
      kafka: 
        bootstrap-address: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dcas.service-registry.stream.kafka.bootstrap-address="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export CAS_SERVICE_REGISTRY_STREAM_KAFKA_BOOTSTRAP_ADDRESS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --cas.service-registry.stream.kafka.bootstrap-address="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Replication Modes

When CAS is configured to replicate service definitions in an active-active mode, you will need to make sure the service registry scheduler is carefully tuned in order to avoid surprises and overwrites. Likewise, the same sort of check needs to be done and verified for ad-hoc dynamic changes to the CAS service registry directory, if CAS is set to monitor for changes. Delays in replication and schedule may force one node to overwrite changes to the other.

For instance, consider the following scenario: there are two nodes in a CAS cluster where CAS1 is set to monitor changes from /etc/cas/services on node N1 and CAS2 is monitoring /etc/cas/services directory on node N2. Both N1 and N2 on startup attempt to bootstrap each other’s copies of service definitions to make sure all is synchronized correctly.

Now let’s consider that a file is /etc/cas/services/App-100.json is deleted from N2. In the time that it takes from N2 to broadcast the change to N1, it is likely that service registry scheduler for N2 also wakes up and attempts to restore the state of the world by synchronizing its copies of its service definition files from the distributed cache, which means that N2 will grab a copy of the deleted service from N1 and will restore the deleted file back. This situation typically manifests itself when the service registry scheduler is set to very aggressive timeouts and can mostly be avoided by relaxing the reload operation to run on a long scheduler such as every 2 hours. Alternatively, you may decide to run an active-passive setup to only have one master node produce and broadcast changes and other slave/passive nodes and only consume changes when needed.