Configuration Server - Standalone Profile
This is the default configuration mode which indicates that CAS does NOT require connections to an external configuration server
and will run in an embedded standalone mode. When this option is turned on, CAS by default will attempt to locate settings and properties
inside a pre-defined directories and files and otherwise falls back to typically using /etc/cas/config
as the configuration directory.
Similar to the Spring Cloud external configuration server, the contents of this directory include (cas|application).(yml|properties)
files that can be used to control CAS behavior. Also, note that this configuration directory can be monitored by CAS to auto-pick up changes
and refresh the application context as needed. Please review this guide to learn more.
Note that by default, all CAS settings and configuration is controlled via the embedded application.properties
file in the CAS server
web application. There is also an embedded application.yml
file that allows you to override all defaults if you wish to ship the
configuration inside the main CAS web application and not rely on externalized configuration files. If you prefer
properties to yaml, then application-standalone.properties
will override application.properties
as well.
Settings found in external configuration files are and will be able to override the defaults provided by CAS. The naming of the configuration files inside the CAS configuration directory follows the below pattern:
- An
application.(properties|yml|yaml)
file is always loaded, if found. - Settings located inside
properties|yml|yaml
files whose name matches the value ofspring.application.name
are loaded (i.ecas.properties
) Note:spring.application.name
defaults to uppercaseCAS
but the lowercase name will also be loaded. - Settings located inside
properties|yml|yaml
files whose name matches the value ofspring.profiles.active
are loaded (i.eldap.properties
). - Profile-specific application properties outside of your packaged web application (
application-{profile}.properties|yml|yaml
) This allows you to, if needed, split your settings into multiple property files and then locate them by assigning their name to the list of active profiles (i.e.spring.profiles.active=standalone,testldap,stagingMfa
)
Configuration files are loaded in the following order where spring.profiles.active=standalone,profile1,profile2
. Note
that the last configuration file loaded will override any duplicate properties from configuration files loaded earlier:
application.(properties|yml|yaml)
- (lower case)
spring.application.name.(properties|yml|yaml)
spring.application.name.(properties|yml|yaml)
application-standalone.(properties|yml|yaml)
standalone.(properties|yml|yaml)
application-profile1.(properties|yml|yaml)
profile1.(properties|yml|yaml)
application-profile2.(properties|yml|yaml)
profile2.(properties|yml|yaml)
If two configuration files with same base name and different extensions exist, they are processed in the order
of properties
, yml
and then yaml
and then groovy
(last one processed wins where duplicate properties exist). These
external configuration files will override files located in the classpath (e.g. files from src/main/resources
in
your CAS overlay that end up in WEB-INF/classes
) but the internal files are loaded per
the Spring Boot rules
which differ from the CAS standalone configuration rules described here (e.g. <profile>.properties
would not be loaded from classpath but application-<profile>.properties
would).
Sources
CAS by default will attempt to locate settings and properties using:
/etc/cas/config
/opt/cas/config
/var/cas/config
CAS has the ability to also load a Groovy file for loading settings. The file
is expected to be found at the above matching directory and should be named ${cas-application-name}.groovy
, such as cas.groovy
. The
script is able to combine conditional settings for active profiles and common settings that are applicable to all environments and profiles into one location with a structure that is similar to the below example:
1
2
3
4
5
6
7
8
9
// Settings may be filtered by individual profiles
profiles {
standalone {
cas.some.setting="value"
}
}
// This applies to all profiles and environments
cas.common.setting="value"
To prepare CAS to support and integrate with Apache Groovy, please review this guide.
You can also use a dedicated configuration file to directly feed a collection of properties to CAS in form of a file or classpath resource. This is specially useful in cases where a bare CAS server is deployed in the cloud without the extra ceremony of a configuration server or an external directory for that matter and the deployer wishes to avoid overriding embedded configuration files.
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
- Notes
cas.standalone.configuration-directory=
Describes a directory path where CAS configuration may be found.
CAS Property:
|
1 |
cas.standalone.configuration-directory=... |
1
cas:
standalone:
configuration-directory: "..."
1
java -Dcas.standalone.configuration-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 CAS_STANDALONE_CONFIGURATION_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 --cas.standalone.configuration-directory="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
cas.standalone.configuration-file=
Describes a file path where that contains the CAS properties in a single file.
org.apereo.cas.configuration.model.core.config.standalone.StandaloneConfigurationProperties.
CAS Property: cas.standalone.configuration-file
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
cas.standalone.configuration-file=...
1
cas:
standalone:
configuration-file: "..."
1
java -Dcas.standalone.configuration-file="..." -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 CAS_STANDALONE_CONFIGURATION_FILE="..."
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 --cas.standalone.configuration-file="..."
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.
Handling Overrides
You are advised to not overlay or otherwise
modify the built in application.properties
or bootstrap.properties
files.
This will only complicate and weaken your deployment.
Instead try to comply with the CAS defaults and bootstrap CAS as much as possible via the defaults,
override via application.yml
, application-standalone.properties
or
use the outlined strategies. Likewise, try to instruct CAS to locate
configuration files external to its own. Premature optimization will only lead to chaos.
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.config.allow-override=true
Flag to indicate that
CAS Property:
|
1 |
spring.cloud.config.allow-override=true |
1
spring:
cloud:
config:
allow-override: "true"
1
java -Dspring.cloud.config.allow-override="true" -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_CONFIG_ALLOW_OVERRIDE="true"
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.config.allow-override="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.discovery.enabled=false
Flag to indicate that config server discovery is enabled (config server URL will be looked up via discovery).
org.springframework.cloud.config.client.ConfigClientProperties$Discovery.
CAS Property: spring.cloud.config.discovery.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.config.discovery.enabled=...
1
spring:
cloud:
config:
discovery:
enabled: "..."
1
java -Dspring.cloud.config.discovery.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_CONFIG_DISCOVERY_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.config.discovery.enabled="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.discovery.service-id=configserver
Service id to locate config server.
org.springframework.cloud.config.client.ConfigClientProperties$Discovery.
CAS Property: spring.cloud.config.discovery.service-id
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.config.discovery.service-id=configserver
1
spring:
cloud:
config:
discovery:
service-id: "configserver"
1
java -Dspring.cloud.config.discovery.service-id="configserver" -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_CONFIG_DISCOVERY_SERVICE_ID="configserver"
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.config.discovery.service-id="configserver"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.enabled=true
Flag to say that remote configuration is enabled. Default true;
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.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.config.enabled=true
1
spring:
cloud:
config:
enabled: "true"
1
java -Dspring.cloud.config.enabled="true" -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_CONFIG_ENABLED="true"
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.config.enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.fail-fast=false
Flag to indicate that failure to connect to the server is fatal (default false).
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.fail-fast
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.config.fail-fast=...
1
spring:
cloud:
config:
fail-fast: "..."
1
java -Dspring.cloud.config.fail-fast="..." -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_CONFIG_FAIL_FAST="..."
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.config.fail-fast="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.headers=
Additional headers used to create the client request.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.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.config.headers=...
1
spring:
cloud:
config:
headers: "..."
1
java -Dspring.cloud.config.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_CONFIG_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.config.headers="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.initialize-on-context-refresh=false
Flag to initialize bootstrap configuration on context refresh event. Default false.
org.springframework.cloud.bootstrap.config.PropertySourceBootstrapProperties.
CAS Property: spring.cloud.config.initialize-on-context-refresh
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.config.initialize-on-context-refresh=...
1
spring:
cloud:
config:
initialize-on-context-refresh: "..."
1
java -Dspring.cloud.config.initialize-on-context-refresh="..." -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_CONFIG_INITIALIZE_ON_CONTEXT_REFRESH="..."
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.config.initialize-on-context-refresh="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.label=
The label name to use to pull remote configuration properties. The default is set on the server (generally "main" for a git based server).
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.label
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.config.label=...
1
spring:
cloud:
config:
label: "..."
1
java -Dspring.cloud.config.label="..." -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_CONFIG_LABEL="..."
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.config.label="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.media-type=
The Accept header media type to send to config server.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.media-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.config.media-type=...
1
spring:
cloud:
config:
media-type: "..."
1
java -Dspring.cloud.config.media-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_CONFIG_MEDIA_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.config.media-type="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.multiple-uri-strategy=
The strategy to use when call to server fails and there are multiple URLs configured on the uri property (default MultipleUriStrategy#ALWAYS
).
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.multiple-uri-strategy
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.config.multiple-uri-strategy=...
1
spring:
cloud:
config:
multiple-uri-strategy: "..."
1
java -Dspring.cloud.config.multiple-uri-strategy="..." -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_CONFIG_MULTIPLE_URI_STRATEGY="..."
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.config.multiple-uri-strategy="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.name=
Name of application used to fetch remote properties.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.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.config.name=...
1
spring:
cloud:
config:
name: "..."
1
java -Dspring.cloud.config.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_CONFIG_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.config.name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.override-none=false
Flag to indicate that when #setAllowOverride(boolean) allowOverride
is true, external properties should take lowest priority and should not override any existing property sources (including local config files). Default false. This will only have an effect when using config first bootstrap.
org.springframework.cloud.bootstrap.config.PropertySourceBootstrapProperties.
CAS Property: spring.cloud.config.override-none
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.config.override-none=...
1
spring:
cloud:
config:
override-none: "..."
1
java -Dspring.cloud.config.override-none="..." -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_CONFIG_OVERRIDE_NONE="..."
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.config.override-none="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.override-system-properties=true
Flag to indicate that the external properties should override system properties. Default true.
org.springframework.cloud.bootstrap.config.PropertySourceBootstrapProperties.
CAS Property: spring.cloud.config.override-system-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.config.override-system-properties=true
1
spring:
cloud:
config:
override-system-properties: "true"
1
java -Dspring.cloud.config.override-system-properties="true" -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_CONFIG_OVERRIDE_SYSTEM_PROPERTIES="true"
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.config.override-system-properties="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.password=
The password to use (HTTP Basic) when contacting the remote server.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.password
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.config.password=...
1
spring:
cloud:
config:
password: "..."
1
java -Dspring.cloud.config.password="..." -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_CONFIG_PASSWORD="..."
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.config.password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.profile=default
The default profile to use when fetching remote configuration (comma-separated). Default is "default".
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.profile
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.config.profile=default
1
spring:
cloud:
config:
profile: "default"
1
java -Dspring.cloud.config.profile="default" -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_CONFIG_PROFILE="default"
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.config.profile="default"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.request-connect-timeout=0
timeout on waiting to connect to the Config Server.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.request-connect-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.config.request-connect-timeout=0
1
spring:
cloud:
config:
request-connect-timeout: "0"
1
java -Dspring.cloud.config.request-connect-timeout="0" -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_CONFIG_REQUEST_CONNECT_TIMEOUT="0"
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.config.request-connect-timeout="0"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.request-read-timeout=0
timeout on waiting to read data from the Config Server.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.request-read-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.config.request-read-timeout=0
1
spring:
cloud:
config:
request-read-timeout: "0"
1
java -Dspring.cloud.config.request-read-timeout="0" -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_CONFIG_REQUEST_READ_TIMEOUT="0"
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.config.request-read-timeout="0"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.retry.initial-interval=1000
Initial retry interval in milliseconds.
org.springframework.cloud.config.client.RetryProperties.
CAS Property: spring.cloud.config.retry.initial-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.config.retry.initial-interval=1000
1
spring:
cloud:
config:
retry:
initial-interval: "1000"
1
java -Dspring.cloud.config.retry.initial-interval="1000" -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_CONFIG_RETRY_INITIAL_INTERVAL="1000"
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.config.retry.initial-interval="1000"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.retry.max-attempts=6
Maximum number of attempts.
org.springframework.cloud.config.client.RetryProperties.
CAS Property: spring.cloud.config.retry.max-attempts
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.config.retry.max-attempts=6
1
spring:
cloud:
config:
retry:
max-attempts: "6"
1
java -Dspring.cloud.config.retry.max-attempts="6" -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_CONFIG_RETRY_MAX_ATTEMPTS="6"
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.config.retry.max-attempts="6"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.retry.max-interval=2000
Maximum interval for backoff.
org.springframework.cloud.config.client.RetryProperties.
CAS Property: spring.cloud.config.retry.max-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.config.retry.max-interval=2000
1
spring:
cloud:
config:
retry:
max-interval: "2000"
1
java -Dspring.cloud.config.retry.max-interval="2000" -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_CONFIG_RETRY_MAX_INTERVAL="2000"
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.config.retry.max-interval="2000"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.retry.multiplier=1.1
Multiplier for next interval.
org.springframework.cloud.config.client.RetryProperties.
CAS Property: spring.cloud.config.retry.multiplier
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.config.retry.multiplier=1.1
1
spring:
cloud:
config:
retry:
multiplier: "1.1"
1
java -Dspring.cloud.config.retry.multiplier="1.1" -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_CONFIG_RETRY_MULTIPLIER="1.1"
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.config.retry.multiplier="1.1"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.retry.use-random-policy=false
Use a random exponential backoff policy.
org.springframework.cloud.config.client.RetryProperties.
CAS Property: spring.cloud.config.retry.use-random-policy
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.config.retry.use-random-policy=...
1
spring:
cloud:
config:
retry:
use-random-policy: "..."
1
java -Dspring.cloud.config.retry.use-random-policy="..." -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_CONFIG_RETRY_USE_RANDOM_POLICY="..."
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.config.retry.use-random-policy="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.send-state=true
Flag to indicate whether to send state. Default true.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.send-state
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.config.send-state=true
1
spring:
cloud:
config:
send-state: "true"
1
java -Dspring.cloud.config.send-state="true" -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_CONFIG_SEND_STATE="true"
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.config.send-state="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.accept-empty=true
Flag to indicate that If HTTP 404 needs to be sent if Application is not Found.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.accept-empty
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.config.server.accept-empty=true
1
spring:
cloud:
config:
server:
accept-empty: "true"
1
java -Dspring.cloud.config.server.accept-empty="true" -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_CONFIG_SERVER_ACCEPT_EMPTY="true"
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.config.server.accept-empty="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.aws-secretsmanager.default-label=
The default staging label to be used to fetch the secret values. If unset, an active version of the secret will be fetched (AWSCURRENT).
org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.aws-secretsmanager.default-label
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.config.server.aws-secretsmanager.default-label=...
1
spring:
cloud:
config:
server:
aws-secretsmanager:
default-label: "..."
1
java -Dspring.cloud.config.server.aws-secretsmanager.default-label="..." -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_CONFIG_SERVER_AWS_SECRETSMANAGER_DEFAULT_LABEL="..."
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.config.server.aws-secretsmanager.default-label="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.aws-secretsmanager.endpoint=
The endpoint to be used by AWS Secrets Manager client. This can be used to specify an alternate endpoint for the API requests.
org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.aws-secretsmanager.endpoint
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.config.server.aws-secretsmanager.endpoint=...
1
spring:
cloud:
config:
server:
aws-secretsmanager:
endpoint: "..."
1
java -Dspring.cloud.config.server.aws-secretsmanager.endpoint="..." -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_CONFIG_SERVER_AWS_SECRETSMANAGER_ENDPOINT="..."
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.config.server.aws-secretsmanager.endpoint="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.aws-secretsmanager.ignore-label=false
Do not set staging label when fetching the secret values.
org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.aws-secretsmanager.ignore-label
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.config.server.aws-secretsmanager.ignore-label=...
1
spring:
cloud:
config:
server:
aws-secretsmanager:
ignore-label: "..."
1
java -Dspring.cloud.config.server.aws-secretsmanager.ignore-label="..." -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_CONFIG_SERVER_AWS_SECRETSMANAGER_IGNORE_LABEL="..."
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.config.server.aws-secretsmanager.ignore-label="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.aws-secretsmanager.order=
The order of the environment repository.
org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.aws-secretsmanager.order
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.config.server.aws-secretsmanager.order=...
1
spring:
cloud:
config:
server:
aws-secretsmanager:
order: "..."
1
java -Dspring.cloud.config.server.aws-secretsmanager.order="..." -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_CONFIG_SERVER_AWS_SECRETSMANAGER_ORDER="..."
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.config.server.aws-secretsmanager.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.aws-secretsmanager.origin=aws:secrets:
Prefix which indicates the origin of the property. Defaults to "aws:secrets:".
org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.aws-secretsmanager.origin
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.config.server.aws-secretsmanager.origin=aws:secrets:
1
spring:
cloud:
config:
server:
aws-secretsmanager:
origin: "aws:secrets:"
1
java -Dspring.cloud.config.server.aws-secretsmanager.origin="aws:secrets:" -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_CONFIG_SERVER_AWS_SECRETSMANAGER_ORIGIN="aws:secrets:"
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.config.server.aws-secretsmanager.origin="aws:secrets:"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.aws-secretsmanager.prefix=
Prefix indicating first level for every property loaded from AWS Secrets Manager. Value must start with a forward slash followed by a valid path segment or be empty. Defaults to "/secret".
org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.aws-secretsmanager.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.config.server.aws-secretsmanager.prefix=...
1
spring:
cloud:
config:
server:
aws-secretsmanager:
prefix: "..."
1
java -Dspring.cloud.config.server.aws-secretsmanager.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_CONFIG_SERVER_AWS_SECRETSMANAGER_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.config.server.aws-secretsmanager.prefix="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.aws-secretsmanager.profile-separator=-
String that separates profile from the application name.
org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.aws-secretsmanager.profile-separator
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.config.server.aws-secretsmanager.profile-separator=-
1
spring:
cloud:
config:
server:
aws-secretsmanager:
profile-separator: "-"
1
java -Dspring.cloud.config.server.aws-secretsmanager.profile-separator="-" -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_CONFIG_SERVER_AWS_SECRETSMANAGER_PROFILE_SEPARATOR="-"
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.config.server.aws-secretsmanager.profile-separator="-"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.aws-secretsmanager.region=
The region to be used by AWS Secrets Manager client.
org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.aws-secretsmanager.region
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.config.server.aws-secretsmanager.region=...
1
spring:
cloud:
config:
server:
aws-secretsmanager:
region: "..."
1
java -Dspring.cloud.config.server.aws-secretsmanager.region="..." -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_CONFIG_SERVER_AWS_SECRETSMANAGER_REGION="..."
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.config.server.aws-secretsmanager.region="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.decrypt-values=true
Flag to indicate the retrieval of all AWS parameters in a hierarchy with their value decrypted. Defaults to "true".
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.decrypt-values
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.config.server.awsparamstore.decrypt-values=true
1
spring:
cloud:
config:
server:
awsparamstore:
decrypt-values: "true"
1
java -Dspring.cloud.config.server.awsparamstore.decrypt-values="true" -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_CONFIG_SERVER_AWSPARAMSTORE_DECRYPT_VALUES="true"
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.config.server.awsparamstore.decrypt-values="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.endpoint=
The service endpoint to be used by the AWS Parameter Store client.
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.endpoint
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.config.server.awsparamstore.endpoint=...
1
spring:
cloud:
config:
server:
awsparamstore:
endpoint: "..."
1
java -Dspring.cloud.config.server.awsparamstore.endpoint="..." -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_CONFIG_SERVER_AWSPARAMSTORE_ENDPOINT="..."
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.config.server.awsparamstore.endpoint="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.max-results=10
The maximum number of items to return for an AWS Parameter Store API call. Defaults to "10".
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.max-results
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.config.server.awsparamstore.max-results=10
1
spring:
cloud:
config:
server:
awsparamstore:
max-results: "10"
1
java -Dspring.cloud.config.server.awsparamstore.max-results="10" -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_CONFIG_SERVER_AWSPARAMSTORE_MAX_RESULTS="10"
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.config.server.awsparamstore.max-results="10"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.order=
The order of the environment repository.
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.order
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.config.server.awsparamstore.order=...
1
spring:
cloud:
config:
server:
awsparamstore:
order: "..."
1
java -Dspring.cloud.config.server.awsparamstore.order="..." -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_CONFIG_SERVER_AWSPARAMSTORE_ORDER="..."
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.config.server.awsparamstore.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.origin=aws:ssm:parameter:
Prefix indicating the property's origin. Defaults to "aws:ssm:parameter:".
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.origin
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.config.server.awsparamstore.origin=aws:ssm:parameter:
1
spring:
cloud:
config:
server:
awsparamstore:
origin: "aws:ssm:parameter:"
1
java -Dspring.cloud.config.server.awsparamstore.origin="aws:ssm:parameter:" -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_CONFIG_SERVER_AWSPARAMSTORE_ORIGIN="aws:ssm:parameter:"
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.config.server.awsparamstore.origin="aws:ssm:parameter:"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.prefix=
Prefix indicating first level for every property loaded from the AWS Parameter Store. Value must start with a forward slash followed by one or more valid path segments or be empty. Defaults to "/config".
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.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.config.server.awsparamstore.prefix=...
1
spring:
cloud:
config:
server:
awsparamstore:
prefix: "..."
1
java -Dspring.cloud.config.server.awsparamstore.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_CONFIG_SERVER_AWSPARAMSTORE_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.config.server.awsparamstore.prefix="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.profile-separator=-
String that separates an appended profile from the context name. Note that an AWS parameter name can only contain dots, dashes and underscores next to alphanumeric characters. Defaults to "-".
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.profile-separator
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.config.server.awsparamstore.profile-separator=-
1
spring:
cloud:
config:
server:
awsparamstore:
profile-separator: "-"
1
java -Dspring.cloud.config.server.awsparamstore.profile-separator="-" -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_CONFIG_SERVER_AWSPARAMSTORE_PROFILE_SEPARATOR="-"
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.config.server.awsparamstore.profile-separator="-"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.recursive=true
Flag to indicate the retrieval of all AWS parameters within a hierarchy. Defaults to "true".
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.recursive
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.config.server.awsparamstore.recursive=true
1
spring:
cloud:
config:
server:
awsparamstore:
recursive: "true"
1
java -Dspring.cloud.config.server.awsparamstore.recursive="true" -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_CONFIG_SERVER_AWSPARAMSTORE_RECURSIVE="true"
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.config.server.awsparamstore.recursive="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awsparamstore.region=
The region to be used by the AWS Parameter Store client.
org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.
CAS Property: spring.cloud.config.server.awsparamstore.region
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.config.server.awsparamstore.region=...
1
spring:
cloud:
config:
server:
awsparamstore:
region: "..."
1
java -Dspring.cloud.config.server.awsparamstore.region="..." -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_CONFIG_SERVER_AWSPARAMSTORE_REGION="..."
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.config.server.awsparamstore.region="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awss3.bucket=
Name of the S3 bucket that contains config.
org.springframework.cloud.config.server.environment.AwsS3EnvironmentProperties.
CAS Property: spring.cloud.config.server.awss3.bucket
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.config.server.awss3.bucket=...
1
spring:
cloud:
config:
server:
awss3:
bucket: "..."
1
java -Dspring.cloud.config.server.awss3.bucket="..." -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_CONFIG_SERVER_AWSS3_BUCKET="..."
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.config.server.awss3.bucket="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awss3.endpoint=
Adds the ability to override the baseUrl of the s3 client.
org.springframework.cloud.config.server.environment.AwsS3EnvironmentProperties.
CAS Property: spring.cloud.config.server.awss3.endpoint
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.config.server.awss3.endpoint=...
1
spring:
cloud:
config:
server:
awss3:
endpoint: "..."
1
java -Dspring.cloud.config.server.awss3.endpoint="..." -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_CONFIG_SERVER_AWSS3_ENDPOINT="..."
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.config.server.awss3.endpoint="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awss3.order=0
org.springframework.cloud.config.server.environment.AwsS3EnvironmentProperties.
CAS Property: spring.cloud.config.server.awss3.order
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.config.server.awss3.order=0
1
spring:
cloud:
config:
server:
awss3:
order: "0"
1
java -Dspring.cloud.config.server.awss3.order="0" -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_CONFIG_SERVER_AWSS3_ORDER="0"
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.config.server.awss3.order="0"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.awss3.region=
AWS region that contains config.
org.springframework.cloud.config.server.environment.AwsS3EnvironmentProperties.
CAS Property: spring.cloud.config.server.awss3.region
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.config.server.awss3.region=...
1
spring:
cloud:
config:
server:
awss3:
region: "..."
1
java -Dspring.cloud.config.server.awss3.region="..." -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_CONFIG_SERVER_AWSS3_REGION="..."
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.config.server.awss3.region="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.bootstrap=false
Flag indicating that the config server should initialize its own Environment with properties from the remote repository. Off by default because it delays startup but can be useful when embedding the server in another application.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.bootstrap
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.config.server.bootstrap=...
1
spring:
cloud:
config:
server:
bootstrap: "..."
1
java -Dspring.cloud.config.server.bootstrap="..." -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_CONFIG_SERVER_BOOTSTRAP="..."
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.config.server.bootstrap="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.credhub.ca-cert-files=
org.springframework.credhub.support.ClientOptions.
CAS Property: spring.cloud.config.server.credhub.ca-cert-files
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.config.server.credhub.ca-cert-files=...
1
spring:
cloud:
config:
server:
credhub:
ca-cert-files: "..."
1
java -Dspring.cloud.config.server.credhub.ca-cert-files="..." -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_CONFIG_SERVER_CREDHUB_CA_CERT_FILES="..."
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.config.server.credhub.ca-cert-files="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.credhub.connection-timeout=
org.springframework.credhub.support.ClientOptions.
CAS Property: spring.cloud.config.server.credhub.connection-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.config.server.credhub.connection-timeout=...
1
spring:
cloud:
config:
server:
credhub:
connection-timeout: "..."
1
java -Dspring.cloud.config.server.credhub.connection-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_CONFIG_SERVER_CREDHUB_CONNECTION_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.config.server.credhub.connection-timeout="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.credhub.oauth2.registration-id=
org.springframework.credhub.core.CredHubProperties$OAuth2.
CAS Property: spring.cloud.config.server.credhub.oauth2.registration-id
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.config.server.credhub.oauth2.registration-id=...
1
spring:
cloud:
config:
server:
credhub:
oauth2:
registration-id: "..."
1
java -Dspring.cloud.config.server.credhub.oauth2.registration-id="..." -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_CONFIG_SERVER_CREDHUB_OAUTH2_REGISTRATION_ID="..."
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.config.server.credhub.oauth2.registration-id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.credhub.order=
org.springframework.cloud.config.server.environment.CredhubEnvironmentProperties.
CAS Property: spring.cloud.config.server.credhub.order
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.config.server.credhub.order=...
1
spring:
cloud:
config:
server:
credhub:
order: "..."
1
java -Dspring.cloud.config.server.credhub.order="..." -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_CONFIG_SERVER_CREDHUB_ORDER="..."
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.config.server.credhub.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.credhub.read-timeout=
org.springframework.credhub.support.ClientOptions.
CAS Property: spring.cloud.config.server.credhub.read-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.config.server.credhub.read-timeout=...
1
spring:
cloud:
config:
server:
credhub:
read-timeout: "..."
1
java -Dspring.cloud.config.server.credhub.read-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_CONFIG_SERVER_CREDHUB_READ_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.config.server.credhub.read-timeout="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.credhub.url=
org.springframework.credhub.core.CredHubProperties.
CAS Property: spring.cloud.config.server.credhub.url
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.config.server.credhub.url=...
1
spring:
cloud:
config:
server:
credhub:
url: "..."
1
java -Dspring.cloud.config.server.credhub.url="..." -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_CONFIG_SERVER_CREDHUB_URL="..."
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.config.server.credhub.url="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.default-application-name=application
Default application name when incoming requests do not have a specific one.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.default-application-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.config.server.default-application-name=application
1
spring:
cloud:
config:
server:
default-application-name: "application"
1
java -Dspring.cloud.config.server.default-application-name="application" -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_CONFIG_SERVER_DEFAULT_APPLICATION_NAME="application"
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.config.server.default-application-name="application"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.default-label=
Default repository label when incoming requests do not have a specific label.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.default-label
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.config.server.default-label=...
1
spring:
cloud:
config:
server:
default-label: "..."
1
java -Dspring.cloud.config.server.default-label="..." -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_CONFIG_SERVER_DEFAULT_LABEL="..."
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.config.server.default-label="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.default-profile=default
Default application profile when incoming requests do not have a specific one.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.default-profile
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.config.server.default-profile=default
1
spring:
cloud:
config:
server:
default-profile: "default"
1
java -Dspring.cloud.config.server.default-profile="default" -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_CONFIG_SERVER_DEFAULT_PROFILE="default"
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.config.server.default-profile="default"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.enabled=true
Flag indicating config server is enabled.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.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.config.server.enabled=true
1
spring:
cloud:
config:
server:
enabled: "true"
1
java -Dspring.cloud.config.server.enabled="true" -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_CONFIG_SERVER_ENABLED="true"
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.config.server.enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.encrypt.enabled=true
Enable decryption of environment properties before sending to client.
org.springframework.cloud.config.server.config.ConfigServerProperties$Encrypt.
CAS Property: spring.cloud.config.server.encrypt.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.config.server.encrypt.enabled=true
1
spring:
cloud:
config:
server:
encrypt:
enabled: "true"
1
java -Dspring.cloud.config.server.encrypt.enabled="true" -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_CONFIG_SERVER_ENCRYPT_ENABLED="true"
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.config.server.encrypt.enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.encrypt.plain-text-encrypt=false
Enable decryption of environment properties served by plain text endpoint org.springframework.cloud.config.server.resource.ResourceController
.
org.springframework.cloud.config.server.config.ConfigServerProperties$Encrypt.
CAS Property: spring.cloud.config.server.encrypt.plain-text-encrypt
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.config.server.encrypt.plain-text-encrypt=...
1
spring:
cloud:
config:
server:
encrypt:
plain-text-encrypt: "..."
1
java -Dspring.cloud.config.server.encrypt.plain-text-encrypt="..." -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_CONFIG_SERVER_ENCRYPT_PLAIN_TEXT_ENCRYPT="..."
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.config.server.encrypt.plain-text-encrypt="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.fail-on-composite-error=true
Flag indicating that if there are any errors reading properties from a subordinate environment repository in a composite environment repository, then the entire composite read should fail. Useful when set to false when a Vault repository is in the composite to allow clients to still read properties from other repositories without providing a valid Vault token. Defaults to true, resulting in a failure on any error.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.fail-on-composite-error
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.config.server.fail-on-composite-error=true
1
spring:
cloud:
config:
server:
fail-on-composite-error: "true"
1
java -Dspring.cloud.config.server.fail-on-composite-error="true" -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_CONFIG_SERVER_FAIL_ON_COMPOSITE_ERROR="true"
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.config.server.fail-on-composite-error="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.gcp-secret-manager.application-label=application
org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.gcp-secret-manager.application-label
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.config.server.gcp-secret-manager.application-label=application
1
spring:
cloud:
config:
server:
gcp-secret-manager:
application-label: "application"
1
java -Dspring.cloud.config.server.gcp-secret-manager.application-label="application" -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_CONFIG_SERVER_GCP_SECRET_MANAGER_APPLICATION_LABEL="application"
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.config.server.gcp-secret-manager.application-label="application"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.gcp-secret-manager.order=
org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.gcp-secret-manager.order
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.config.server.gcp-secret-manager.order=...
1
spring:
cloud:
config:
server:
gcp-secret-manager:
order: "..."
1
java -Dspring.cloud.config.server.gcp-secret-manager.order="..." -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_CONFIG_SERVER_GCP_SECRET_MANAGER_ORDER="..."
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.config.server.gcp-secret-manager.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.gcp-secret-manager.profile-label=profile
org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.gcp-secret-manager.profile-label
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.config.server.gcp-secret-manager.profile-label=profile
1
spring:
cloud:
config:
server:
gcp-secret-manager:
profile-label: "profile"
1
java -Dspring.cloud.config.server.gcp-secret-manager.profile-label="profile" -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_CONFIG_SERVER_GCP_SECRET_MANAGER_PROFILE_LABEL="profile"
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.config.server.gcp-secret-manager.profile-label="profile"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.gcp-secret-manager.service-account=
org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.gcp-secret-manager.service-account
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.config.server.gcp-secret-manager.service-account=...
1
spring:
cloud:
config:
server:
gcp-secret-manager:
service-account: "..."
1
java -Dspring.cloud.config.server.gcp-secret-manager.service-account="..." -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_CONFIG_SERVER_GCP_SECRET_MANAGER_SERVICE_ACCOUNT="..."
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.config.server.gcp-secret-manager.service-account="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.gcp-secret-manager.token-mandatory=true
org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.gcp-secret-manager.token-mandatory
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.config.server.gcp-secret-manager.token-mandatory=true
1
spring:
cloud:
config:
server:
gcp-secret-manager:
token-mandatory: "true"
1
java -Dspring.cloud.config.server.gcp-secret-manager.token-mandatory="true" -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_CONFIG_SERVER_GCP_SECRET_MANAGER_TOKEN_MANDATORY="true"
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.config.server.gcp-secret-manager.token-mandatory="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.gcp-secret-manager.version=1
org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.
CAS Property: spring.cloud.config.server.gcp-secret-manager.version
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.config.server.gcp-secret-manager.version=1
1
spring:
cloud:
config:
server:
gcp-secret-manager:
version: "1"
1
java -Dspring.cloud.config.server.gcp-secret-manager.version="1" -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_CONFIG_SERVER_GCP_SECRET_MANAGER_VERSION="1"
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.config.server.gcp-secret-manager.version="1"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.basedir=
Base directory for local working copy of repository.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.basedir
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.config.server.git.basedir=...
1
spring:
cloud:
config:
server:
git:
basedir: "..."
1
java -Dspring.cloud.config.server.git.basedir="..." -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_CONFIG_SERVER_GIT_BASEDIR="..."
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.config.server.git.basedir="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.clone-on-start=false
Flag to indicate that the repository should be cloned on startup (not on demand). Generally leads to slower startup but faster first query.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.clone-on-start
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.config.server.git.clone-on-start=...
1
spring:
cloud:
config:
server:
git:
clone-on-start: "..."
1
java -Dspring.cloud.config.server.git.clone-on-start="..." -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_CONFIG_SERVER_GIT_CLONE_ON_START="..."
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.config.server.git.clone-on-start="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.clone-submodules=false
Flag to indicate that the submodules in the repository should be cloned.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.clone-submodules
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.config.server.git.clone-submodules=...
1
spring:
cloud:
config:
server:
git:
clone-submodules: "..."
1
java -Dspring.cloud.config.server.git.clone-submodules="..." -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_CONFIG_SERVER_GIT_CLONE_SUBMODULES="..."
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.config.server.git.clone-submodules="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.default-label=
The default label to be used with the remote repository.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.default-label
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.config.server.git.default-label=...
1
spring:
cloud:
config:
server:
git:
default-label: "..."
1
java -Dspring.cloud.config.server.git.default-label="..." -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_CONFIG_SERVER_GIT_DEFAULT_LABEL="..."
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.config.server.git.default-label="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.delete-untracked-branches=false
Flag to indicate that the branch should be deleted locally if it's origin tracked branch was removed.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.delete-untracked-branches
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.config.server.git.delete-untracked-branches=...
1
spring:
cloud:
config:
server:
git:
delete-untracked-branches: "..."
1
java -Dspring.cloud.config.server.git.delete-untracked-branches="..." -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_CONFIG_SERVER_GIT_DELETE_UNTRACKED_BRANCHES="..."
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.config.server.git.delete-untracked-branches="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.force-pull=false
Flag to indicate that the repository should force pull. If true discard any local changes and take from remote repository.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.force-pull
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.config.server.git.force-pull=...
1
spring:
cloud:
config:
server:
git:
force-pull: "..."
1
java -Dspring.cloud.config.server.git.force-pull="..." -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_CONFIG_SERVER_GIT_FORCE_PULL="..."
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.config.server.git.force-pull="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.host-key=
Valid SSH host key. Must be set if hostKeyAlgorithm is also set.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.host-key
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.config.server.git.host-key=...
1
spring:
cloud:
config:
server:
git:
host-key: "..."
1
java -Dspring.cloud.config.server.git.host-key="..." -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_CONFIG_SERVER_GIT_HOST_KEY="..."
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.config.server.git.host-key="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.host-key-algorithm=
One of ssh-dss, ssh-rsa, ssh-ed25519, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, or ecdsa-sha2-nistp521. Must be set if hostKey is also set.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.host-key-algorithm
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.config.server.git.host-key-algorithm=...
1
spring:
cloud:
config:
server:
git:
host-key-algorithm: "..."
1
java -Dspring.cloud.config.server.git.host-key-algorithm="..." -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_CONFIG_SERVER_GIT_HOST_KEY_ALGORITHM="..."
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.config.server.git.host-key-algorithm="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.ignore-local-ssh-settings=false
If true, use property-based instead of file-based SSH config.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.ignore-local-ssh-settings
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.config.server.git.ignore-local-ssh-settings=...
1
spring:
cloud:
config:
server:
git:
ignore-local-ssh-settings: "..."
1
java -Dspring.cloud.config.server.git.ignore-local-ssh-settings="..." -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_CONFIG_SERVER_GIT_IGNORE_LOCAL_SSH_SETTINGS="..."
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.config.server.git.ignore-local-ssh-settings="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.known-hosts-file=
Location of custom .known_hosts file.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.known-hosts-file
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.config.server.git.known-hosts-file=...
1
spring:
cloud:
config:
server:
git:
known-hosts-file: "..."
1
java -Dspring.cloud.config.server.git.known-hosts-file="..." -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_CONFIG_SERVER_GIT_KNOWN_HOSTS_FILE="..."
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.config.server.git.known-hosts-file="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.order=
The order of the environment repository.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.order
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.config.server.git.order=...
1
spring:
cloud:
config:
server:
git:
order: "..."
1
java -Dspring.cloud.config.server.git.order="..." -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_CONFIG_SERVER_GIT_ORDER="..."
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.config.server.git.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.passphrase=
Passphrase for unlocking your ssh private key.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.passphrase
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.config.server.git.passphrase=...
1
spring:
cloud:
config:
server:
git:
passphrase: "..."
1
java -Dspring.cloud.config.server.git.passphrase="..." -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_CONFIG_SERVER_GIT_PASSPHRASE="..."
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.config.server.git.passphrase="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.password=
Password for authentication with remote repository.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.password
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.config.server.git.password=...
1
spring:
cloud:
config:
server:
git:
password: "..."
1
java -Dspring.cloud.config.server.git.password="..." -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_CONFIG_SERVER_GIT_PASSWORD="..."
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.config.server.git.password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.preferred-authentications=
Override server authentication method order. This should allow for evading login prompts if server has keyboard-interactive authentication before the publickey method.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.preferred-authentications
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.config.server.git.preferred-authentications=...
1
spring:
cloud:
config:
server:
git:
preferred-authentications: "..."
1
java -Dspring.cloud.config.server.git.preferred-authentications="..." -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_CONFIG_SERVER_GIT_PREFERRED_AUTHENTICATIONS="..."
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.config.server.git.preferred-authentications="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.private-key=
Valid SSH private key. Must be set if ignoreLocalSshSettings is true and Git URI is SSH format.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.private-key
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.config.server.git.private-key=...
1
spring:
cloud:
config:
server:
git:
private-key: "..."
1
java -Dspring.cloud.config.server.git.private-key="..." -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_CONFIG_SERVER_GIT_PRIVATE_KEY="..."
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.config.server.git.private-key="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.proxy=
HTTP proxy configuration.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.proxy
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.config.server.git.proxy=...
1
spring:
cloud:
config:
server:
git:
proxy: "..."
1
java -Dspring.cloud.config.server.git.proxy="..." -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_CONFIG_SERVER_GIT_PROXY="..."
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.config.server.git.proxy="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.refresh-rate=0
Time (in seconds) between refresh of the git repository.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.refresh-rate
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.config.server.git.refresh-rate=0
1
spring:
cloud:
config:
server:
git:
refresh-rate: "0"
1
java -Dspring.cloud.config.server.git.refresh-rate="0" -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_CONFIG_SERVER_GIT_REFRESH_RATE="0"
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.config.server.git.refresh-rate="0"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.repos=
Map of repository identifier to location and other properties.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.repos
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.config.server.git.repos=...
1
spring:
cloud:
config:
server:
git:
repos: "..."
1
java -Dspring.cloud.config.server.git.repos="..." -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_CONFIG_SERVER_GIT_REPOS="..."
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.config.server.git.repos="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.search-paths=
Search paths to use within local working copy. By default searches only the root.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.search-paths
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.config.server.git.search-paths=...
1
spring:
cloud:
config:
server:
git:
search-paths: "..."
1
java -Dspring.cloud.config.server.git.search-paths="..." -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_CONFIG_SERVER_GIT_SEARCH_PATHS="..."
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.config.server.git.search-paths="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.skip-ssl-validation=false
Flag to indicate that SSL certificate validation should be bypassed when communicating with a repository served over an HTTPS connection.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.skip-ssl-validation
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.config.server.git.skip-ssl-validation=...
1
spring:
cloud:
config:
server:
git:
skip-ssl-validation: "..."
1
java -Dspring.cloud.config.server.git.skip-ssl-validation="..." -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_CONFIG_SERVER_GIT_SKIP_SSL_VALIDATION="..."
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.config.server.git.skip-ssl-validation="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.strict-host-key-checking=true
If false, ignore errors with host key.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.strict-host-key-checking
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.config.server.git.strict-host-key-checking=true
1
spring:
cloud:
config:
server:
git:
strict-host-key-checking: "true"
1
java -Dspring.cloud.config.server.git.strict-host-key-checking="true" -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_CONFIG_SERVER_GIT_STRICT_HOST_KEY_CHECKING="true"
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.config.server.git.strict-host-key-checking="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.timeout=5
Timeout (in seconds) for obtaining HTTP or SSH connection (if applicable), defaults to 5 seconds.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.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.config.server.git.timeout=5
1
spring:
cloud:
config:
server:
git:
timeout: "5"
1
java -Dspring.cloud.config.server.git.timeout="5" -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_CONFIG_SERVER_GIT_TIMEOUT="5"
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.config.server.git.timeout="5"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.try-master-branch=true
To maintain compatibility we will try the master branch in addition to main when we try to fetch the default branch.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.try-master-branch
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.config.server.git.try-master-branch=true
1
spring:
cloud:
config:
server:
git:
try-master-branch: "true"
1
java -Dspring.cloud.config.server.git.try-master-branch="true" -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_CONFIG_SERVER_GIT_TRY_MASTER_BRANCH="true"
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.config.server.git.try-master-branch="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.uri=
URI of remote repository.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.uri
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.config.server.git.uri=...
1
spring:
cloud:
config:
server:
git:
uri: "..."
1
java -Dspring.cloud.config.server.git.uri="..." -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_CONFIG_SERVER_GIT_URI="..."
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.config.server.git.uri="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.git.username=
Username for authentication with remote repository.
org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.
CAS Property: spring.cloud.config.server.git.username
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.config.server.git.username=...
1
spring:
cloud:
config:
server:
git:
username: "..."
1
java -Dspring.cloud.config.server.git.username="..." -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_CONFIG_SERVER_GIT_USERNAME="..."
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.config.server.git.username="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.health.down-health-status=
org.springframework.cloud.config.server.config.ConfigServerHealthIndicator.
CAS Property: spring.cloud.config.server.health.down-health-status
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.config.server.health.down-health-status=...
1
spring:
cloud:
config:
server:
health:
down-health-status: "..."
1
java -Dspring.cloud.config.server.health.down-health-status="..." -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_CONFIG_SERVER_HEALTH_DOWN_HEALTH_STATUS="..."
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.config.server.health.down-health-status="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.health.repositories=
org.springframework.cloud.config.server.config.ConfigServerHealthIndicator.
CAS Property: spring.cloud.config.server.health.repositories
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.config.server.health.repositories=...
1
spring:
cloud:
config:
server:
health:
repositories: "..."
1
java -Dspring.cloud.config.server.health.repositories="..." -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_CONFIG_SERVER_HEALTH_REPOSITORIES="..."
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.config.server.health.repositories="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.jdbc.default-label=master
org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.
CAS Property: spring.cloud.config.server.jdbc.default-label
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.config.server.jdbc.default-label=master
1
spring:
cloud:
config:
server:
jdbc:
default-label: "master"
1
java -Dspring.cloud.config.server.jdbc.default-label="master" -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_CONFIG_SERVER_JDBC_DEFAULT_LABEL="master"
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.config.server.jdbc.default-label="master"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.jdbc.enabled=true
Flag to indicate that JDBC environment repository configuration is enabled.
org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.
CAS Property: spring.cloud.config.server.jdbc.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.config.server.jdbc.enabled=true
1
spring:
cloud:
config:
server:
jdbc:
enabled: "true"
1
java -Dspring.cloud.config.server.jdbc.enabled="true" -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_CONFIG_SERVER_JDBC_ENABLED="true"
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.config.server.jdbc.enabled="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.jdbc.fail-on-error=true
Flag to determine how to handle query exceptions.
org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.
CAS Property: spring.cloud.config.server.jdbc.fail-on-error
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.config.server.jdbc.fail-on-error=true
1
spring:
cloud:
config:
server:
jdbc:
fail-on-error: "true"
1
java -Dspring.cloud.config.server.jdbc.fail-on-error="true" -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_CONFIG_SERVER_JDBC_FAIL_ON_ERROR="true"
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.config.server.jdbc.fail-on-error="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.jdbc.order=0
org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.
CAS Property: spring.cloud.config.server.jdbc.order
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.config.server.jdbc.order=0
1
spring:
cloud:
config:
server:
jdbc:
order: "0"
1
java -Dspring.cloud.config.server.jdbc.order="0" -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_CONFIG_SERVER_JDBC_ORDER="0"
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.config.server.jdbc.order="0"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.jdbc.sql=SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?
SQL used to query database for keys and values.
org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.
CAS Property: spring.cloud.config.server.jdbc.sql
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.config.server.jdbc.sql=SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?
1
spring:
cloud:
config:
server:
jdbc:
sql: "SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?"
1
java -Dspring.cloud.config.server.jdbc.sql="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?" -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_CONFIG_SERVER_JDBC_SQL="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?"
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.config.server.jdbc.sql="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.jdbc.sql-without-profile=SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?
SQL used to query database for keys and values when profile is null.
org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.
CAS Property: spring.cloud.config.server.jdbc.sql-without-profile
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.config.server.jdbc.sql-without-profile=SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?
1
spring:
cloud:
config:
server:
jdbc:
sql-without-profile: "SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?"
1
java -Dspring.cloud.config.server.jdbc.sql-without-profile="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?" -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_CONFIG_SERVER_JDBC_SQL_WITHOUT_PROFILE="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?"
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.config.server.jdbc.sql-without-profile="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.native.add-label-locations=true
Flag to determine whether label locations should be added.
org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.
CAS Property: spring.cloud.config.server.native.add-label-locations
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.config.server.native.add-label-locations=true
1
spring:
cloud:
config:
server:
native:
add-label-locations: "true"
1
java -Dspring.cloud.config.server.native.add-label-locations="true" -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_CONFIG_SERVER_NATIVE_ADD_LABEL_LOCATIONS="true"
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.config.server.native.add-label-locations="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.native.default-label=master
org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.
CAS Property: spring.cloud.config.server.native.default-label
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.config.server.native.default-label=master
1
spring:
cloud:
config:
server:
native:
default-label: "master"
1
java -Dspring.cloud.config.server.native.default-label="master" -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_CONFIG_SERVER_NATIVE_DEFAULT_LABEL="master"
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.config.server.native.default-label="master"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.native.fail-on-error=false
Flag to determine how to handle exceptions during decryption (default false).
org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.
CAS Property: spring.cloud.config.server.native.fail-on-error
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.config.server.native.fail-on-error=...
1
spring:
cloud:
config:
server:
native:
fail-on-error: "..."
1
java -Dspring.cloud.config.server.native.fail-on-error="..." -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_CONFIG_SERVER_NATIVE_FAIL_ON_ERROR="..."
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.config.server.native.fail-on-error="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.native.order=
org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.
CAS Property: spring.cloud.config.server.native.order
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.config.server.native.order=...
1
spring:
cloud:
config:
server:
native:
order: "..."
1
java -Dspring.cloud.config.server.native.order="..." -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_CONFIG_SERVER_NATIVE_ORDER="..."
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.config.server.native.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.native.search-locations=
Locations to search for configuration files. Defaults to the same as a Spring Boot app so [classpath:/,classpath:/config/,file:./,file:./config/].
org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.
CAS Property: spring.cloud.config.server.native.search-locations
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.config.server.native.search-locations=...
1
spring:
cloud:
config:
server:
native:
search-locations: "..."
1
java -Dspring.cloud.config.server.native.search-locations="..." -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_CONFIG_SERVER_NATIVE_SEARCH_LOCATIONS="..."
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.config.server.native.search-locations="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.native.version=
Version string to be reported for native repository.
org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.
CAS Property: spring.cloud.config.server.native.version
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.config.server.native.version=...
1
spring:
cloud:
config:
server:
native:
version: "..."
1
java -Dspring.cloud.config.server.native.version="..." -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_CONFIG_SERVER_NATIVE_VERSION="..."
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.config.server.native.version="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.overrides=
Extra map for a property source to be sent to all clients unconditionally.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.overrides
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.config.server.overrides=...
1
spring:
cloud:
config:
server:
overrides: "..."
1
java -Dspring.cloud.config.server.overrides="..." -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_CONFIG_SERVER_OVERRIDES="..."
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.config.server.overrides="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.prefix=
Prefix for configuration resource paths (default is empty). Useful when embedding in another application when you don't want to change the context path or servlet path.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.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.config.server.prefix=...
1
spring:
cloud:
config:
server:
prefix: "..."
1
java -Dspring.cloud.config.server.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_CONFIG_SERVER_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.config.server.prefix="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.redis.order=
org.springframework.cloud.config.server.environment.RedisEnvironmentProperties.
CAS Property: spring.cloud.config.server.redis.order
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.config.server.redis.order=...
1
spring:
cloud:
config:
server:
redis:
order: "..."
1
java -Dspring.cloud.config.server.redis.order="..." -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_CONFIG_SERVER_REDIS_ORDER="..."
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.config.server.redis.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.reverse-location-order=false
By default the location order we use in GenericResourceRepository is the order in which they are listed. Prior to Hoxton.SR11 the order used to be reverse. If this property is set to true then we will reverse ther order like it used to be prior to Hoxton.SR11.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.reverse-location-order
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.config.server.reverse-location-order=...
1
spring:
cloud:
config:
server:
reverse-location-order: "..."
1
java -Dspring.cloud.config.server.reverse-location-order="..." -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_CONFIG_SERVER_REVERSE_LOCATION_ORDER="..."
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.config.server.reverse-location-order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.strip-document-from-yaml=true
Flag to indicate that YAML documents that are text or collections (not a map) should be returned in "native" form.
org.springframework.cloud.config.server.config.ConfigServerProperties.
CAS Property: spring.cloud.config.server.strip-document-from-yaml
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.config.server.strip-document-from-yaml=true
1
spring:
cloud:
config:
server:
strip-document-from-yaml: "true"
1
java -Dspring.cloud.config.server.strip-document-from-yaml="true" -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_CONFIG_SERVER_STRIP_DOCUMENT_FROM_YAML="true"
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.config.server.strip-document-from-yaml="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.basedir=
Base directory for local working copy of repository.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.basedir
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.config.server.svn.basedir=...
1
spring:
cloud:
config:
server:
svn:
basedir: "..."
1
java -Dspring.cloud.config.server.svn.basedir="..." -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_CONFIG_SERVER_SVN_BASEDIR="..."
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.config.server.svn.basedir="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.default-label=
The default label to be used with the remote repository.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.default-label
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.config.server.svn.default-label=...
1
spring:
cloud:
config:
server:
svn:
default-label: "..."
1
java -Dspring.cloud.config.server.svn.default-label="..." -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_CONFIG_SERVER_SVN_DEFAULT_LABEL="..."
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.config.server.svn.default-label="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.order=
The order of the environment repository.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.order
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.config.server.svn.order=...
1
spring:
cloud:
config:
server:
svn:
order: "..."
1
java -Dspring.cloud.config.server.svn.order="..." -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_CONFIG_SERVER_SVN_ORDER="..."
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.config.server.svn.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.passphrase=
Passphrase for unlocking your ssh private key.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.passphrase
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.config.server.svn.passphrase=...
1
spring:
cloud:
config:
server:
svn:
passphrase: "..."
1
java -Dspring.cloud.config.server.svn.passphrase="..." -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_CONFIG_SERVER_SVN_PASSPHRASE="..."
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.config.server.svn.passphrase="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.password=
Password for authentication with remote repository.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.password
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.config.server.svn.password=...
1
spring:
cloud:
config:
server:
svn:
password: "..."
1
java -Dspring.cloud.config.server.svn.password="..." -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_CONFIG_SERVER_SVN_PASSWORD="..."
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.config.server.svn.password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.search-paths=
Search paths to use within local working copy. By default searches only the root.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.search-paths
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.config.server.svn.search-paths=...
1
spring:
cloud:
config:
server:
svn:
search-paths: "..."
1
java -Dspring.cloud.config.server.svn.search-paths="..." -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_CONFIG_SERVER_SVN_SEARCH_PATHS="..."
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.config.server.svn.search-paths="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.strict-host-key-checking=true
Reject incoming SSH host keys from remote servers not in the known host list.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.strict-host-key-checking
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.config.server.svn.strict-host-key-checking=true
1
spring:
cloud:
config:
server:
svn:
strict-host-key-checking: "true"
1
java -Dspring.cloud.config.server.svn.strict-host-key-checking="true" -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_CONFIG_SERVER_SVN_STRICT_HOST_KEY_CHECKING="true"
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.config.server.svn.strict-host-key-checking="true"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.uri=
URI of remote repository.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.uri
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.config.server.svn.uri=...
1
spring:
cloud:
config:
server:
svn:
uri: "..."
1
java -Dspring.cloud.config.server.svn.uri="..." -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_CONFIG_SERVER_SVN_URI="..."
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.config.server.svn.uri="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.svn.username=
Username for authentication with remote repository.
org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.
CAS Property: spring.cloud.config.server.svn.username
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.config.server.svn.username=...
1
spring:
cloud:
config:
server:
svn:
username: "..."
1
java -Dspring.cloud.config.server.svn.username="..." -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_CONFIG_SERVER_SVN_USERNAME="..."
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.config.server.svn.username="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.app-role.app-role-path=approle
Mount path of the AppRole authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AppRoleProperties.
CAS Property: spring.cloud.config.server.vault.app-role.app-role-path
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.config.server.vault.app-role.app-role-path=approle
1
spring:
cloud:
config:
server:
vault:
app-role:
app-role-path: "approle"
1
java -Dspring.cloud.config.server.vault.app-role.app-role-path="approle" -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_CONFIG_SERVER_VAULT_APP_ROLE_APP_ROLE_PATH="approle"
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.config.server.vault.app-role.app-role-path="approle"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.app-role.role=
Name of the role, optional, used for pull-mode.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AppRoleProperties.
CAS Property: spring.cloud.config.server.vault.app-role.role
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.config.server.vault.app-role.role=...
1
spring:
cloud:
config:
server:
vault:
app-role:
role: "..."
1
java -Dspring.cloud.config.server.vault.app-role.role="..." -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_CONFIG_SERVER_VAULT_APP_ROLE_ROLE="..."
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.config.server.vault.app-role.role="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.app-role.role-id=
The RoleId.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AppRoleProperties.
CAS Property: spring.cloud.config.server.vault.app-role.role-id
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.config.server.vault.app-role.role-id=...
1
spring:
cloud:
config:
server:
vault:
app-role:
role-id: "..."
1
java -Dspring.cloud.config.server.vault.app-role.role-id="..." -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_CONFIG_SERVER_VAULT_APP_ROLE_ROLE_ID="..."
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.config.server.vault.app-role.role-id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.app-role.secret-id=
The SecretId.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AppRoleProperties.
CAS Property: spring.cloud.config.server.vault.app-role.secret-id
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.config.server.vault.app-role.secret-id=...
1
spring:
cloud:
config:
server:
vault:
app-role:
secret-id: "..."
1
java -Dspring.cloud.config.server.vault.app-role.secret-id="..." -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_CONFIG_SERVER_VAULT_APP_ROLE_SECRET_ID="..."
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.config.server.vault.app-role.secret-id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.authentication=
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.authentication
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.config.server.vault.authentication=...
1
spring:
cloud:
config:
server:
vault:
authentication: "..."
1
java -Dspring.cloud.config.server.vault.authentication="..." -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_CONFIG_SERVER_VAULT_AUTHENTICATION="..."
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.config.server.vault.authentication="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.aws-ec2.aws-ec2-path=aws-ec2
Mount path of the AWS-EC2 authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsEc2Properties.
CAS Property: spring.cloud.config.server.vault.aws-ec2.aws-ec2-path
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.config.server.vault.aws-ec2.aws-ec2-path=aws-ec2
1
spring:
cloud:
config:
server:
vault:
aws-ec2:
aws-ec2-path: "aws-ec2"
1
java -Dspring.cloud.config.server.vault.aws-ec2.aws-ec2-path="aws-ec2" -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_CONFIG_SERVER_VAULT_AWS_EC2_AWS_EC2_PATH="aws-ec2"
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.config.server.vault.aws-ec2.aws-ec2-path="aws-ec2"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.aws-ec2.identity-document=http://169.254.169.254/latest/dynamic/instance-identity/pkcs7
URL of the AWS-EC2 PKCS7 identity document.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsEc2Properties.
CAS Property: spring.cloud.config.server.vault.aws-ec2.identity-document
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.config.server.vault.aws-ec2.identity-document=http://169.254.169.254/latest/dynamic/instance-identity/pkcs7
1
spring:
cloud:
config:
server:
vault:
aws-ec2:
identity-document: "http://169.254.169.254/latest/dynamic/instance-identity/pkcs7"
1
java -Dspring.cloud.config.server.vault.aws-ec2.identity-document="http://169.254.169.254/latest/dynamic/instance-identity/pkcs7" -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_CONFIG_SERVER_VAULT_AWS_EC2_IDENTITY_DOCUMENT="http://169.254.169.254/latest/dynamic/instance-identity/pkcs7"
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.config.server.vault.aws-ec2.identity-document="http://169.254.169.254/latest/dynamic/instance-identity/pkcs7"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.aws-ec2.nonce=
Nonce used for AWS-EC2 authentication. An empty nonce defaults to nonce generation.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsEc2Properties.
CAS Property: spring.cloud.config.server.vault.aws-ec2.nonce
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.config.server.vault.aws-ec2.nonce=...
1
spring:
cloud:
config:
server:
vault:
aws-ec2:
nonce: "..."
1
java -Dspring.cloud.config.server.vault.aws-ec2.nonce="..." -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_CONFIG_SERVER_VAULT_AWS_EC2_NONCE="..."
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.config.server.vault.aws-ec2.nonce="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.aws-ec2.role=
Name of the role, optional.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsEc2Properties.
CAS Property: spring.cloud.config.server.vault.aws-ec2.role
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.config.server.vault.aws-ec2.role=...
1
spring:
cloud:
config:
server:
vault:
aws-ec2:
role: "..."
1
java -Dspring.cloud.config.server.vault.aws-ec2.role="..." -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_CONFIG_SERVER_VAULT_AWS_EC2_ROLE="..."
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.config.server.vault.aws-ec2.role="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.aws-iam.aws-path=aws
Mount path of the AWS authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsIamProperties.
CAS Property: spring.cloud.config.server.vault.aws-iam.aws-path
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.config.server.vault.aws-iam.aws-path=aws
1
spring:
cloud:
config:
server:
vault:
aws-iam:
aws-path: "aws"
1
java -Dspring.cloud.config.server.vault.aws-iam.aws-path="aws" -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_CONFIG_SERVER_VAULT_AWS_IAM_AWS_PATH="aws"
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.config.server.vault.aws-iam.aws-path="aws"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.aws-iam.endpoint-uri=
STS server URI. @since 2.2
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsIamProperties.
CAS Property: spring.cloud.config.server.vault.aws-iam.endpoint-uri
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.config.server.vault.aws-iam.endpoint-uri=...
1
spring:
cloud:
config:
server:
vault:
aws-iam:
endpoint-uri: "..."
1
java -Dspring.cloud.config.server.vault.aws-iam.endpoint-uri="..." -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_CONFIG_SERVER_VAULT_AWS_IAM_ENDPOINT_URI="..."
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.config.server.vault.aws-iam.endpoint-uri="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.aws-iam.role=
Name of the role, optional. Defaults to the friendly IAM name if not set.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsIamProperties.
CAS Property: spring.cloud.config.server.vault.aws-iam.role
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.config.server.vault.aws-iam.role=...
1
spring:
cloud:
config:
server:
vault:
aws-iam:
role: "..."
1
java -Dspring.cloud.config.server.vault.aws-iam.role="..." -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_CONFIG_SERVER_VAULT_AWS_IAM_ROLE="..."
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.config.server.vault.aws-iam.role="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.aws-iam.server-name=
Name of the server used to set X-Vault-AWS-IAM-Server-ID
header in the headers of login requests.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsIamProperties.
CAS Property: spring.cloud.config.server.vault.aws-iam.server-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.config.server.vault.aws-iam.server-name=...
1
spring:
cloud:
config:
server:
vault:
aws-iam:
server-name: "..."
1
java -Dspring.cloud.config.server.vault.aws-iam.server-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_CONFIG_SERVER_VAULT_AWS_IAM_SERVER_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.config.server.vault.aws-iam.server-name="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.azure-msi.azure-path=azure
Mount path of the Azure MSI authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AzureMsiProperties.
CAS Property: spring.cloud.config.server.vault.azure-msi.azure-path
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.config.server.vault.azure-msi.azure-path=azure
1
spring:
cloud:
config:
server:
vault:
azure-msi:
azure-path: "azure"
1
java -Dspring.cloud.config.server.vault.azure-msi.azure-path="azure" -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_CONFIG_SERVER_VAULT_AZURE_MSI_AZURE_PATH="azure"
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.config.server.vault.azure-msi.azure-path="azure"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.azure-msi.identity-token-service=
URI to the Azure MSI Identity Service.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AzureMsiProperties.
CAS Property: spring.cloud.config.server.vault.azure-msi.identity-token-service
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.config.server.vault.azure-msi.identity-token-service=...
1
spring:
cloud:
config:
server:
vault:
azure-msi:
identity-token-service: "..."
1
java -Dspring.cloud.config.server.vault.azure-msi.identity-token-service="..." -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_CONFIG_SERVER_VAULT_AZURE_MSI_IDENTITY_TOKEN_SERVICE="..."
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.config.server.vault.azure-msi.identity-token-service="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.azure-msi.metadata-service=
URI to the Azure MSI Metadata Service.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AzureMsiProperties.
CAS Property: spring.cloud.config.server.vault.azure-msi.metadata-service
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.config.server.vault.azure-msi.metadata-service=...
1
spring:
cloud:
config:
server:
vault:
azure-msi:
metadata-service: "..."
1
java -Dspring.cloud.config.server.vault.azure-msi.metadata-service="..." -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_CONFIG_SERVER_VAULT_AZURE_MSI_METADATA_SERVICE="..."
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.config.server.vault.azure-msi.metadata-service="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.azure-msi.role=
Name of the role.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AzureMsiProperties.
CAS Property: spring.cloud.config.server.vault.azure-msi.role
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.config.server.vault.azure-msi.role=...
1
spring:
cloud:
config:
server:
vault:
azure-msi:
role: "..."
1
java -Dspring.cloud.config.server.vault.azure-msi.role="..." -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_CONFIG_SERVER_VAULT_AZURE_MSI_ROLE="..."
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.config.server.vault.azure-msi.role="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.backend=secret
Vault backend. Defaults to secret.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.backend
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.config.server.vault.backend=secret
1
spring:
cloud:
config:
server:
vault:
backend: "secret"
1
java -Dspring.cloud.config.server.vault.backend="secret" -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_CONFIG_SERVER_VAULT_BACKEND="secret"
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.config.server.vault.backend="secret"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.default-key=application
The key in vault shared by all applications. Defaults to application. Set to empty to disable.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.default-key
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.config.server.vault.default-key=application
1
spring:
cloud:
config:
server:
vault:
default-key: "application"
1
java -Dspring.cloud.config.server.vault.default-key="application" -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_CONFIG_SERVER_VAULT_DEFAULT_KEY="application"
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.config.server.vault.default-key="application"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-gce.gcp-path=gcp
Mount path of the Kubernetes authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpGceProperties.
CAS Property: spring.cloud.config.server.vault.gcp-gce.gcp-path
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.config.server.vault.gcp-gce.gcp-path=gcp
1
spring:
cloud:
config:
server:
vault:
gcp-gce:
gcp-path: "gcp"
1
java -Dspring.cloud.config.server.vault.gcp-gce.gcp-path="gcp" -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_CONFIG_SERVER_VAULT_GCP_GCE_GCP_PATH="gcp"
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.config.server.vault.gcp-gce.gcp-path="gcp"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-gce.role=
Name of the role against which the login is being attempted.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpGceProperties.
CAS Property: spring.cloud.config.server.vault.gcp-gce.role
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.config.server.vault.gcp-gce.role=...
1
spring:
cloud:
config:
server:
vault:
gcp-gce:
role: "..."
1
java -Dspring.cloud.config.server.vault.gcp-gce.role="..." -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_CONFIG_SERVER_VAULT_GCP_GCE_ROLE="..."
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.config.server.vault.gcp-gce.role="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-gce.service-account=
Optional service account id. Using the default id if left unconfigured.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpGceProperties.
CAS Property: spring.cloud.config.server.vault.gcp-gce.service-account
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.config.server.vault.gcp-gce.service-account=...
1
spring:
cloud:
config:
server:
vault:
gcp-gce:
service-account: "..."
1
java -Dspring.cloud.config.server.vault.gcp-gce.service-account="..." -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_CONFIG_SERVER_VAULT_GCP_GCE_SERVICE_ACCOUNT="..."
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.config.server.vault.gcp-gce.service-account="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-iam.credentials.encoded-key=
The base64 encoded contents of an OAuth2 account private key in JSON format.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpCredentials.
CAS Property: spring.cloud.config.server.vault.gcp-iam.credentials.encoded-key
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.config.server.vault.gcp-iam.credentials.encoded-key=...
1
spring:
cloud:
config:
server:
vault:
gcp-iam:
credentials:
encoded-key: "..."
1
java -Dspring.cloud.config.server.vault.gcp-iam.credentials.encoded-key="..." -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_CONFIG_SERVER_VAULT_GCP_IAM_CREDENTIALS_ENCODED_KEY="..."
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.config.server.vault.gcp-iam.credentials.encoded-key="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-iam.credentials.location=
Location of the OAuth2 credentials private key.
Since this is a Resource, the private key can be in a multitude of locations, such as a local file system, classpath, URL, etc. org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpCredentials.
CAS Property: spring.cloud.config.server.vault.gcp-iam.credentials.location
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.config.server.vault.gcp-iam.credentials.location=...
1
spring:
cloud:
config:
server:
vault:
gcp-iam:
credentials:
location: "..."
1
java -Dspring.cloud.config.server.vault.gcp-iam.credentials.location="..." -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_CONFIG_SERVER_VAULT_GCP_IAM_CREDENTIALS_LOCATION="..."
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.config.server.vault.gcp-iam.credentials.location="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-iam.gcp-path=gcp
Mount path of the Kubernetes authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpIamProperties.
CAS Property: spring.cloud.config.server.vault.gcp-iam.gcp-path
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.config.server.vault.gcp-iam.gcp-path=gcp
1
spring:
cloud:
config:
server:
vault:
gcp-iam:
gcp-path: "gcp"
1
java -Dspring.cloud.config.server.vault.gcp-iam.gcp-path="gcp" -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_CONFIG_SERVER_VAULT_GCP_IAM_GCP_PATH="gcp"
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.config.server.vault.gcp-iam.gcp-path="gcp"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-iam.jwt-validity=15m
Validity of the JWT token.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpIamProperties.
CAS Property: spring.cloud.config.server.vault.gcp-iam.jwt-validity
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.config.server.vault.gcp-iam.jwt-validity=15m
1
spring:
cloud:
config:
server:
vault:
gcp-iam:
jwt-validity: "15m"
1
java -Dspring.cloud.config.server.vault.gcp-iam.jwt-validity="15m" -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_CONFIG_SERVER_VAULT_GCP_IAM_JWT_VALIDITY="15m"
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.config.server.vault.gcp-iam.jwt-validity="15m"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-iam.project-id=
Overrides the GCP project Id.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpIamProperties.
CAS Property: spring.cloud.config.server.vault.gcp-iam.project-id
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.config.server.vault.gcp-iam.project-id=...
1
spring:
cloud:
config:
server:
vault:
gcp-iam:
project-id: "..."
1
java -Dspring.cloud.config.server.vault.gcp-iam.project-id="..." -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_CONFIG_SERVER_VAULT_GCP_IAM_PROJECT_ID="..."
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.config.server.vault.gcp-iam.project-id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-iam.role=
Name of the role against which the login is being attempted.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpIamProperties.
CAS Property: spring.cloud.config.server.vault.gcp-iam.role
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.config.server.vault.gcp-iam.role=...
1
spring:
cloud:
config:
server:
vault:
gcp-iam:
role: "..."
1
java -Dspring.cloud.config.server.vault.gcp-iam.role="..." -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_CONFIG_SERVER_VAULT_GCP_IAM_ROLE="..."
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.config.server.vault.gcp-iam.role="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.gcp-iam.service-account-id=
Overrides the GCP service account Id.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpIamProperties.
CAS Property: spring.cloud.config.server.vault.gcp-iam.service-account-id
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.config.server.vault.gcp-iam.service-account-id=...
1
spring:
cloud:
config:
server:
vault:
gcp-iam:
service-account-id: "..."
1
java -Dspring.cloud.config.server.vault.gcp-iam.service-account-id="..." -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_CONFIG_SERVER_VAULT_GCP_IAM_SERVICE_ACCOUNT_ID="..."
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.config.server.vault.gcp-iam.service-account-id="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.host=127.0.0.1
Vault host. Defaults to 127.0.0.1.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.host
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.config.server.vault.host=127.0.0.1
1
spring:
cloud:
config:
server:
vault:
host: "127.0.0.1"
1
java -Dspring.cloud.config.server.vault.host="127.0.0.1" -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_CONFIG_SERVER_VAULT_HOST="127.0.0.1"
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.config.server.vault.host="127.0.0.1"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.kubernetes.kubernetes-path=kubernetes
Mount path of the Kubernetes authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$KubernetesProperties.
CAS Property: spring.cloud.config.server.vault.kubernetes.kubernetes-path
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.config.server.vault.kubernetes.kubernetes-path=kubernetes
1
spring:
cloud:
config:
server:
vault:
kubernetes:
kubernetes-path: "kubernetes"
1
java -Dspring.cloud.config.server.vault.kubernetes.kubernetes-path="kubernetes" -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_CONFIG_SERVER_VAULT_KUBERNETES_KUBERNETES_PATH="kubernetes"
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.config.server.vault.kubernetes.kubernetes-path="kubernetes"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.kubernetes.role=
Name of the role against which the login is being attempted.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$KubernetesProperties.
CAS Property: spring.cloud.config.server.vault.kubernetes.role
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.config.server.vault.kubernetes.role=...
1
spring:
cloud:
config:
server:
vault:
kubernetes:
role: "..."
1
java -Dspring.cloud.config.server.vault.kubernetes.role="..." -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_CONFIG_SERVER_VAULT_KUBERNETES_ROLE="..."
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.config.server.vault.kubernetes.role="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.kubernetes.service-account-token-file=/var/run/secrets/kubernetes.io/serviceaccount/token
Path to the service account token file.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$KubernetesProperties.
CAS Property: spring.cloud.config.server.vault.kubernetes.service-account-token-file
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.config.server.vault.kubernetes.service-account-token-file=/var/run/secrets/kubernetes.io/serviceaccount/token
1
spring:
cloud:
config:
server:
vault:
kubernetes:
service-account-token-file: "/var/run/secrets/kubernetes.io/serviceaccount/token"
1
java -Dspring.cloud.config.server.vault.kubernetes.service-account-token-file="/var/run/secrets/kubernetes.io/serviceaccount/token" -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_CONFIG_SERVER_VAULT_KUBERNETES_SERVICE_ACCOUNT_TOKEN_FILE="/var/run/secrets/kubernetes.io/serviceaccount/token"
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.config.server.vault.kubernetes.service-account-token-file="/var/run/secrets/kubernetes.io/serviceaccount/token"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.kv-version=1
Value to indicate which version of Vault kv backend is used. Defaults to 1.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.kv-version
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.config.server.vault.kv-version=1
1
spring:
cloud:
config:
server:
vault:
kv-version: "1"
1
java -Dspring.cloud.config.server.vault.kv-version="1" -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_CONFIG_SERVER_VAULT_KV_VERSION="1"
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.config.server.vault.kv-version="1"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.namespace=
The value of the Vault X-Vault-Namespace header. Defaults to null. This a Vault Enterprise feature only.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.namespace
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.config.server.vault.namespace=...
1
spring:
cloud:
config:
server:
vault:
namespace: "..."
1
java -Dspring.cloud.config.server.vault.namespace="..." -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_CONFIG_SERVER_VAULT_NAMESPACE="..."
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.config.server.vault.namespace="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.order=
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.order
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.config.server.vault.order=...
1
spring:
cloud:
config:
server:
vault:
order: "..."
1
java -Dspring.cloud.config.server.vault.order="..." -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_CONFIG_SERVER_VAULT_ORDER="..."
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.config.server.vault.order="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.path-to-key=
KV2 API required "data" after "mount-path". There could be folder/path structure, where the keys/applications are grouped. This property is the path after mount-path, under which application(s) are located (appended after "data") Default value is blank, which means all grouped applications are located right under the mount-path
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.path-to-key
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.config.server.vault.path-to-key=...
1
spring:
cloud:
config:
server:
vault:
path-to-key: "..."
1
java -Dspring.cloud.config.server.vault.path-to-key="..." -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_CONFIG_SERVER_VAULT_PATH_TO_KEY="..."
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.config.server.vault.path-to-key="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.pcf.instance-certificate=
Path to the instance certificate (PEM). Defaults to CF_INSTANCE_CERT
env variable.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$PcfProperties.
CAS Property: spring.cloud.config.server.vault.pcf.instance-certificate
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.config.server.vault.pcf.instance-certificate=...
1
spring:
cloud:
config:
server:
vault:
pcf:
instance-certificate: "..."
1
java -Dspring.cloud.config.server.vault.pcf.instance-certificate="..." -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_CONFIG_SERVER_VAULT_PCF_INSTANCE_CERTIFICATE="..."
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.config.server.vault.pcf.instance-certificate="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.pcf.instance-key=
Path to the instance key (PEM). Defaults to CF_INSTANCE_KEY
env variable.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$PcfProperties.
CAS Property: spring.cloud.config.server.vault.pcf.instance-key
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.config.server.vault.pcf.instance-key=...
1
spring:
cloud:
config:
server:
vault:
pcf:
instance-key: "..."
1
java -Dspring.cloud.config.server.vault.pcf.instance-key="..." -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_CONFIG_SERVER_VAULT_PCF_INSTANCE_KEY="..."
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.config.server.vault.pcf.instance-key="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.pcf.pcf-path=pcf
Mount path of the Kubernetes authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$PcfProperties.
CAS Property: spring.cloud.config.server.vault.pcf.pcf-path
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.config.server.vault.pcf.pcf-path=pcf
1
spring:
cloud:
config:
server:
vault:
pcf:
pcf-path: "pcf"
1
java -Dspring.cloud.config.server.vault.pcf.pcf-path="pcf" -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_CONFIG_SERVER_VAULT_PCF_PCF_PATH="pcf"
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.config.server.vault.pcf.pcf-path="pcf"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.pcf.role=
Name of the role against which the login is being attempted.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$PcfProperties.
CAS Property: spring.cloud.config.server.vault.pcf.role
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.config.server.vault.pcf.role=...
1
spring:
cloud:
config:
server:
vault:
pcf:
role: "..."
1
java -Dspring.cloud.config.server.vault.pcf.role="..." -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_CONFIG_SERVER_VAULT_PCF_ROLE="..."
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.config.server.vault.pcf.role="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.port=8200
Vault port. Defaults to 8200.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.port
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.config.server.vault.port=8200
1
spring:
cloud:
config:
server:
vault:
port: "8200"
1
java -Dspring.cloud.config.server.vault.port="8200" -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_CONFIG_SERVER_VAULT_PORT="8200"
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.config.server.vault.port="8200"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.profile-separator=,
Vault profile separator. Defaults to comma.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.profile-separator
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.config.server.vault.profile-separator=,
1
spring:
cloud:
config:
server:
vault:
profile-separator: ","
1
java -Dspring.cloud.config.server.vault.profile-separator="," -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_CONFIG_SERVER_VAULT_PROFILE_SEPARATOR=","
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.config.server.vault.profile-separator=","
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.proxy=
HTTP proxy configuration.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.proxy
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.config.server.vault.proxy=...
1
spring:
cloud:
config:
server:
vault:
proxy: "..."
1
java -Dspring.cloud.config.server.vault.proxy="..." -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_CONFIG_SERVER_VAULT_PROXY="..."
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.config.server.vault.proxy="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.scheme=http
Vault scheme. Defaults to http.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.scheme
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.config.server.vault.scheme=http
1
spring:
cloud:
config:
server:
vault:
scheme: "http"
1
java -Dspring.cloud.config.server.vault.scheme="http" -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_CONFIG_SERVER_VAULT_SCHEME="http"
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.config.server.vault.scheme="http"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.skip-ssl-validation=false
Flag to indicate that SSL certificate validation should be bypassed when communicating with a repository served over an HTTPS connection.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.skip-ssl-validation
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.config.server.vault.skip-ssl-validation=...
1
spring:
cloud:
config:
server:
vault:
skip-ssl-validation: "..."
1
java -Dspring.cloud.config.server.vault.skip-ssl-validation="..." -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_CONFIG_SERVER_VAULT_SKIP_SSL_VALIDATION="..."
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.config.server.vault.skip-ssl-validation="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.ssl.cert-auth-path=cert
Mount path of the TLS cert authentication backend.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.
CAS Property: spring.cloud.config.server.vault.ssl.cert-auth-path
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.config.server.vault.ssl.cert-auth-path=cert
1
spring:
cloud:
config:
server:
vault:
ssl:
cert-auth-path: "cert"
1
java -Dspring.cloud.config.server.vault.ssl.cert-auth-path="cert" -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_CONFIG_SERVER_VAULT_SSL_CERT_AUTH_PATH="cert"
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.config.server.vault.ssl.cert-auth-path="cert"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.ssl.key-store=
Trust store that holds certificates and private keys.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.
CAS Property: spring.cloud.config.server.vault.ssl.key-store
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.config.server.vault.ssl.key-store=...
1
spring:
cloud:
config:
server:
vault:
ssl:
key-store: "..."
1
java -Dspring.cloud.config.server.vault.ssl.key-store="..." -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_CONFIG_SERVER_VAULT_SSL_KEY_STORE="..."
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.config.server.vault.ssl.key-store="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.ssl.key-store-password=
Password used to access the key store.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.
CAS Property: spring.cloud.config.server.vault.ssl.key-store-password
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.config.server.vault.ssl.key-store-password=...
1
spring:
cloud:
config:
server:
vault:
ssl:
key-store-password: "..."
1
java -Dspring.cloud.config.server.vault.ssl.key-store-password="..." -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_CONFIG_SERVER_VAULT_SSL_KEY_STORE_PASSWORD="..."
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.config.server.vault.ssl.key-store-password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.ssl.trust-store=
Trust store that holds SSL certificates.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.
CAS Property: spring.cloud.config.server.vault.ssl.trust-store
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.config.server.vault.ssl.trust-store=...
1
spring:
cloud:
config:
server:
vault:
ssl:
trust-store: "..."
1
java -Dspring.cloud.config.server.vault.ssl.trust-store="..." -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_CONFIG_SERVER_VAULT_SSL_TRUST_STORE="..."
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.config.server.vault.ssl.trust-store="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.ssl.trust-store-password=
Password used to access the trust store.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.
CAS Property: spring.cloud.config.server.vault.ssl.trust-store-password
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.config.server.vault.ssl.trust-store-password=...
1
spring:
cloud:
config:
server:
vault:
ssl:
trust-store-password: "..."
1
java -Dspring.cloud.config.server.vault.ssl.trust-store-password="..." -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_CONFIG_SERVER_VAULT_SSL_TRUST_STORE_PASSWORD="..."
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.config.server.vault.ssl.trust-store-password="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.timeout=5
Timeout (in seconds) for obtaining HTTP connection, defaults to 5 seconds.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.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.config.server.vault.timeout=5
1
spring:
cloud:
config:
server:
vault:
timeout: "5"
1
java -Dspring.cloud.config.server.vault.timeout="5" -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_CONFIG_SERVER_VAULT_TIMEOUT="5"
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.config.server.vault.timeout="5"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.server.vault.token=
Static vault token. Required if #authentication
is TOKEN
.
org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.
CAS Property: spring.cloud.config.server.vault.token
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.config.server.vault.token=...
1
spring:
cloud:
config:
server:
vault:
token: "..."
1
java -Dspring.cloud.config.server.vault.token="..." -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_CONFIG_SERVER_VAULT_TOKEN="..."
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.config.server.vault.token="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.tls=
TLS properties.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.tls
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.config.tls=...
1
spring:
cloud:
config:
tls: "..."
1
java -Dspring.cloud.config.tls="..." -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_CONFIG_TLS="..."
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.config.tls="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.token=
Security Token passed thru to underlying environment repository.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.token
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.config.token=...
1
spring:
cloud:
config:
token: "..."
1
java -Dspring.cloud.config.token="..." -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_CONFIG_TOKEN="..."
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.config.token="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.uri=http://localhost:8888
The URI of the remote server (default http://localhost:8888).
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.uri
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.config.uri=http://localhost:8888
1
spring:
cloud:
config:
uri: "["http://localhost:8888"]"
1
java -Dspring.cloud.config.uri="["http://localhost:8888"]" -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_CONFIG_URI="["http://localhost:8888"]"
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.config.uri="["http://localhost:8888"]"
cas.war
with an embedded server container and can be found in the build/libs
directory.
spring.cloud.config.username=
The username to use (HTTP Basic) when contacting the remote server.
org.springframework.cloud.config.client.ConfigClientProperties.
CAS Property: spring.cloud.config.username
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.config.username=...
1
spring:
cloud:
config:
username: "..."
1
java -Dspring.cloud.config.username="..." -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_CONFIG_USERNAME="..."
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.config.username="..."
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.