Configuration Management - Clustered Deployments with Kafka
Apache Kafka is an open-source message broker project developed by the Apache Software Foundation. The project aims to provide a unified, high-throughput, low-latency platform for handling real-time data feeds. It is, in its essence, a “massively scalable pub/sub message queue designed as a distributed transaction log”, making it highly valuable for enterprise infrastructures to process streaming data.
Support is enabled by including the following dependency in the final overlay:
1
2
3
4
5
<dependency>
<groupId>org.apereo.cas</groupId>
<artifactId>cas-server-support-configuration-cloud-kafka</artifactId>
<version>${cas.version}</version>
</dependency>
1
implementation "org.apereo.cas:cas-server-support-configuration-cloud-kafka:${project.'cas.version'}"
1
2
3
4
5
6
7
8
9
dependencyManagement {
imports {
mavenBom "org.apereo.cas:cas-server-support-bom:${project.'cas.version'}"
}
}
dependencies {
implementation "org.apereo.cas:cas-server-support-configuration-cloud-kafka"
}
1
2
3
4
5
6
7
8
9
10
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-configuration-cloud-kafka"
}
Broadcast CAS configuration updates to other nodes in the cluster via Kafka.
The following settings and properties are available from the CAS configuration catalog:
- Required
- Optional
- Signing & Encryption
- Hibernate & JDBC
- Email Servers
- Groovy Scripting
- LDAP & Active Directory
- Authentication
- Password Encoding
- Principal Transformation
- Password Policy
- Third Party
- Notes
spring.cloud.stream.kafka.binder.authorization-exception-retry-interval=
CAS Property:
|
1 |
spring.cloud.stream.kafka.binder.authorization-exception-retry-interval=... |
1
spring:
cloud:
stream:
kafka:
binder:
authorization-exception-retry-interval: "..."
1
java -Dspring.cloud.stream.kafka.binder.authorization-exception-retry-interval="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_AUTHORIZATION_EXCEPTION_RETRY_INTERVAL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.authorization-exception-retry-interval="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.auto-add-partitions=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.auto-add-partitions
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.auto-add-partitions=...
1
spring:
cloud:
stream:
kafka:
binder:
auto-add-partitions: "..."
1
java -Dspring.cloud.stream.kafka.binder.auto-add-partitions="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_AUTO_ADD_PARTITIONS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.auto-add-partitions="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.auto-alter-topics=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.auto-alter-topics
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.auto-alter-topics=...
1
spring:
cloud:
stream:
kafka:
binder:
auto-alter-topics: "..."
1
java -Dspring.cloud.stream.kafka.binder.auto-alter-topics="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_AUTO_ALTER_TOPICS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.auto-alter-topics="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.auto-create-topics=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.auto-create-topics
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.auto-create-topics=...
1
spring:
cloud:
stream:
kafka:
binder:
auto-create-topics: "..."
1
java -Dspring.cloud.stream.kafka.binder.auto-create-topics="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_AUTO_CREATE_TOPICS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.auto-create-topics="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.brokers=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.brokers
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.brokers=...
1
spring:
cloud:
stream:
kafka:
binder:
brokers: "..."
1
java -Dspring.cloud.stream.kafka.binder.brokers="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_BROKERS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.brokers="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.certificate-store-directory=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.certificate-store-directory
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.certificate-store-directory=...
1
spring:
cloud:
stream:
kafka:
binder:
certificate-store-directory: "..."
1
java -Dspring.cloud.stream.kafka.binder.certificate-store-directory="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_CERTIFICATE_STORE_DIRECTORY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.certificate-store-directory="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.configuration=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.configuration
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.configuration=...
1
spring:
cloud:
stream:
kafka:
binder:
configuration: "..."
1
java -Dspring.cloud.stream.kafka.binder.configuration="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_CONFIGURATION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.configuration="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.consider-down-when-any-partition-has-no-leader=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.consider-down-when-any-partition-has-no-leader
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.consider-down-when-any-partition-has-no-leader=...
1
spring:
cloud:
stream:
kafka:
binder:
consider-down-when-any-partition-has-no-leader: "..."
1
java -Dspring.cloud.stream.kafka.binder.consider-down-when-any-partition-has-no-leader="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_CONSIDER_DOWN_WHEN_ANY_PARTITION_HAS_NO_LEADER="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.consider-down-when-any-partition-has-no-leader="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.consumer-properties=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.consumer-properties
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.consumer-properties=...
1
spring:
cloud:
stream:
kafka:
binder:
consumer-properties: "..."
1
java -Dspring.cloud.stream.kafka.binder.consumer-properties="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_CONSUMER_PROPERTIES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.consumer-properties="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.enable-observation=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.enable-observation
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.enable-observation=...
1
spring:
cloud:
stream:
kafka:
binder:
enable-observation: "..."
1
java -Dspring.cloud.stream.kafka.binder.enable-observation="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_ENABLE_OBSERVATION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.enable-observation="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.header-mapper-bean-name=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.header-mapper-bean-name
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.header-mapper-bean-name=...
1
spring:
cloud:
stream:
kafka:
binder:
header-mapper-bean-name: "..."
1
java -Dspring.cloud.stream.kafka.binder.header-mapper-bean-name="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_HEADER_MAPPER_BEAN_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.header-mapper-bean-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.headers=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.headers
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.headers=...
1
spring:
cloud:
stream:
kafka:
binder:
headers: "..."
1
java -Dspring.cloud.stream.kafka.binder.headers="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_HEADERS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.headers="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.health-indicator-consumer-group=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.health-indicator-consumer-group
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.health-indicator-consumer-group=...
1
spring:
cloud:
stream:
kafka:
binder:
health-indicator-consumer-group: "..."
1
java -Dspring.cloud.stream.kafka.binder.health-indicator-consumer-group="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_HEALTH_INDICATOR_CONSUMER_GROUP="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.health-indicator-consumer-group="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.health-timeout=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.health-timeout
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.health-timeout=...
1
spring:
cloud:
stream:
kafka:
binder:
health-timeout: "..."
1
java -Dspring.cloud.stream.kafka.binder.health-timeout="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_HEALTH_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.health-timeout="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.jaas=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.jaas
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.jaas=...
1
spring:
cloud:
stream:
kafka:
binder:
jaas: "..."
1
java -Dspring.cloud.stream.kafka.binder.jaas="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_JAAS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.jaas="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.metrics.default-offset-lag-metrics-enabled=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$Metrics.
CAS Property: spring.cloud.stream.kafka.binder.metrics.default-offset-lag-metrics-enabled
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.metrics.default-offset-lag-metrics-enabled=...
1
spring:
cloud:
stream:
kafka:
binder:
metrics:
default-offset-lag-metrics-enabled: "..."
1
java -Dspring.cloud.stream.kafka.binder.metrics.default-offset-lag-metrics-enabled="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_METRICS_DEFAULT_OFFSET_LAG_METRICS_ENABLED="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.metrics.default-offset-lag-metrics-enabled="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.metrics.offset-lag-metrics-interval=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$Metrics.
CAS Property: spring.cloud.stream.kafka.binder.metrics.offset-lag-metrics-interval
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.metrics.offset-lag-metrics-interval=...
1
spring:
cloud:
stream:
kafka:
binder:
metrics:
offset-lag-metrics-interval: "..."
1
java -Dspring.cloud.stream.kafka.binder.metrics.offset-lag-metrics-interval="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_METRICS_OFFSET_LAG_METRICS_INTERVAL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.metrics.offset-lag-metrics-interval="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.min-partition-count=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.min-partition-count
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.min-partition-count=...
1
spring:
cloud:
stream:
kafka:
binder:
min-partition-count: "..."
1
java -Dspring.cloud.stream.kafka.binder.min-partition-count="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_MIN_PARTITION_COUNT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.min-partition-count="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.producer-properties=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.producer-properties
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.producer-properties=...
1
spring:
cloud:
stream:
kafka:
binder:
producer-properties: "..."
1
java -Dspring.cloud.stream.kafka.binder.producer-properties="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_PRODUCER_PROPERTIES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.producer-properties="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.replication-factor=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.replication-factor
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.replication-factor=...
1
spring:
cloud:
stream:
kafka:
binder:
replication-factor: "..."
1
java -Dspring.cloud.stream.kafka.binder.replication-factor="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_REPLICATION_FACTOR="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.replication-factor="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.required-acks=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties.
CAS Property: spring.cloud.stream.kafka.binder.required-acks
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.required-acks=...
1
spring:
cloud:
stream:
kafka:
binder:
required-acks: "..."
1
java -Dspring.cloud.stream.kafka.binder.required-acks="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_REQUIRED_ACKS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.required-acks="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.batch-timeout=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.batch-timeout
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.batch-timeout=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
batch-timeout: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.batch-timeout="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_BATCH_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.batch-timeout="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.buffer-size=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.buffer-size
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.buffer-size=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
buffer-size: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.buffer-size="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_BUFFER_SIZE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.buffer-size="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.compression-type=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.compression-type
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.compression-type=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
compression-type: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.compression-type="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_COMPRESSION_TYPE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.compression-type="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.configuration=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.configuration
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.configuration=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
configuration: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.configuration="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_CONFIGURATION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.configuration="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.error-channel-enabled=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.error-channel-enabled
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.error-channel-enabled=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
error-channel-enabled: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.error-channel-enabled="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_ERROR_CHANNEL_ENABLED="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.error-channel-enabled="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.header-mode=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.header-mode
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.header-mode=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
header-mode: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.header-mode="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_HEADER_MODE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.header-mode="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.header-patterns=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.header-patterns
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.header-patterns=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
header-patterns: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.header-patterns="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_HEADER_PATTERNS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.header-patterns="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.message-key-expression=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.message-key-expression
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.message-key-expression=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
message-key-expression: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.message-key-expression="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_MESSAGE_KEY_EXPRESSION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.message-key-expression="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.partition-count=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.partition-count
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.partition-count=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
partition-count: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.partition-count="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_PARTITION_COUNT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.partition-count="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.partition-key-expression=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.partition-key-expression
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.partition-key-expression=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
partition-key-expression: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.partition-key-expression="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_PARTITION_KEY_EXPRESSION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.partition-key-expression="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.partition-key-extractor-name=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.partition-key-extractor-name
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.partition-key-extractor-name=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
partition-key-extractor-name: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.partition-key-extractor-name="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_PARTITION_KEY_EXTRACTOR_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.partition-key-extractor-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.partition-selector-expression=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.partition-selector-expression
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.partition-selector-expression=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
partition-selector-expression: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.partition-selector-expression="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_PARTITION_SELECTOR_EXPRESSION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.partition-selector-expression="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.partition-selector-name=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.partition-selector-name
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.partition-selector-name=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
partition-selector-name: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.partition-selector-name="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_PARTITION_SELECTOR_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.partition-selector-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.required-groups=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.required-groups
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.required-groups=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
required-groups: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.required-groups="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_REQUIRED_GROUPS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.required-groups="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.sync=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.sync
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.sync=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
sync: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.sync="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_SYNC="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.sync="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.topic=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.topic
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.topic=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
topic: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.topic="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_TOPIC="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.topic="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.producer.use-native-encoding=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$CombinedProducerProperties.
CAS Property: spring.cloud.stream.kafka.binder.transaction.producer.use-native-encoding
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.producer.use-native-encoding=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
producer:
use-native-encoding: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.producer.use-native-encoding="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_PRODUCER_USE_NATIVE_ENCODING="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.producer.use-native-encoding="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.binder.transaction.transaction-id-prefix=
org.springframework.cloud.stream.binder.kafka.properties.KafkaBinderConfigurationProperties$Transaction.
CAS Property: spring.cloud.stream.kafka.binder.transaction.transaction-id-prefix
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.
.properties
files:
1
spring.cloud.stream.kafka.binder.transaction.transaction-id-prefix=...
1
spring:
cloud:
stream:
kafka:
binder:
transaction:
transaction-id-prefix: "..."
1
java -Dspring.cloud.stream.kafka.binder.transaction.transaction-id-prefix="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDER_TRANSACTION_TRANSACTION_ID_PREFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.binder.transaction.transaction-id-prefix="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.stream.kafka.bindings=
org.springframework.cloud.stream.binder.kafka.properties.KafkaExtendedBindingProperties.
CAS Property: spring.cloud.stream.kafka.bindings
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.
.properties
files:
1
spring.cloud.stream.kafka.bindings=...
1
spring:
cloud:
stream:
kafka:
bindings: "..."
1
java -Dspring.cloud.stream.kafka.bindings="..." -jar build/libs/cas.war
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.
1
2
3
export SPRING_CLOUD_STREAM_KAFKA_BINDINGS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.stream.kafka.bindings="..."
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.
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas
. All other settings are controlled and provided
to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with
the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition
or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the
way you intend.
Validation
Configuration properties are automatically validated on CAS startup to report issues with configuration binding, specially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.
Indexed Settings
CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value
. The index [0]
is meant to be
incremented by the adopter to allow for distinct multiple configuration blocks.
Troubleshooting
To enable additional logging, modify the logging configuration file to add the following:
1
2
3
4
<Logger name="org.springframework.kafka" level="debug" additivity="false">
<AppenderRef ref="casConsole"/>
<AppenderRef ref="casFile"/>
</Logger>