WORKERS AHEAD!

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

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 of spring.application.name are loaded (i.e cas.properties) Note: spring.application.name defaults to uppercase CAS but the lowercase name will also be loaded.
Settings located inside properties|yml|yaml files whose name matches the value of spring.profiles.active are loaded (i.e ldap.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:

// 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:

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

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

cas.standalone.configuration-directory=

Describes a directory path where CAS configuration may be found.

org.apereo.cas.configuration.model.core.config.standalone.StandaloneConfigurationProperties.

_{How can I configure this property?}

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

Note

When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value. The only possible exception to this rule is when naming actuator endpoints; The name of the actuator endpoints (i.e. ssoSessions) MUST remain in camelCase mode.

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

cas.standalone.configuration-directory=...

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

CAS properties can be specified using the YAML syntax:

cas: 
  standalone: 
    configuration-directory: "..."

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

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

java -Dcas.standalone.configuration-directory="..." -jar build/libs/cas.war

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

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

export CAS_STANDALONE_CONFIGURATION_DIRECTORY="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.standalone.configuration-directory="..."

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

cas.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.

_{How can I configure this property?}

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

Note

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

cas.standalone.configuration-file=...

CAS properties can be specified using the YAML syntax:

cas: 
  standalone: 
    configuration-file: "..."

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

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

java -Dcas.standalone.configuration-file="..." -jar build/libs/cas.war

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

export CAS_STANDALONE_CONFIGURATION_FILE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --cas.standalone.configuration-file="..."

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

Configuration Metadata

The collection of configuration properties listed in this section are automatically generated from the CAS source and components that contain the actual field definitions, types, descriptions, modules, etc. This metadata may not always be 100% accurate, or could be lacking details and sufficient explanations.

Be Selective

This section is meant as a guide only. Do NOT copy/paste the entire collection of settings into your CAS configuration; rather pick only the properties that you need. Do NOT enable settings unless you are certain of their purpose and do NOT copy settings into your configuration only to keep them as reference. All these ideas lead to upgrade headaches, maintenance nightmares and premature aging.

YAGNI

Note that for nearly ALL use cases, declaring and configuring properties listed here is sufficient. You should NOT have to explicitly massage a CAS XML/Java/etc configuration file to design an authentication handler, create attribute release policies, etc. CAS at runtime will auto-configure all required changes for you. If you are unsure about the meaning of a given CAS setting, do NOT turn it on without hesitation. Review the codebase or better yet, ask questions to clarify the intended behavior.

Naming Convention

Property names can be specified in very relaxed terms. For instance cas.someProperty, cas.some-property, cas.some_property are all valid names. While all forms are accepted by CAS, there are certain components (in CAS and other frameworks used) whose activation at runtime is conditional on a property value, where this property is required to have been specified in CAS configuration using kebab case. This is both true for properties that are owned by CAS as well as those that might be presented to the system via an external library or framework such as Spring Boot, etc.

Note

Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas. All other settings are controlled and provided to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the way you intend.

Validation

Configuration properties are automatically validated on CAS startup to report issues with configuration binding, specially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.

Indexed Settings

CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be incremented by the adopter to allow for distinct multiple configuration blocks.

Handling Overrides

Remember

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:

_{The configuration settings listed below are tagged as Third Party in the CAS configuration metadata. This flag indicates that the configuration setting is not controlled, owned or managed by the CAS ecosystem, and affects functionality that is offered by a third-party library, such as Spring Boot or Spring Cloud to CAS. For additional info, you might have to visit the third-party source to find more details.}

spring.cloud.config.allow-override=true

Flag to indicate that #isOverrideSystemProperties() systemPropertiesOverride can be used. Set to false to prevent users from changing the default accidentally. Default true.

org.springframework.cloud.bootstrap.config.PropertySourceBootstrapProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.allow-override=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      allow-override: "true"

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

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

java -Dspring.cloud.config.allow-override="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_ALLOW_OVERRIDE="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.allow-override="true"

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

spring.cloud.config.charset=UTF-8

The charset to read the resource from the config server.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.charset=UTF-8

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      charset: "UTF-8"

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

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

java -Dspring.cloud.config.charset="UTF-8" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_CHARSET="UTF-8"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.charset="UTF-8"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.discovery.enabled=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      discovery: 
        enabled: "..."

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

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

java -Dspring.cloud.config.discovery.enabled="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_DISCOVERY_ENABLED="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.discovery.enabled="..."

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

spring.cloud.config.discovery.service-id=configserver

Service id to locate config server.

org.springframework.cloud.config.client.ConfigClientProperties$Discovery.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.discovery.service-id=configserver

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      discovery: 
        service-id: "configserver"

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

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

java -Dspring.cloud.config.discovery.service-id="configserver" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_DISCOVERY_SERVICE_ID="configserver"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.discovery.service-id="configserver"

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

spring.cloud.config.enabled=true

Flag to say that remote configuration is enabled. Default true;

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      enabled: "true"

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

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

java -Dspring.cloud.config.enabled="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_ENABLED="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.enabled="true"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.fail-fast=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      fail-fast: "..."

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

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

java -Dspring.cloud.config.fail-fast="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_FAIL_FAST="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.fail-fast="..."

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

spring.cloud.config.headers=

Additional headers used to create the client request.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.headers=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      headers: "..."

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

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

java -Dspring.cloud.config.headers="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_HEADERS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.headers="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.initialize-on-context-refresh=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      initialize-on-context-refresh: "..."

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

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

java -Dspring.cloud.config.initialize-on-context-refresh="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_INITIALIZE_ON_CONTEXT_REFRESH="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.initialize-on-context-refresh="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.label=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      label: "..."

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

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

java -Dspring.cloud.config.label="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_LABEL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.label="..."

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

spring.cloud.config.media-type=

The Accept header media type to send to config server.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.media-type=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      media-type: "..."

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

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

java -Dspring.cloud.config.media-type="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_MEDIA_TYPE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.media-type="..."

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

spring.cloud.config.multiple-uri-strategy=always

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.multiple-uri-strategy=always

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      multiple-uri-strategy: "always"

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

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

java -Dspring.cloud.config.multiple-uri-strategy="always" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_MULTIPLE_URI_STRATEGY="always"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.multiple-uri-strategy="always"

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

spring.cloud.config.name=

Name of application used to fetch remote properties.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.name=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      name: "..."

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

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

java -Dspring.cloud.config.name="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_NAME="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.name="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.override-none=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      override-none: "..."

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

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

java -Dspring.cloud.config.override-none="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_OVERRIDE_NONE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.override-none="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.override-system-properties=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      override-system-properties: "true"

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

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

java -Dspring.cloud.config.override-system-properties="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_OVERRIDE_SYSTEM_PROPERTIES="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.override-system-properties="true"

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

spring.cloud.config.password=

The password to use (HTTP Basic) when contacting the remote server.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      password: "..."

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

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

java -Dspring.cloud.config.password="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_PASSWORD="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.password="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.profile=default

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      profile: "default"

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

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

java -Dspring.cloud.config.profile="default" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_PROFILE="default"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.profile="default"

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

spring.cloud.config.request-connect-timeout=0

timeout on waiting to connect to the Config Server.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.request-connect-timeout=0

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      request-connect-timeout: "0"

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

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

java -Dspring.cloud.config.request-connect-timeout="0" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_REQUEST_CONNECT_TIMEOUT="0"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.request-connect-timeout="0"

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

spring.cloud.config.request-read-timeout=0

timeout on waiting to read data from the Config Server.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.request-read-timeout=0

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      request-read-timeout: "0"

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

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

java -Dspring.cloud.config.request-read-timeout="0" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_REQUEST_READ_TIMEOUT="0"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.request-read-timeout="0"

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

spring.cloud.config.retry.initial-interval=1000

Initial retry interval in milliseconds.

org.springframework.cloud.config.client.RetryProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.retry.initial-interval=1000

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      retry: 
        initial-interval: "1000"

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

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

java -Dspring.cloud.config.retry.initial-interval="1000" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_RETRY_INITIAL_INTERVAL="1000"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.retry.initial-interval="1000"

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

spring.cloud.config.retry.max-attempts=6

Maximum number of attempts.

org.springframework.cloud.config.client.RetryProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.retry.max-attempts=6

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      retry: 
        max-attempts: "6"

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

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

java -Dspring.cloud.config.retry.max-attempts="6" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_RETRY_MAX_ATTEMPTS="6"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.retry.max-attempts="6"

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

spring.cloud.config.retry.max-interval=2000

Maximum interval for backoff.

org.springframework.cloud.config.client.RetryProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.retry.max-interval=2000

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      retry: 
        max-interval: "2000"

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

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

java -Dspring.cloud.config.retry.max-interval="2000" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_RETRY_MAX_INTERVAL="2000"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.retry.max-interval="2000"

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

spring.cloud.config.retry.multiplier=1.1

Multiplier for next interval.

org.springframework.cloud.config.client.RetryProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.retry.multiplier=1.1

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      retry: 
        multiplier: "1.1"

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

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

java -Dspring.cloud.config.retry.multiplier="1.1" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_RETRY_MULTIPLIER="1.1"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.retry.multiplier="1.1"

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

spring.cloud.config.retry.use-random-policy=false

Use a random exponential backoff policy.

org.springframework.cloud.config.client.RetryProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.retry.use-random-policy=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      retry: 
        use-random-policy: "..."

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

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

java -Dspring.cloud.config.retry.use-random-policy="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_RETRY_USE_RANDOM_POLICY="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.retry.use-random-policy="..."

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

spring.cloud.config.send-all-labels=false

If set to true the client will send all labels to the server instead of sending one at a time. Support for this would require a config server version of 4.2.0 or higher.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.send-all-labels=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      send-all-labels: "..."

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

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

java -Dspring.cloud.config.send-all-labels="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SEND_ALL_LABELS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.send-all-labels="..."

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

spring.cloud.config.send-state=true

Flag to indicate whether to send state. Default true.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.send-state=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      send-state: "true"

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

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

java -Dspring.cloud.config.send-state="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SEND_STATE="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.send-state="true"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.accept-empty=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        accept-empty: "true"

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

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

java -Dspring.cloud.config.server.accept-empty="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_ACCEPT_EMPTY="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.accept-empty="true"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.aws-secretsmanager.default-label=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        aws-secretsmanager: 
          default-label: "..."

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

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

java -Dspring.cloud.config.server.aws-secretsmanager.default-label="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWS_SECRETSMANAGER_DEFAULT_LABEL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.aws-secretsmanager.default-label="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.aws-secretsmanager.endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        aws-secretsmanager: 
          endpoint: "..."

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

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

java -Dspring.cloud.config.server.aws-secretsmanager.endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWS_SECRETSMANAGER_ENDPOINT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.aws-secretsmanager.endpoint="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.aws-secretsmanager.ignore-label=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        aws-secretsmanager: 
          ignore-label: "..."

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

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

java -Dspring.cloud.config.server.aws-secretsmanager.ignore-label="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWS_SECRETSMANAGER_IGNORE_LABEL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.aws-secretsmanager.ignore-label="..."

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

spring.cloud.config.server.aws-secretsmanager.order=

The order of the environment repository.

org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.aws-secretsmanager.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        aws-secretsmanager: 
          order: "..."

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

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

java -Dspring.cloud.config.server.aws-secretsmanager.order="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWS_SECRETSMANAGER_ORDER="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.aws-secretsmanager.order="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.aws-secretsmanager.origin=aws:secrets:

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        aws-secretsmanager: 
          origin: "aws:secrets:"

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

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

java -Dspring.cloud.config.server.aws-secretsmanager.origin="aws:secrets:" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWS_SECRETSMANAGER_ORIGIN="aws:secrets:"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.aws-secretsmanager.origin="aws:secrets:"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.aws-secretsmanager.prefix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        aws-secretsmanager: 
          prefix: "..."

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

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

java -Dspring.cloud.config.server.aws-secretsmanager.prefix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWS_SECRETSMANAGER_PREFIX="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.aws-secretsmanager.prefix="..."

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

spring.cloud.config.server.aws-secretsmanager.profile-separator=-

String that separates profile from the application name.

org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.aws-secretsmanager.profile-separator=-

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        aws-secretsmanager: 
          profile-separator: "-"

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

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

java -Dspring.cloud.config.server.aws-secretsmanager.profile-separator="-" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWS_SECRETSMANAGER_PROFILE_SEPARATOR="-"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.aws-secretsmanager.profile-separator="-"

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

spring.cloud.config.server.aws-secretsmanager.region=

The region to be used by AWS Secrets Manager client.

org.springframework.cloud.config.server.environment.AwsSecretsManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.aws-secretsmanager.region=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        aws-secretsmanager: 
          region: "..."

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

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

java -Dspring.cloud.config.server.aws-secretsmanager.region="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWS_SECRETSMANAGER_REGION="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.aws-secretsmanager.region="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.decrypt-values=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          decrypt-values: "true"

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

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

java -Dspring.cloud.config.server.awsparamstore.decrypt-values="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_DECRYPT_VALUES="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.decrypt-values="true"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          endpoint: "..."

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

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

java -Dspring.cloud.config.server.awsparamstore.endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_ENDPOINT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.endpoint="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.max-results=10

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          max-results: "10"

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

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

java -Dspring.cloud.config.server.awsparamstore.max-results="10" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_MAX_RESULTS="10"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.max-results="10"

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

spring.cloud.config.server.awsparamstore.order=

The order of the environment repository.

org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          order: "..."

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

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

java -Dspring.cloud.config.server.awsparamstore.order="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_ORDER="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.order="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.origin=aws:ssm:parameter:

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          origin: "aws:ssm:parameter:"

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

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

java -Dspring.cloud.config.server.awsparamstore.origin="aws:ssm:parameter:" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_ORIGIN="aws:ssm:parameter:"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.origin="aws:ssm:parameter:"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.prefix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          prefix: "..."

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

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

java -Dspring.cloud.config.server.awsparamstore.prefix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_PREFIX="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.prefix="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.profile-separator=-

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          profile-separator: "-"

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

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

java -Dspring.cloud.config.server.awsparamstore.profile-separator="-" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_PROFILE_SEPARATOR="-"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.profile-separator="-"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.recursive=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          recursive: "true"

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

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

java -Dspring.cloud.config.server.awsparamstore.recursive="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_RECURSIVE="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.recursive="true"

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

spring.cloud.config.server.awsparamstore.region=

The region to be used by the AWS Parameter Store client.

org.springframework.cloud.config.server.environment.AwsParameterStoreEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awsparamstore.region=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awsparamstore: 
          region: "..."

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

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

java -Dspring.cloud.config.server.awsparamstore.region="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSPARAMSTORE_REGION="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awsparamstore.region="..."

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

spring.cloud.config.server.awss3.bucket=

Name of the S3 bucket that contains config.

org.springframework.cloud.config.server.environment.AwsS3EnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awss3.bucket=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awss3: 
          bucket: "..."

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

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

java -Dspring.cloud.config.server.awss3.bucket="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSS3_BUCKET="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awss3.bucket="..."

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

spring.cloud.config.server.awss3.endpoint=

Adds the ability to override the baseUrl of the s3 client.

org.springframework.cloud.config.server.environment.AwsS3EnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awss3.endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awss3: 
          endpoint: "..."

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

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

java -Dspring.cloud.config.server.awss3.endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSS3_ENDPOINT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awss3.endpoint="..."

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

spring.cloud.config.server.awss3.order=0

org.springframework.cloud.config.server.environment.AwsS3EnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awss3.order=0

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awss3: 
          order: "0"

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

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

java -Dspring.cloud.config.server.awss3.order="0" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSS3_ORDER="0"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awss3.order="0"

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

spring.cloud.config.server.awss3.region=

AWS region that contains config.

org.springframework.cloud.config.server.environment.AwsS3EnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.awss3.region=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        awss3: 
          region: "..."

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

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

java -Dspring.cloud.config.server.awss3.region="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_AWSS3_REGION="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.awss3.region="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.bootstrap=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        bootstrap: "..."

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

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

java -Dspring.cloud.config.server.bootstrap="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_BOOTSTRAP="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.bootstrap="..."

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

spring.cloud.config.server.credhub.ca-cert-files=

org.springframework.credhub.support.ClientOptions.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.credhub.ca-cert-files=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        credhub: 
          ca-cert-files: "..."

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

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

java -Dspring.cloud.config.server.credhub.ca-cert-files="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_CREDHUB_CA_CERT_FILES="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.credhub.ca-cert-files="..."

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

spring.cloud.config.server.credhub.connection-timeout=

org.springframework.credhub.support.ClientOptions.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.credhub.connection-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        credhub: 
          connection-timeout: "..."

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

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

java -Dspring.cloud.config.server.credhub.connection-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_CREDHUB_CONNECTION_TIMEOUT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.credhub.connection-timeout="..."

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

spring.cloud.config.server.credhub.default-label=master

The default label to be used when is not provided by client applications.

org.springframework.cloud.config.server.environment.CredhubEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.credhub.default-label=master

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        credhub: 
          default-label: "master"

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

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

java -Dspring.cloud.config.server.credhub.default-label="master" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_CREDHUB_DEFAULT_LABEL="master"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.credhub.default-label="master"

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

spring.cloud.config.server.credhub.oauth2.registration-id=

org.springframework.credhub.core.CredHubProperties$OAuth2.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.credhub.oauth2.registration-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        credhub: 
          oauth2: 
            registration-id: "..."

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

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

java -Dspring.cloud.config.server.credhub.oauth2.registration-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_CREDHUB_OAUTH2_REGISTRATION_ID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.credhub.oauth2.registration-id="..."

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

spring.cloud.config.server.credhub.order=

org.springframework.cloud.config.server.environment.CredhubEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.credhub.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        credhub: 
          order: "..."

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

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

java -Dspring.cloud.config.server.credhub.order="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_CREDHUB_ORDER="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.credhub.order="..."

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

spring.cloud.config.server.credhub.path=

The common base path for credentials in CredHub. It is empty by default.

org.springframework.cloud.config.server.environment.CredhubEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.credhub.path=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        credhub: 
          path: "..."

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

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

java -Dspring.cloud.config.server.credhub.path="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_CREDHUB_PATH="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.credhub.path="..."

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

spring.cloud.config.server.credhub.read-timeout=

org.springframework.credhub.support.ClientOptions.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.credhub.read-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        credhub: 
          read-timeout: "..."

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

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

java -Dspring.cloud.config.server.credhub.read-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_CREDHUB_READ_TIMEOUT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.credhub.read-timeout="..."

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

spring.cloud.config.server.credhub.url=

org.springframework.credhub.core.CredHubProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.credhub.url=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        credhub: 
          url: "..."

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

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

java -Dspring.cloud.config.server.credhub.url="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_CREDHUB_URL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.credhub.url="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.default-application-name=application

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        default-application-name: "application"

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

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

java -Dspring.cloud.config.server.default-application-name="application" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_DEFAULT_APPLICATION_NAME="application"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.default-application-name="application"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.default-label=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        default-label: "..."

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

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

java -Dspring.cloud.config.server.default-label="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_DEFAULT_LABEL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.default-label="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.default-profile=default

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        default-profile: "default"

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

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

java -Dspring.cloud.config.server.default-profile="default" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_DEFAULT_PROFILE="default"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.default-profile="default"

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

spring.cloud.config.server.enabled=true

Flag indicating config server is enabled.

org.springframework.cloud.config.server.config.ConfigServerProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        enabled: "true"

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

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

java -Dspring.cloud.config.server.enabled="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_ENABLED="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.enabled="true"

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

spring.cloud.config.server.encrypt.enabled=true

Enable decryption of environment properties before sending to client.

org.springframework.cloud.config.server.config.ConfigServerProperties$Encrypt.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.encrypt.enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        encrypt: 
          enabled: "true"

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

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

java -Dspring.cloud.config.server.encrypt.enabled="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_ENCRYPT_ENABLED="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.encrypt.enabled="true"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.encrypt.plain-text-encrypt=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        encrypt: 
          plain-text-encrypt: "..."

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

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

java -Dspring.cloud.config.server.encrypt.plain-text-encrypt="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_ENCRYPT_PLAIN_TEXT_ENCRYPT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.encrypt.plain-text-encrypt="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.fail-on-composite-error=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        fail-on-composite-error: "true"

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

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

java -Dspring.cloud.config.server.fail-on-composite-error="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_FAIL_ON_COMPOSITE_ERROR="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.fail-on-composite-error="true"

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

spring.cloud.config.server.gcp-secret-manager.application-label=application

org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.gcp-secret-manager.application-label=application

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        gcp-secret-manager: 
          application-label: "application"

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

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

java -Dspring.cloud.config.server.gcp-secret-manager.application-label="application" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GCP_SECRET_MANAGER_APPLICATION_LABEL="application"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.gcp-secret-manager.application-label="application"

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

spring.cloud.config.server.gcp-secret-manager.order=

org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.gcp-secret-manager.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        gcp-secret-manager: 
          order: "..."

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

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

java -Dspring.cloud.config.server.gcp-secret-manager.order="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GCP_SECRET_MANAGER_ORDER="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.gcp-secret-manager.order="..."

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

spring.cloud.config.server.gcp-secret-manager.profile-label=profile

org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.gcp-secret-manager.profile-label=profile

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        gcp-secret-manager: 
          profile-label: "profile"

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

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

java -Dspring.cloud.config.server.gcp-secret-manager.profile-label="profile" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GCP_SECRET_MANAGER_PROFILE_LABEL="profile"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.gcp-secret-manager.profile-label="profile"

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

spring.cloud.config.server.gcp-secret-manager.service-account=

org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.gcp-secret-manager.service-account=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        gcp-secret-manager: 
          service-account: "..."

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

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

java -Dspring.cloud.config.server.gcp-secret-manager.service-account="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GCP_SECRET_MANAGER_SERVICE_ACCOUNT="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.gcp-secret-manager.service-account="..."

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

spring.cloud.config.server.gcp-secret-manager.token-mandatory=true

org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.gcp-secret-manager.token-mandatory=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        gcp-secret-manager: 
          token-mandatory: "true"

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

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

java -Dspring.cloud.config.server.gcp-secret-manager.token-mandatory="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GCP_SECRET_MANAGER_TOKEN_MANDATORY="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.gcp-secret-manager.token-mandatory="true"

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

spring.cloud.config.server.gcp-secret-manager.version=1

org.springframework.cloud.config.server.environment.GoogleSecretManagerEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.gcp-secret-manager.version=1

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        gcp-secret-manager: 
          version: "1"

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

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

java -Dspring.cloud.config.server.gcp-secret-manager.version="1" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GCP_SECRET_MANAGER_VERSION="1"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.gcp-secret-manager.version="1"

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

spring.cloud.config.server.git.basedir=

Base directory for local working copy of repository.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.basedir=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          basedir: "..."

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

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

java -Dspring.cloud.config.server.git.basedir="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_BASEDIR="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.basedir="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.clone-on-start=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          clone-on-start: "..."

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

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

java -Dspring.cloud.config.server.git.clone-on-start="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_CLONE_ON_START="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.clone-on-start="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.clone-submodules=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          clone-submodules: "..."

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

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

java -Dspring.cloud.config.server.git.clone-submodules="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_CLONE_SUBMODULES="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.clone-submodules="..."

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

spring.cloud.config.server.git.default-label=

The default label to be used with the remote repository.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.default-label=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          default-label: "..."

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

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

java -Dspring.cloud.config.server.git.default-label="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_DEFAULT_LABEL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.default-label="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.delete-untracked-branches=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          delete-untracked-branches: "..."

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

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

java -Dspring.cloud.config.server.git.delete-untracked-branches="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_DELETE_UNTRACKED_BRANCHES="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.delete-untracked-branches="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.force-pull=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          force-pull: "..."

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

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

java -Dspring.cloud.config.server.git.force-pull="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_FORCE_PULL="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.force-pull="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.host-key=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          host-key: "..."

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

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

java -Dspring.cloud.config.server.git.host-key="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_HOST_KEY="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.host-key="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.host-key-algorithm=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          host-key-algorithm: "..."

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

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

java -Dspring.cloud.config.server.git.host-key-algorithm="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_HOST_KEY_ALGORITHM="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.host-key-algorithm="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.ignore-local-ssh-settings=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          ignore-local-ssh-settings: "..."

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

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

java -Dspring.cloud.config.server.git.ignore-local-ssh-settings="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_IGNORE_LOCAL_SSH_SETTINGS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.ignore-local-ssh-settings="..."

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

spring.cloud.config.server.git.known-hosts-file=

Location of custom .known_hosts file.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.known-hosts-file=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          known-hosts-file: "..."

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

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

java -Dspring.cloud.config.server.git.known-hosts-file="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_KNOWN_HOSTS_FILE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.known-hosts-file="..."

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

spring.cloud.config.server.git.order=

The order of the environment repository.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          order: "..."

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

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

java -Dspring.cloud.config.server.git.order="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_ORDER="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.order="..."

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

spring.cloud.config.server.git.passphrase=

Passphrase for unlocking your ssh private key.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.passphrase=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          passphrase: "..."

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

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

java -Dspring.cloud.config.server.git.passphrase="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_PASSPHRASE="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.passphrase="..."

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

spring.cloud.config.server.git.password=

Password for authentication with remote repository.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          password: "..."

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

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

java -Dspring.cloud.config.server.git.password="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_PASSWORD="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.password="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.preferred-authentications=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          preferred-authentications: "..."

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

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

java -Dspring.cloud.config.server.git.preferred-authentications="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_PREFERRED_AUTHENTICATIONS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.preferred-authentications="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.private-key=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          private-key: "..."

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

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

java -Dspring.cloud.config.server.git.private-key="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_PRIVATE_KEY="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.private-key="..."

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

spring.cloud.config.server.git.proxy=

HTTP proxy configuration.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.proxy=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          proxy: "..."

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

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

java -Dspring.cloud.config.server.git.proxy="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_PROXY="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.proxy="..."

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

spring.cloud.config.server.git.refresh-rate=0

Time (in seconds) between refresh of the git repository.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.refresh-rate=0

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          refresh-rate: "0"

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

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

java -Dspring.cloud.config.server.git.refresh-rate="0" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_REFRESH_RATE="0"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.refresh-rate="0"

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

spring.cloud.config.server.git.repos=

Map of repository identifier to location and other properties.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.repos=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          repos: "..."

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

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

java -Dspring.cloud.config.server.git.repos="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_REPOS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.repos="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.search-paths=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          search-paths: "..."

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

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

java -Dspring.cloud.config.server.git.search-paths="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_SEARCH_PATHS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.search-paths="..."

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.skip-ssl-validation=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          skip-ssl-validation: "..."

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

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

java -Dspring.cloud.config.server.git.skip-ssl-validation="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_SKIP_SSL_VALIDATION="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.skip-ssl-validation="..."

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

spring.cloud.config.server.git.strict-host-key-checking=true

If false, ignore errors with host key.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.strict-host-key-checking=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          strict-host-key-checking: "true"

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

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

java -Dspring.cloud.config.server.git.strict-host-key-checking="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_STRICT_HOST_KEY_CHECKING="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.strict-host-key-checking="true"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.timeout=5

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          timeout: "5"

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

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

java -Dspring.cloud.config.server.git.timeout="5" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_TIMEOUT="5"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.timeout="5"

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

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.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.try-master-branch=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          try-master-branch: "true"

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

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

java -Dspring.cloud.config.server.git.try-master-branch="true" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_TRY_MASTER_BRANCH="true"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.try-master-branch="true"

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

spring.cloud.config.server.git.uri=

URI of remote repository.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.uri=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          uri: "..."

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

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

java -Dspring.cloud.config.server.git.uri="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_URI="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.uri="..."

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

spring.cloud.config.server.git.username=

Username for authentication with remote repository.

org.springframework.cloud.config.server.environment.MultipleJGitEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.git.username=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        git: 
          username: "..."

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

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

java -Dspring.cloud.config.server.git.username="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_GIT_USERNAME="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.git.username="..."

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

spring.cloud.config.server.health.down-health-status=

org.springframework.cloud.config.server.config.ConfigServerHealthIndicator.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.health.down-health-status=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        health: 
          down-health-status: "..."

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

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

java -Dspring.cloud.config.server.health.down-health-status="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_HEALTH_DOWN_HEALTH_STATUS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.health.down-health-status="..."

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

spring.cloud.config.server.health.repositories=

org.springframework.cloud.config.server.config.ConfigServerHealthIndicator.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.health.repositories=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        health: 
          repositories: "..."

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

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

java -Dspring.cloud.config.server.health.repositories="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_HEALTH_REPOSITORIES="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.health.repositories="..."

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

spring.cloud.config.server.jdbc.default-label=master

org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.jdbc.default-label=master

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        jdbc: 
          default-label: "master"

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

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

java -Dspring.cloud.config.server.jdbc.default-label="master" -jar build/libs/cas.war

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

export SPRING_CLOUD_CONFIG_SERVER_JDBC_DEFAULT_LABEL="master"

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.config.server.jdbc.default-label="master"

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

spring.cloud.config.server.jdbc.enabled=true

Flag to indicate that JDBC environment repository configuration is enabled.

org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.

_{How can I configure this property?}

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

Note

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

spring.cloud.config.server.jdbc.enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        jdbc: 
          enabled: "true"

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

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.jdbc.enabled="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_JDBC_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.jdbc.enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.jdbc.fail-on-error=true

Flag to determine how to handle query exceptions.

org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.jdbc.fail-on-error=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        jdbc: 
          fail-on-error: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.jdbc.fail-on-error="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_JDBC_FAIL_ON_ERROR="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.jdbc.fail-on-error="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.jdbc.order=0

org.springframework.cloud.config.server.environment.JdbcEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.jdbc.order=0

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        jdbc: 
          order: "0"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.jdbc.order="0" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_JDBC_ORDER="0"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.jdbc.order="0"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.jdbc.sql=SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        jdbc: 
          sql: "SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.jdbc.sql="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_JDBC_SQL="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.jdbc.sql="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE=? and LABEL=?"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.jdbc.sql-without-profile=SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        jdbc: 
          sql-without-profile: "SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -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 properties can specified as system environment variables before the CAS web application is launched:

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

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.jdbc.sql-without-profile="SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.mongodb.collection=properties

Name of the MongoDB collection to query for configuration properties.

org.springframework.cloud.config.server.environment.MongoDbEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.mongodb.collection=properties

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        mongodb: 
          collection: "properties"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.mongodb.collection="properties" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_MONGODB_COLLECTION="properties"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.mongodb.collection="properties"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.mongodb.default-label=master

Default label to use if none is specified.

org.springframework.cloud.config.server.environment.MongoDbEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.mongodb.default-label=master

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        mongodb: 
          default-label: "master"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.mongodb.default-label="master" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_MONGODB_DEFAULT_LABEL="master"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.mongodb.default-label="master"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.mongodb.enabled=true

Flag to indicate that MongoDB environment repository configuration is enabled.

org.springframework.cloud.config.server.environment.MongoDbEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.mongodb.enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        mongodb: 
          enabled: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.mongodb.enabled="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_MONGODB_ENABLED="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.mongodb.enabled="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.mongodb.fail-on-error=true

Flag to determine how to handle query exceptions.

org.springframework.cloud.config.server.environment.MongoDbEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.mongodb.fail-on-error=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        mongodb: 
          fail-on-error: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.mongodb.fail-on-error="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_MONGODB_FAIL_ON_ERROR="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.mongodb.fail-on-error="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.mongodb.order=0

Order of the MongoDB environment repository.

org.springframework.cloud.config.server.environment.MongoDbEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.mongodb.order=0

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        mongodb: 
          order: "0"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.mongodb.order="0" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_MONGODB_ORDER="0"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.mongodb.order="0"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.native.add-label-locations=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        native: 
          add-label-locations: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.native.add-label-locations="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_NATIVE_ADD_LABEL_LOCATIONS="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.native.add-label-locations="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.native.default-label=master

org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.native.default-label=master

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        native: 
          default-label: "master"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.native.default-label="master" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_NATIVE_DEFAULT_LABEL="master"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.native.default-label="master"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.native.fail-on-error=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        native: 
          fail-on-error: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.native.fail-on-error="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_NATIVE_FAIL_ON_ERROR="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.native.fail-on-error="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.native.order=

org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.native.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        native: 
          order: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.native.order="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_NATIVE_ORDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.native.order="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.native.search-locations=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        native: 
          search-locations: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.native.search-locations="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_NATIVE_SEARCH_LOCATIONS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.native.search-locations="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.native.version=

Version string to be reported for native repository.

org.springframework.cloud.config.server.environment.NativeEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.native.version=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        native: 
          version: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.native.version="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_NATIVE_VERSION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.native.version="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.overrides=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        overrides: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.overrides="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_OVERRIDES="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.overrides="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.prefix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        prefix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.prefix="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_PREFIX="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.prefix="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.redis.order=

org.springframework.cloud.config.server.environment.RedisEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.redis.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        redis: 
          order: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.redis.order="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_REDIS_ORDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.redis.order="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.reverse-location-order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        reverse-location-order: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.reverse-location-order="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_REVERSE_LOCATION_ORDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.reverse-location-order="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.strip-document-from-yaml=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        strip-document-from-yaml: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.strip-document-from-yaml="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_STRIP_DOCUMENT_FROM_YAML="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.strip-document-from-yaml="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.svn.basedir=

Base directory for local working copy of repository.

org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.basedir=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          basedir: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.basedir="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_BASEDIR="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.basedir="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.svn.default-label=

The default label to be used with the remote repository.

org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.default-label=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          default-label: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.default-label="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_DEFAULT_LABEL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.default-label="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.svn.order=

The order of the environment repository.

org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          order: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.order="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_ORDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.order="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.svn.passphrase=

Passphrase for unlocking your ssh private key.

org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.passphrase=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          passphrase: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.passphrase="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_PASSPHRASE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.passphrase="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.svn.password=

Password for authentication with remote repository.

org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          password: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.password="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_PASSWORD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.password="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.search-paths=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          search-paths: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.search-paths="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_SEARCH_PATHS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.search-paths="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.strict-host-key-checking=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          strict-host-key-checking: "true"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.strict-host-key-checking="true" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_STRICT_HOST_KEY_CHECKING="true"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.strict-host-key-checking="true"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.svn.uri=

URI of remote repository.

org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.uri=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          uri: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.uri="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_URI="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.uri="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.svn.username=

Username for authentication with remote repository.

org.springframework.cloud.config.server.environment.SvnKitEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.svn.username=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        svn: 
          username: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.svn.username="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_SVN_USERNAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.svn.username="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.app-role.app-role-path=approle

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          app-role: 
            app-role-path: "approle"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.app-role.app-role-path="approle" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_APP_ROLE_APP_ROLE_PATH="approle"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.app-role.app-role-path="approle"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.app-role.role=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          app-role: 
            role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.app-role.role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_APP_ROLE_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.app-role.role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.app-role.role-id=

The RoleId.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AppRoleProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.app-role.role-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          app-role: 
            role-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.app-role.role-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_APP_ROLE_ROLE_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.app-role.role-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.app-role.secret-id=

The SecretId.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AppRoleProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.app-role.secret-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          app-role: 
            secret-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.app-role.secret-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_APP_ROLE_SECRET_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.app-role.secret-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.authentication=

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.authentication=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          authentication: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.authentication="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AUTHENTICATION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.authentication="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.aws-ec2.aws-ec2-path=aws-ec2

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          aws-ec2: 
            aws-ec2-path: "aws-ec2"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.aws-ec2.aws-ec2-path="aws-ec2" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AWS_EC2_AWS_EC2_PATH="aws-ec2"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.aws-ec2.aws-ec2-path="aws-ec2"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.aws-ec2.identity-document=http://169.254.169.254/latest/dynamic/instance-identity/pkcs7

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          aws-ec2: 
            identity-document: "http://169.254.169.254/latest/dynamic/instance-identity/pkcs7"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -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 properties can specified as system environment variables before the CAS web application is launched:

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

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.aws-ec2.identity-document="http://169.254.169.254/latest/dynamic/instance-identity/pkcs7"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.aws-ec2.nonce=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          aws-ec2: 
            nonce: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.aws-ec2.nonce="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AWS_EC2_NONCE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.aws-ec2.nonce="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.aws-ec2.role=

Name of the role, optional.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsEc2Properties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.aws-ec2.role=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          aws-ec2: 
            role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.aws-ec2.role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AWS_EC2_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.aws-ec2.role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.aws-iam.aws-path=aws

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          aws-iam: 
            aws-path: "aws"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.aws-iam.aws-path="aws" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AWS_IAM_AWS_PATH="aws"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.aws-iam.aws-path="aws"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.aws-iam.endpoint-uri=

STS server URI. @since 2.2

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AwsIamProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.aws-iam.endpoint-uri=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          aws-iam: 
            endpoint-uri: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.aws-iam.endpoint-uri="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AWS_IAM_ENDPOINT_URI="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.aws-iam.endpoint-uri="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.aws-iam.role=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          aws-iam: 
            role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.aws-iam.role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AWS_IAM_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.aws-iam.role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.aws-iam.server-name=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          aws-iam: 
            server-name: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.aws-iam.server-name="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AWS_IAM_SERVER_NAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.aws-iam.server-name="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.azure-msi.azure-path=azure

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          azure-msi: 
            azure-path: "azure"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.azure-msi.azure-path="azure" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AZURE_MSI_AZURE_PATH="azure"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.azure-msi.azure-path="azure"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.azure-msi.identity-token-service=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          azure-msi: 
            identity-token-service: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.azure-msi.identity-token-service="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AZURE_MSI_IDENTITY_TOKEN_SERVICE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.azure-msi.identity-token-service="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.azure-msi.metadata-service=

URI to the Azure MSI Metadata Service.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AzureMsiProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.azure-msi.metadata-service=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          azure-msi: 
            metadata-service: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.azure-msi.metadata-service="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AZURE_MSI_METADATA_SERVICE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.azure-msi.metadata-service="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.azure-msi.role=

Name of the role.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$AzureMsiProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.azure-msi.role=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          azure-msi: 
            role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.azure-msi.role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_AZURE_MSI_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.azure-msi.role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.backend=secret

Vault backend. Defaults to secret.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.backend=secret

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          backend: "secret"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.backend="secret" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_BACKEND="secret"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.backend="secret"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.default-key=application

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          default-key: "application"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.default-key="application" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_DEFAULT_KEY="application"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.default-key="application"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.default-label=main

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.default-label=main

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          default-label: "main"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.default-label="main" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_DEFAULT_LABEL="main"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.default-label="main"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.enable-label=false

Flag to indicate that the repository should use 'label' as well as 'application-name' and 'profile', for vault secrets. By default, the vault secrets are expected to be in 'application-name,profile' path. When this flag enabled, they are expected to be in `application-name,profile,label' path. To maintain compatibility this flag is not enabled by default.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.enable-label=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          enable-label: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.enable-label="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_ENABLE_LABEL="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.enable-label="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-gce.gcp-path=gcp

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-gce: 
            gcp-path: "gcp"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-gce.gcp-path="gcp" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_GCE_GCP_PATH="gcp"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-gce.gcp-path="gcp"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-gce.role=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-gce: 
            role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-gce.role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_GCE_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-gce.role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-gce.service-account=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-gce: 
            service-account: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-gce.service-account="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_GCE_SERVICE_ACCOUNT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-gce.service-account="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-iam.credentials.encoded-key=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-iam: 
            credentials: 
              encoded-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-iam.credentials.encoded-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_IAM_CREDENTIALS_ENCODED_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-iam.credentials.encoded-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-iam.credentials.location=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-iam: 
            credentials: 
              location: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-iam.credentials.location="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_IAM_CREDENTIALS_LOCATION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-iam.credentials.location="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-iam.gcp-path=gcp

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-iam: 
            gcp-path: "gcp"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-iam.gcp-path="gcp" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_IAM_GCP_PATH="gcp"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-iam.gcp-path="gcp"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.gcp-iam.jwt-validity=15m

Validity of the JWT token.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpIamProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-iam.jwt-validity=15m

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-iam: 
            jwt-validity: "15m"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-iam.jwt-validity="15m" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_IAM_JWT_VALIDITY="15m"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-iam.jwt-validity="15m"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.gcp-iam.project-id=

Overrides the GCP project Id.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpIamProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-iam.project-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-iam: 
            project-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-iam.project-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_IAM_PROJECT_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-iam.project-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-iam.role=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-iam: 
            role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-iam.role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_IAM_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-iam.role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.gcp-iam.service-account-id=

Overrides the GCP service account Id.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$GcpIamProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.gcp-iam.service-account-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          gcp-iam: 
            service-account-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.gcp-iam.service-account-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_GCP_IAM_SERVICE_ACCOUNT_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.gcp-iam.service-account-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.host=127.0.0.1

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          host: "127.0.0.1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.host="127.0.0.1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_HOST="127.0.0.1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.host="127.0.0.1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.kubernetes.kubernetes-path=kubernetes

Mount path of the Kubernetes authentication backend.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$KubernetesProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.kubernetes.kubernetes-path=kubernetes

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          kubernetes: 
            kubernetes-path: "kubernetes"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.kubernetes.kubernetes-path="kubernetes" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_KUBERNETES_KUBERNETES_PATH="kubernetes"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.kubernetes.kubernetes-path="kubernetes"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.kubernetes.role=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          kubernetes: 
            role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.kubernetes.role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_KUBERNETES_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.kubernetes.role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.kubernetes.service-account-token-file=/var/run/secrets/kubernetes.io/serviceaccount/token

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          kubernetes: 
            service-account-token-file: "/var/run/secrets/kubernetes.io/serviceaccount/token"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.kubernetes.service-account-token-file="/var/run/secrets/kubernetes.io/serviceaccount/token" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_KUBERNETES_SERVICE_ACCOUNT_TOKEN_FILE="/var/run/secrets/kubernetes.io/serviceaccount/token"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.kubernetes.service-account-token-file="/var/run/secrets/kubernetes.io/serviceaccount/token"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.kv-version=1

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          kv-version: "1"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.kv-version="1" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_KV_VERSION="1"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.kv-version="1"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.namespace=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          namespace: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.namespace="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_NAMESPACE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.namespace="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.order=

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.order=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          order: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.order="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_ORDER="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.order="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.path-to-key=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          path-to-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.path-to-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_PATH_TO_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.path-to-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.pcf.instance-certificate=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          pcf: 
            instance-certificate: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.pcf.instance-certificate="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_PCF_INSTANCE_CERTIFICATE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.pcf.instance-certificate="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.pcf.instance-key=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          pcf: 
            instance-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.pcf.instance-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_PCF_INSTANCE_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.pcf.instance-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.pcf.pcf-path=pcf

Mount path of the Kubernetes authentication backend.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$PcfProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.pcf.pcf-path=pcf

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          pcf: 
            pcf-path: "pcf"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.pcf.pcf-path="pcf" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_PCF_PCF_PATH="pcf"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.pcf.pcf-path="pcf"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.pcf.role=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          pcf: 
            role: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.pcf.role="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_PCF_ROLE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.pcf.role="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.port=8200

Vault port. Defaults to 8200.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.port=8200

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          port: "8200"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.port="8200" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_PORT="8200"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.port="8200"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.profile-separator=,

Vault profile separator. Defaults to comma.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.profile-separator=,

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          profile-separator: ","

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.profile-separator="," -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_PROFILE_SEPARATOR=","

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.profile-separator=","

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.proxy=

HTTP proxy configuration.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.proxy=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          proxy: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.proxy="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_PROXY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.proxy="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.scheme=http

Vault scheme. Defaults to http.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.scheme=http

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          scheme: "http"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.scheme="http" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_SCHEME="http"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.scheme="http"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.skip-ssl-validation=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          skip-ssl-validation: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.skip-ssl-validation="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_SKIP_SSL_VALIDATION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.skip-ssl-validation="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.ssl.cert-auth-path=cert

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          ssl: 
            cert-auth-path: "cert"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.ssl.cert-auth-path="cert" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_SSL_CERT_AUTH_PATH="cert"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.ssl.cert-auth-path="cert"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.ssl.key-store=

Trust store that holds certificates and private keys.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.ssl.key-store=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          ssl: 
            key-store: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.ssl.key-store="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_SSL_KEY_STORE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.ssl.key-store="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.ssl.key-store-password=

Password used to access the key store.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.ssl.key-store-password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          ssl: 
            key-store-password: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.ssl.key-store-password="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_SSL_KEY_STORE_PASSWORD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.ssl.key-store-password="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.ssl.trust-store=

Trust store that holds SSL certificates.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.ssl.trust-store=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          ssl: 
            trust-store: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.ssl.trust-store="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_SSL_TRUST_STORE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.ssl.trust-store="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.ssl.trust-store-password=

Password used to access the trust store.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties$Ssl.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.ssl.trust-store-password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          ssl: 
            trust-store-password: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.ssl.trust-store-password="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_SSL_TRUST_STORE_PASSWORD="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.ssl.trust-store-password="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

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.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.timeout=5

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          timeout: "5"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.timeout="5" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_TIMEOUT="5"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.timeout="5"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.server.vault.token=

Static vault token. Required if #authentication is TOKEN.

org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.server.vault.token=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      server: 
        vault: 
          token: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.server.vault.token="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_SERVER_VAULT_TOKEN="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.server.vault.token="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.tls=

TLS properties.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.tls=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      tls: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.tls="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_TLS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.tls="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.token=

Security Token passed thru to underlying environment repository.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.token=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      token: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.token="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_TOKEN="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.token="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.uri=http://localhost:8888

The URI of the remote server (default http://localhost:8888).

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.uri=http://localhost:8888

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      uri: "["http://localhost:8888"]"

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.uri="["http://localhost:8888"]" -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_URI="["http://localhost:8888"]"

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.uri="["http://localhost:8888"]"

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

spring.cloud.config.username=

The username to use (HTTP Basic) when contacting the remote server.

org.springframework.cloud.config.client.ConfigClientProperties.

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:

spring.cloud.config.username=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    config: 
      username: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dspring.cloud.config.username="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export SPRING_CLOUD_CONFIG_USERNAME="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --spring.cloud.config.username="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

# Flag to indicate that {@link #isOverrideSystemProperties() systemPropertiesOverride} can be used.
# spring.cloud.config.allow-override=true

# The charset to read the resource from the config server.
# spring.cloud.config.charset=UTF-8

# Flag to indicate that config server discovery is enabled (config server URL will be looked up via discovery).
# spring.cloud.config.discovery.enabled=false

# Service id to locate config server.
# spring.cloud.config.discovery.service-id=configserver

# Flag to say that remote configuration is enabled.
# spring.cloud.config.enabled=true

# Flag to indicate that failure to connect to the server is fatal (default false).
# spring.cloud.config.fail-fast=false

# Additional headers used to create the client request.
# spring.cloud.config.headers=

# Flag to initialize bootstrap configuration on context refresh event.
# spring.cloud.config.initialize-on-context-refresh=false

# The label name to use to pull remote configuration properties.
# spring.cloud.config.label=

# The Accept header media type to send to config server.
# spring.cloud.config.media-type=

# The strategy to use when call to server fails and there are multiple URLs configured on the uri property (default {@link MultipleUriStrategy#ALWAYS}).
# spring.cloud.config.multiple-uri-strategy=always

# Name of application used to fetch remote properties.
# spring.cloud.config.name=

# Flag to indicate that when {@link #setAllowOverride(boolean) allowOverride} is true, external properties should take lowest priority and should not override any existing property sources (including local config files).
# spring.cloud.config.override-none=false

# Flag to indicate that the external properties should override system properties.
# spring.cloud.config.override-system-properties=true

# The password to use (HTTP Basic) when contacting the remote server.
# spring.cloud.config.password=

# The default profile to use when fetching remote configuration (comma-separated).
# spring.cloud.config.profile=default

# timeout on waiting to connect to the Config Server.
# spring.cloud.config.request-connect-timeout=0

# timeout on waiting to read data from the Config Server.
# spring.cloud.config.request-read-timeout=0

# Initial retry interval in milliseconds.
# spring.cloud.config.retry.initial-interval=1000

# Maximum number of attempts.
# spring.cloud.config.retry.max-attempts=6

# Maximum interval for backoff.
# spring.cloud.config.retry.max-interval=2000

# Multiplier for next interval.
# spring.cloud.config.retry.multiplier=1.1

# Use a random exponential backoff policy.
# spring.cloud.config.retry.use-random-policy=false

# If set to true the client will send all labels to the server instead of sending one at a time.
# spring.cloud.config.send-all-labels=false

# Flag to indicate whether to send state.
# spring.cloud.config.send-state=true

# Flag to indicate that If HTTP 404 needs to be sent if Application is not Found.
# spring.cloud.config.server.accept-empty=true

# The default staging label to be used to fetch the secret values.
# spring.cloud.config.server.aws-secretsmanager.default-label=

# The endpoint to be used by AWS Secrets Manager client.
# spring.cloud.config.server.aws-secretsmanager.endpoint=

# Do not set staging label when fetching the secret values.
# spring.cloud.config.server.aws-secretsmanager.ignore-label=false

# The order of the environment repository.
# spring.cloud.config.server.aws-secretsmanager.order=

# Prefix which indicates the origin of the property.
# spring.cloud.config.server.aws-secretsmanager.origin=aws:secrets:

# Prefix indicating first level for every property loaded from AWS Secrets Manager.
# spring.cloud.config.server.aws-secretsmanager.prefix=

# String that separates profile from the application name.
# spring.cloud.config.server.aws-secretsmanager.profile-separator=-

# The region to be used by AWS Secrets Manager client.
# spring.cloud.config.server.aws-secretsmanager.region=

# Flag to indicate the retrieval of all AWS parameters in a hierarchy with their value decrypted.
# spring.cloud.config.server.awsparamstore.decrypt-values=true

# The service endpoint to be used by the AWS Parameter Store client.
# spring.cloud.config.server.awsparamstore.endpoint=

# The maximum number of items to return for an AWS Parameter Store API call.
# spring.cloud.config.server.awsparamstore.max-results=10

# The order of the environment repository.
# spring.cloud.config.server.awsparamstore.order=

# Prefix indicating the property's origin.
# spring.cloud.config.server.awsparamstore.origin=aws:ssm:parameter:

# Prefix indicating first level for every property loaded from the AWS Parameter Store.
# spring.cloud.config.server.awsparamstore.prefix=

# String that separates an appended profile from the context name.
# spring.cloud.config.server.awsparamstore.profile-separator=-

# Flag to indicate the retrieval of all AWS parameters within a hierarchy.
# spring.cloud.config.server.awsparamstore.recursive=true

# The region to be used by the AWS Parameter Store client.
# spring.cloud.config.server.awsparamstore.region=

# Name of the S3 bucket that contains config.
# spring.cloud.config.server.awss3.bucket=

# Adds the ability to override the baseUrl of the s3 client.
# spring.cloud.config.server.awss3.endpoint=

# 
# spring.cloud.config.server.awss3.order=0

# AWS region that contains config.
# spring.cloud.config.server.awss3.region=

# Flag indicating that the config server should initialize its own Environment with properties from the remote repository.
# spring.cloud.config.server.bootstrap=false

# 
# spring.cloud.config.server.credhub.ca-cert-files=

# 
# spring.cloud.config.server.credhub.connection-timeout=

# The default label to be used when is not provided by client applications.
# spring.cloud.config.server.credhub.default-label=master

# 
# spring.cloud.config.server.credhub.oauth2.registration-id=

# 
# spring.cloud.config.server.credhub.order=

# The common base path for credentials in CredHub.
# spring.cloud.config.server.credhub.path=

# 
# spring.cloud.config.server.credhub.read-timeout=

# 
# spring.cloud.config.server.credhub.url=

# Default application name when incoming requests do not have a specific one.
# spring.cloud.config.server.default-application-name=application

# Default repository label when incoming requests do not have a specific label.
# spring.cloud.config.server.default-label=

# Default application profile when incoming requests do not have a specific one.
# spring.cloud.config.server.default-profile=default

# Flag indicating config server is enabled.
# spring.cloud.config.server.enabled=true

# Enable decryption of environment properties before sending to client.
# spring.cloud.config.server.encrypt.enabled=true

# Enable decryption of environment properties served by plain text endpoint {@link org.springframework.cloud.config.server.resource.ResourceController}.
# spring.cloud.config.server.encrypt.plain-text-encrypt=false

# 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.
# spring.cloud.config.server.fail-on-composite-error=true

# 
# spring.cloud.config.server.gcp-secret-manager.application-label=application

# 
# spring.cloud.config.server.gcp-secret-manager.order=

# 
# spring.cloud.config.server.gcp-secret-manager.profile-label=profile

# 
# spring.cloud.config.server.gcp-secret-manager.service-account=

# 
# spring.cloud.config.server.gcp-secret-manager.token-mandatory=true

# 
# spring.cloud.config.server.gcp-secret-manager.version=1

# Base directory for local working copy of repository.
# spring.cloud.config.server.git.basedir=

# Flag to indicate that the repository should be cloned on startup (not on demand).
# spring.cloud.config.server.git.clone-on-start=false

# Flag to indicate that the submodules in the repository should be cloned.
# spring.cloud.config.server.git.clone-submodules=false

# The default label to be used with the remote repository.
# spring.cloud.config.server.git.default-label=

# Flag to indicate that the branch should be deleted locally if it's origin tracked branch was removed.
# spring.cloud.config.server.git.delete-untracked-branches=false

# Flag to indicate that the repository should force pull.
# spring.cloud.config.server.git.force-pull=false

# Valid SSH host key.
# spring.cloud.config.server.git.host-key=

# One of ssh-dss, ssh-rsa, ssh-ed25519, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, or ecdsa-sha2-nistp521.
# spring.cloud.config.server.git.host-key-algorithm=

# If true, use property-based instead of file-based SSH config.
# spring.cloud.config.server.git.ignore-local-ssh-settings=false

# Location of custom .known_hosts file.
# spring.cloud.config.server.git.known-hosts-file=

# The order of the environment repository.
# spring.cloud.config.server.git.order=

# Passphrase for unlocking your ssh private key.
# spring.cloud.config.server.git.passphrase=

# Password for authentication with remote repository.
# spring.cloud.config.server.git.password=

# Override server authentication method order.
# spring.cloud.config.server.git.preferred-authentications=

# Valid SSH private key.
# spring.cloud.config.server.git.private-key=

# HTTP proxy configuration.
# spring.cloud.config.server.git.proxy=

# Time (in seconds) between refresh of the git repository.
# spring.cloud.config.server.git.refresh-rate=0

# Map of repository identifier to location and other properties.
# spring.cloud.config.server.git.repos=

# Search paths to use within local working copy.
# spring.cloud.config.server.git.search-paths=

# Flag to indicate that SSL certificate validation should be bypassed when communicating with a repository served over an HTTPS connection.
# spring.cloud.config.server.git.skip-ssl-validation=false

# If false, ignore errors with host key.
# spring.cloud.config.server.git.strict-host-key-checking=true

# Timeout (in seconds) for obtaining HTTP or SSH connection (if applicable), defaults to 5 seconds.
# spring.cloud.config.server.git.timeout=5

# To maintain compatibility we will try the master branch in addition to main when we try to fetch the default branch.
# spring.cloud.config.server.git.try-master-branch=true

# URI of remote repository.
# spring.cloud.config.server.git.uri=

# Username for authentication with remote repository.
# spring.cloud.config.server.git.username=

# 
# spring.cloud.config.server.health.down-health-status=

# 
# spring.cloud.config.server.health.repositories=

# 
# spring.cloud.config.server.jdbc.default-label=master

# Flag to indicate that JDBC environment repository configuration is enabled.
# spring.cloud.config.server.jdbc.enabled=true

# Flag to determine how to handle query exceptions.
# spring.cloud.config.server.jdbc.fail-on-error=true

# 
# spring.cloud.config.server.jdbc.order=0

# SQL used to query database for keys and values.
# 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 when profile is null.
# spring.cloud.config.server.jdbc.sql-without-profile=SELECT "KEY", "VALUE" from PROPERTIES where APPLICATION=? and PROFILE is null and LABEL=?

# Name of the MongoDB collection to query for configuration properties.
# spring.cloud.config.server.mongodb.collection=properties

# Default label to use if none is specified.
# spring.cloud.config.server.mongodb.default-label=master

# Flag to indicate that MongoDB environment repository configuration is enabled.
# spring.cloud.config.server.mongodb.enabled=true

# Flag to determine how to handle query exceptions.
# spring.cloud.config.server.mongodb.fail-on-error=true

# Order of the MongoDB environment repository.
# spring.cloud.config.server.mongodb.order=0

# Flag to determine whether label locations should be added.
# spring.cloud.config.server.native.add-label-locations=true

# 
# spring.cloud.config.server.native.default-label=master

# Flag to determine how to handle exceptions during decryption (default false).
# spring.cloud.config.server.native.fail-on-error=false

# 
# spring.cloud.config.server.native.order=

# Locations to search for configuration files.
# spring.cloud.config.server.native.search-locations=

# Version string to be reported for native repository.
# spring.cloud.config.server.native.version=

# Extra map for a property source to be sent to all clients unconditionally.
# spring.cloud.config.server.overrides=

# Prefix for configuration resource paths (default is empty).
# spring.cloud.config.server.prefix=

# 
# spring.cloud.config.server.redis.order=

# By default the location order we use in GenericResourceRepository is the order in which they are listed.
# spring.cloud.config.server.reverse-location-order=false

# Flag to indicate that YAML documents that are text or collections (not a map) should be returned in "native" form.
# spring.cloud.config.server.strip-document-from-yaml=true

# Base directory for local working copy of repository.
# spring.cloud.config.server.svn.basedir=

# The default label to be used with the remote repository.
# spring.cloud.config.server.svn.default-label=

# The order of the environment repository.
# spring.cloud.config.server.svn.order=

# Passphrase for unlocking your ssh private key.
# spring.cloud.config.server.svn.passphrase=

# Password for authentication with remote repository.
# spring.cloud.config.server.svn.password=

# Search paths to use within local working copy.
# spring.cloud.config.server.svn.search-paths=

# Reject incoming SSH host keys from remote servers not in the known host list.
# spring.cloud.config.server.svn.strict-host-key-checking=true

# URI of remote repository.
# spring.cloud.config.server.svn.uri=

# Username for authentication with remote repository.
# spring.cloud.config.server.svn.username=

# Mount path of the AppRole authentication backend.
# spring.cloud.config.server.vault.app-role.app-role-path=approle

# Name of the role, optional, used for pull-mode.
# spring.cloud.config.server.vault.app-role.role=

# The RoleId.
# spring.cloud.config.server.vault.app-role.role-id=

# The SecretId.
# spring.cloud.config.server.vault.app-role.secret-id=

# 
# spring.cloud.config.server.vault.authentication=

# Mount path of the AWS-EC2 authentication backend.
# spring.cloud.config.server.vault.aws-ec2.aws-ec2-path=aws-ec2

# URL of the AWS-EC2 PKCS7 identity document.
# spring.cloud.config.server.vault.aws-ec2.identity-document=http://169.254.169.254/latest/dynamic/instance-identity/pkcs7

# Nonce used for AWS-EC2 authentication.
# spring.cloud.config.server.vault.aws-ec2.nonce=

# Name of the role, optional.
# spring.cloud.config.server.vault.aws-ec2.role=

# Mount path of the AWS authentication backend.
# spring.cloud.config.server.vault.aws-iam.aws-path=aws

# STS server URI.
# spring.cloud.config.server.vault.aws-iam.endpoint-uri=

# Name of the role, optional.
# spring.cloud.config.server.vault.aws-iam.role=

# Name of the server used to set {@code X-Vault-AWS-IAM-Server-ID} header in the headers of login requests.
# spring.cloud.config.server.vault.aws-iam.server-name=

# Mount path of the Azure MSI authentication backend.
# spring.cloud.config.server.vault.azure-msi.azure-path=azure

# URI to the Azure MSI Identity Service.
# spring.cloud.config.server.vault.azure-msi.identity-token-service=

# URI to the Azure MSI Metadata Service.
# spring.cloud.config.server.vault.azure-msi.metadata-service=

# Name of the role.
# spring.cloud.config.server.vault.azure-msi.role=

# Vault backend.
# spring.cloud.config.server.vault.backend=secret

# The key in vault shared by all applications.
# spring.cloud.config.server.vault.default-key=application

# 
# spring.cloud.config.server.vault.default-label=main

# Flag to indicate that the repository should use 'label' as well as 'application-name' and 'profile', for vault secrets.
# spring.cloud.config.server.vault.enable-label=false

# Mount path of the Kubernetes authentication backend.
# spring.cloud.config.server.vault.gcp-gce.gcp-path=gcp

# Name of the role against which the login is being attempted.
# spring.cloud.config.server.vault.gcp-gce.role=

# Optional service account id.
# spring.cloud.config.server.vault.gcp-gce.service-account=

# The base64 encoded contents of an OAuth2 account private key in JSON format.
# spring.cloud.config.server.vault.gcp-iam.credentials.encoded-key=

# Location of the OAuth2 credentials private key.
# spring.cloud.config.server.vault.gcp-iam.credentials.location=

# Mount path of the Kubernetes authentication backend.
# spring.cloud.config.server.vault.gcp-iam.gcp-path=gcp

# Validity of the JWT token.
# spring.cloud.config.server.vault.gcp-iam.jwt-validity=15m

# Overrides the GCP project Id.
# spring.cloud.config.server.vault.gcp-iam.project-id=

# Name of the role against which the login is being attempted.
# spring.cloud.config.server.vault.gcp-iam.role=

# Overrides the GCP service account Id.
# spring.cloud.config.server.vault.gcp-iam.service-account-id=

# Vault host.
# spring.cloud.config.server.vault.host=127.0.0.1

# Mount path of the Kubernetes authentication backend.
# spring.cloud.config.server.vault.kubernetes.kubernetes-path=kubernetes

# Name of the role against which the login is being attempted.
# spring.cloud.config.server.vault.kubernetes.role=

# Path to the service account token file.
# spring.cloud.config.server.vault.kubernetes.service-account-token-file=/var/run/secrets/kubernetes.io/serviceaccount/token

# Value to indicate which version of Vault kv backend is used.
# spring.cloud.config.server.vault.kv-version=1

# The value of the Vault X-Vault-Namespace header.
# spring.cloud.config.server.vault.namespace=

# 
# spring.cloud.config.server.vault.order=

# KV2 API required "data" after "mount-path".
# spring.cloud.config.server.vault.path-to-key=

# Path to the instance certificate (PEM).
# spring.cloud.config.server.vault.pcf.instance-certificate=

# Path to the instance key (PEM).
# spring.cloud.config.server.vault.pcf.instance-key=

# Mount path of the Kubernetes authentication backend.
# spring.cloud.config.server.vault.pcf.pcf-path=pcf

# Name of the role against which the login is being attempted.
# spring.cloud.config.server.vault.pcf.role=

# Vault port.
# spring.cloud.config.server.vault.port=8200

# Vault profile separator.
# spring.cloud.config.server.vault.profile-separator=,

# HTTP proxy configuration.
# spring.cloud.config.server.vault.proxy=

# Vault scheme.
# spring.cloud.config.server.vault.scheme=http

# Flag to indicate that SSL certificate validation should be bypassed when communicating with a repository served over an HTTPS connection.
# spring.cloud.config.server.vault.skip-ssl-validation=false

# Mount path of the TLS cert authentication backend.
# spring.cloud.config.server.vault.ssl.cert-auth-path=cert

# Trust store that holds certificates and private keys.
# spring.cloud.config.server.vault.ssl.key-store=

# Password used to access the key store.
# spring.cloud.config.server.vault.ssl.key-store-password=

# Trust store that holds SSL certificates.
# spring.cloud.config.server.vault.ssl.trust-store=

# Password used to access the trust store.
# spring.cloud.config.server.vault.ssl.trust-store-password=

# Timeout (in seconds) for obtaining HTTP connection, defaults to 5 seconds.
# spring.cloud.config.server.vault.timeout=5

# Static vault token.
# spring.cloud.config.server.vault.token=

# TLS properties.
# spring.cloud.config.tls=

# Security Token passed thru to underlying environment repository.
# spring.cloud.config.token=

# The URI of the remote server (default http://localhost:8888).
# spring.cloud.config.uri=["http://localhost:8888"]

# The username to use (HTTP Basic) when contacting the remote server.
# spring.cloud.config.username=

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note