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.

Spring Cloud Configuration Server - Spring Cloud Azure KeyVault

Spring Cloud Configuration Server is able to use Microsoft Azure’s KeyVault Secrets to locate properties and settings. Support is provided via the following dependency in the WAR overlay:

<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-configuration-cloud-azure-keyvault</artifactId>
    <version>${cas.version}</version>
</dependency>

implementation "org.apereo.cas:cas-server-support-configuration-cloud-azure-keyvault:${project.'cas.version'}"

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

dependencies {
    implementation "org.apereo.cas:cas-server-support-configuration-cloud-azure-keyvault"
}

dependencies {
    /*
    The following platform references should be included automatically and are listed here for reference only.
            
    implementation enforcedPlatform("org.apereo.cas:cas-server-support-bom:${project.'cas.version'}")
    implementation platform(org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES)
    */

    implementation "org.apereo.cas:cas-server-support-configuration-cloud-azure-keyvault"
}

IMPORTANT: The allowed name pattern in Azure Key Vault is ^[0-9a-zA-Z-]+$. For properties that contain that contain . in the name (i.e. cas.some.property), replace . with - when you store the setting in Azure Key Vault (i.e. cas-some-property). The module will handle the transformation for you.

Usage

The configuration modules provided here may also be used verbatim inside a CAS server overlay and do not exclusively belong to a Spring Cloud Configuration server. While this module is primarily useful when inside the Spring Cloud Configuration server, it nonetheless may also be used inside a CAS server overlay directly to fetch settings from a source.

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

_{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.azure.keyvault.secret.challenge-resource-verification-enabled=true

Whether to enable the Azure Key Vault challenge resource verification, default: true. Calls the disableChallengeResourceVerification method of the Azure Key Vault Client Builder when set to false.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultSecretProperties.

_{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:

spring.cloud.azure.keyvault.secret.challenge-resource-verification-enabled=true

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

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          challenge-resource-verification-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.azure.keyvault.secret.challenge-resource-verification-enabled="true" -jar build/libs/cas.war

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

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CHALLENGE_RESOURCE_VERIFICATION_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.azure.keyvault.secret.challenge-resource-verification-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.azure.keyvault.secret.client.application-id=

Represents current application and is used for telemetry/monitoring purposes.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.application-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            application-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.azure.keyvault.secret.client.application-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_APPLICATION_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.azure.keyvault.secret.client.application-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.azure.keyvault.secret.client.connect-timeout=

Amount of time(Duration) the request attempts to connect to the remote host and the connection is resolved.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.connect-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            connect-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.azure.keyvault.secret.client.connect-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_CONNECT_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.azure.keyvault.secret.client.connect-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.azure.keyvault.secret.client.connection-idle-timeout=

Amount of time(Duration) before an idle connection.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.connection-idle-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            connection-idle-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.azure.keyvault.secret.client.connection-idle-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_CONNECTION_IDLE_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.azure.keyvault.secret.client.connection-idle-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.azure.keyvault.secret.client.headers=

List of headers applied to each request sent with client. For instance, '"myCustomHeader", "myStaticValue"'.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.headers=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            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.azure.keyvault.secret.client.headers="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_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.azure.keyvault.secret.client.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.azure.keyvault.secret.client.headers[0].name=

The name of the header.

com.azure.spring.cloud.core.properties.client.HeaderProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.headers[0].name=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            headers[0]: 
              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.azure.keyvault.secret.client.headers[0].name="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_HEADERS[0]_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.azure.keyvault.secret.client.headers[0].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.azure.keyvault.secret.client.headers[0].values=

List of values of the header.

com.azure.spring.cloud.core.properties.client.HeaderProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.headers[0].values=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            headers[0]: 
              values: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.client.headers[0].values="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_HEADERS[0]_VALUES="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.headers[0].values="..."

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

spring.cloud.azure.keyvault.secret.client.logging.allowed-header-names=

Comma-delimited list of allowlist headers that should be logged. The default value is `"x-ms-request-id","x-ms-client-request-id","x-ms-return-client-request-id","traceparent","MS-CV","Accept","Cache-Control","Connection","Content-Length","Content-Type","Date","ETag","Expires","If-Match","If-Modified-Since","If-None-Match","If-Unmodified-Since","Last-Modified","Pragma","Request-Id","Retry-After","Server","Transfer-Encoding","User-Agent","WWW-Authenticate"`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpLoggingConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.logging.allowed-header-names=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            logging: 
              allowed-header-names: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.client.logging.allowed-header-names="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_LOGGING_ALLOWED_HEADER_NAMES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.client.logging.allowed-header-names="..."

The above example assumes 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.azure.keyvault.secret.client.logging.allowed-query-param-names=

Comma-delimited list of allowlist query parameters. The default value is `"api-version"`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpLoggingConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.logging.allowed-query-param-names=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            logging: 
              allowed-query-param-names: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.client.logging.allowed-query-param-names="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_LOGGING_ALLOWED_QUERY_PARAM_NAMES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.client.logging.allowed-query-param-names="..."

The above example assumes 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.azure.keyvault.secret.client.logging.level=

The level of detail to log on HTTP messages. Supported types are: NONE, BASIC, HEADERS, BODY, BODY_AND_HEADERS. The default value is `NONE`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpLoggingConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.logging.level=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            logging: 
              level: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.client.logging.level="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_LOGGING_LEVEL="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.client.logging.level="..."

The above example assumes 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.azure.keyvault.secret.client.logging.pretty-print-body=

Whether to pretty print the message bodies. The default value is `false`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpLoggingConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.logging.pretty-print-body=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            logging: 
              pretty-print-body: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.client.logging.pretty-print-body="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_LOGGING_PRETTY_PRINT_BODY="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.client.logging.pretty-print-body="..."

The above example assumes 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.azure.keyvault.secret.client.maximum-connection-pool-size=

Maximum connection pool size used by the underlying HTTP client.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.maximum-connection-pool-size=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            maximum-connection-pool-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.client.maximum-connection-pool-size="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_MAXIMUM_CONNECTION_POOL_SIZE="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.client.maximum-connection-pool-size="..."

The above example assumes 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.azure.keyvault.secret.client.read-timeout=

Amount of time(Duration) used when reading the server response.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.read-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            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.azure.keyvault.secret.client.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_AZURE_KEYVAULT_SECRET_CLIENT_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.azure.keyvault.secret.client.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.azure.keyvault.secret.client.response-timeout=

Amount of time(Duration) used when waiting for a server to reply.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.response-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            response-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.azure.keyvault.secret.client.response-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_RESPONSE_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.azure.keyvault.secret.client.response-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.azure.keyvault.secret.client.write-timeout=

Amount of time(Duration) each request being sent over the wire.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.client.write-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          client: 
            write-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.azure.keyvault.secret.client.write-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_WRITE_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.azure.keyvault.secret.client.write-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.azure.keyvault.secret.credential.client-certificate-password=

Password of the certificate file.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.credential.client-certificate-password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          credential: 
            client-certificate-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.azure.keyvault.secret.credential.client-certificate-password="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_CLIENT_CERTIFICATE_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.azure.keyvault.secret.credential.client-certificate-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.azure.keyvault.secret.credential.client-certificate-path=

Path of a PEM certificate file to use when performing service principal authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.credential.client-certificate-path=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          credential: 
            client-certificate-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.azure.keyvault.secret.credential.client-certificate-path="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_CLIENT_CERTIFICATE_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.azure.keyvault.secret.credential.client-certificate-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.azure.keyvault.secret.credential.client-id=

Client ID to use when performing service principal authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.credential.client-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          credential: 
            client-id: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.credential.client-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_CLIENT_ID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.client-id="..."

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

spring.cloud.azure.keyvault.secret.credential.client-secret=

Client secret to use when performing service principal authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.credential.client-secret=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          credential: 
            client-secret: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.credential.client-secret="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_CLIENT_SECRET="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.client-secret="..."

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

spring.cloud.azure.keyvault.secret.credential.managed-identity-enabled=false

Whether to enable managed identity to authenticate with Azure. If true and the client-id is set, will use the client ID as user assigned managed identity client ID.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.credential.managed-identity-enabled=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          credential: 
            managed-identity-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.azure.keyvault.secret.credential.managed-identity-enabled="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_MANAGED_IDENTITY_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.azure.keyvault.secret.credential.managed-identity-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.azure.keyvault.secret.credential.password=

Password to use when performing username/password authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.credential.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          credential: 
            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.azure.keyvault.secret.credential.password="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_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.azure.keyvault.secret.credential.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.azure.keyvault.secret.credential.username=

Username to use when performing username/password authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.credential.username=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          credential: 
            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.azure.keyvault.secret.credential.username="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_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.azure.keyvault.secret.credential.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.azure.keyvault.secret.enabled=true

Whether an Azure Service is enabled.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultSecretProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          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.azure.keyvault.secret.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_AZURE_KEYVAULT_SECRET_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.azure.keyvault.secret.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.azure.keyvault.secret.endpoint=

Azure Key Vault endpoint. For instance, 'https://{your-unique-keyvault-name}.vault.azure.net/'.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultSecretProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          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.azure.keyvault.secret.endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_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.azure.keyvault.secret.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.azure.keyvault.secret.profile.cloud-type=

Name of the Azure cloud to connect to. Supported types are: AZURE, AZURE_CHINA, AZURE_US_GOVERNMENT, OTHER. The default value is `AZURE`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.cloud-type=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            cloud-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.azure.keyvault.secret.profile.cloud-type="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_CLOUD_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.azure.keyvault.secret.profile.cloud-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.azure.keyvault.secret.profile.environment.active-directory-endpoint=

The Azure Active Directory endpoint to connect to.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.active-directory-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              active-directory-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.azure.keyvault.secret.profile.environment.active-directory-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_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.azure.keyvault.secret.profile.environment.active-directory-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.azure.keyvault.secret.profile.environment.active-directory-graph-api-version=

The Azure Active Directory Graph API version.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.active-directory-graph-api-version=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              active-directory-graph-api-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.azure.keyvault.secret.profile.environment.active-directory-graph-api-version="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_GRAPH_API_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.azure.keyvault.secret.profile.environment.active-directory-graph-api-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.azure.keyvault.secret.profile.environment.active-directory-graph-endpoint=

The Azure Active Directory Graph endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.active-directory-graph-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              active-directory-graph-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.azure.keyvault.secret.profile.environment.active-directory-graph-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_GRAPH_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.azure.keyvault.secret.profile.environment.active-directory-graph-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.azure.keyvault.secret.profile.environment.active-directory-resource-id=

The Azure Active Directory resource ID.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.active-directory-resource-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              active-directory-resource-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.azure.keyvault.secret.profile.environment.active-directory-resource-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_RESOURCE_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.azure.keyvault.secret.profile.environment.active-directory-resource-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.azure.keyvault.secret.profile.environment.azure-application-insights-endpoint=

The Azure Application Insights endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.azure-application-insights-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              azure-application-insights-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.azure.keyvault.secret.profile.environment.azure-application-insights-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_AZURE_APPLICATION_INSIGHTS_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.azure.keyvault.secret.profile.environment.azure-application-insights-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.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix=

The Data Lake analytics catalog and job endpoint suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              azure-data-lake-analytics-catalog-and-job-endpoint-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_AZURE_DATA_LAKE_ANALYTICS_CATALOG_AND_JOB_ENDPOINT_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix="..."

The above example assumes 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.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix=

The Data Lake storage file system endpoint suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              azure-data-lake-store-file-system-endpoint-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_AZURE_DATA_LAKE_STORE_FILE_SYSTEM_ENDPOINT_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix="..."

The above example assumes 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.azure.keyvault.secret.profile.environment.azure-log-analytics-endpoint=

The Azure Log Analytics endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.azure-log-analytics-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              azure-log-analytics-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.azure.keyvault.secret.profile.environment.azure-log-analytics-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_AZURE_LOG_ANALYTICS_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.azure.keyvault.secret.profile.environment.azure-log-analytics-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.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-id=

The Data Lake endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              data-lake-endpoint-resource-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.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_DATA_LAKE_ENDPOINT_RESOURCE_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.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-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.azure.keyvault.secret.profile.environment.gallery-endpoint=

The gallery endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.gallery-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              gallery-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.azure.keyvault.secret.profile.environment.gallery-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_GALLERY_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.azure.keyvault.secret.profile.environment.gallery-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.azure.keyvault.secret.profile.environment.key-vault-dns-suffix=

The Key Vault DNS suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.key-vault-dns-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              key-vault-dns-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.profile.environment.key-vault-dns-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_KEY_VAULT_DNS_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.profile.environment.key-vault-dns-suffix="..."

The above example assumes 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.azure.keyvault.secret.profile.environment.management-endpoint=

The management service endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.management-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              management-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.azure.keyvault.secret.profile.environment.management-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_MANAGEMENT_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.azure.keyvault.secret.profile.environment.management-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.azure.keyvault.secret.profile.environment.microsoft-graph-endpoint=

The Microsoft Graph endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.microsoft-graph-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              microsoft-graph-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.azure.keyvault.secret.profile.environment.microsoft-graph-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_MICROSOFT_GRAPH_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.azure.keyvault.secret.profile.environment.microsoft-graph-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.azure.keyvault.secret.profile.environment.portal=

The management portal URL.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.portal=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              portal: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.profile.environment.portal="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_PORTAL="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.profile.environment.portal="..."

The above example assumes 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.azure.keyvault.secret.profile.environment.publishing-profile=

The publishing settings file URL.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.publishing-profile=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              publishing-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.azure.keyvault.secret.profile.environment.publishing-profile="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_PUBLISHING_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.azure.keyvault.secret.profile.environment.publishing-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.azure.keyvault.secret.profile.environment.resource-manager-endpoint=

The resource management endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.resource-manager-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              resource-manager-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.azure.keyvault.secret.profile.environment.resource-manager-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_RESOURCE_MANAGER_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.azure.keyvault.secret.profile.environment.resource-manager-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.azure.keyvault.secret.profile.environment.service-bus-domain-name=

The domain name for Service Bus.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.service-bus-domain-name=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              service-bus-domain-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.azure.keyvault.secret.profile.environment.service-bus-domain-name="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_SERVICE_BUS_DOMAIN_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.azure.keyvault.secret.profile.environment.service-bus-domain-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.azure.keyvault.secret.profile.environment.sql-management-endpoint=

The SQL management endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.sql-management-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              sql-management-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.azure.keyvault.secret.profile.environment.sql-management-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_SQL_MANAGEMENT_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.azure.keyvault.secret.profile.environment.sql-management-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.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix=

The SQL Server hostname suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              sql-server-hostname-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_SQL_SERVER_HOSTNAME_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix="..."

The above example assumes 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.azure.keyvault.secret.profile.environment.storage-endpoint-suffix=

The Storage endpoint suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.environment.storage-endpoint-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            environment: 
              storage-endpoint-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.profile.environment.storage-endpoint-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_STORAGE_ENDPOINT_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.profile.environment.storage-endpoint-suffix="..."

The above example assumes 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.azure.keyvault.secret.profile.subscription-id=

Subscription ID to use when connecting to Azure resources.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.subscription-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            subscription-id: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.profile.subscription-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_SUBSCRIPTION_ID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.subscription-id="..."

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

spring.cloud.azure.keyvault.secret.profile.tenant-id=

Tenant ID for Azure resources.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.profile.tenant-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          profile: 
            tenant-id: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.profile.tenant-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_TENANT_ID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.tenant-id="..."

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

spring.cloud.azure.keyvault.secret.property-source-enabled=true

Whether to enable the Key Vault property source.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultSecretProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-source-enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-source-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.azure.keyvault.secret.property-source-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_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCE_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.azure.keyvault.secret.property-source-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.azure.keyvault.secret.property-sources=

List of Azure Key Vault property sources. For instance, ' property-sources[0].name=key-vault-property-source-1, property-sources[0].endpoint={ENDPOINT_1}, property-sources[1].name=key-vault-property-source-2, property-sources[1].endpoint={ENDPOINT_2} '.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultSecretProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].case-sensitive=

Whether to enable case-sensitive for secret keys. The default value is `false`.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultPropertySourceProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].case-sensitive=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            case-sensitive: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].case-sensitive="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CASE_SENSITIVE="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].case-sensitive="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].challenge-resource-verification-enabled=true

Whether to enable the Azure Key Vault challenge resource verification, default: true. Calls the disableChallengeResourceVerification method of the Azure Key Vault Client Builder when set to false.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultPropertySourceProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].challenge-resource-verification-enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            challenge-resource-verification-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.azure.keyvault.secret.property-sources[0].challenge-resource-verification-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_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CHALLENGE_RESOURCE_VERIFICATION_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.azure.keyvault.secret.property-sources[0].challenge-resource-verification-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.azure.keyvault.secret.property-sources[0].client.application-id=

Represents current application and is used for telemetry/monitoring purposes.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.ClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.application-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              application-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.azure.keyvault.secret.property-sources[0].client.application-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_APPLICATION_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.azure.keyvault.secret.property-sources[0].client.application-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.azure.keyvault.secret.property-sources[0].client.connect-timeout=

Amount of time(Duration) the request attempts to connect to the remote host and the connection is resolved.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.connect-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              connect-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.azure.keyvault.secret.property-sources[0].client.connect-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_CONNECT_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.azure.keyvault.secret.property-sources[0].client.connect-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.azure.keyvault.secret.property-sources[0].client.connection-idle-timeout=

Amount of time(Duration) before an idle connection.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.connection-idle-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              connection-idle-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.azure.keyvault.secret.property-sources[0].client.connection-idle-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_CONNECTION_IDLE_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.azure.keyvault.secret.property-sources[0].client.connection-idle-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.azure.keyvault.secret.property-sources[0].client.headers[0].name=

The name of the header.

com.azure.spring.cloud.core.properties.client.HeaderProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.headers[0].name=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              headers[0]: 
                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.azure.keyvault.secret.property-sources[0].client.headers[0].name="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_HEADERS[0]_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.azure.keyvault.secret.property-sources[0].client.headers[0].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.azure.keyvault.secret.property-sources[0].client.headers[0].values=

List of values of the header.

com.azure.spring.cloud.core.properties.client.HeaderProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.headers[0].values=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              headers[0]: 
                values: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].values="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_HEADERS[0]_VALUES="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].values="..."

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

spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names=

Comma-delimited list of allowlist headers that should be logged. The default value is `'x-ms-request-id','x-ms-client-request-id','x-ms-return-client-request-id','traceparent','MS-CV','Accept','Cache-Control','Connection','Content-Length','Content-Type','Date','ETag','Expires','If-Match','If-Modified-Since','If-None-Match','If-Unmodified-Since','Last-Modified','Pragma','Request-Id','Retry-After','Server','Transfer-Encoding','User-Agent','WWW-Authenticate'`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpLoggingConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              logging: 
                allowed-header-names: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_LOGGING_ALLOWED_HEADER_NAMES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names=

Comma-delimited list of allowlist query parameters. The default value is `'api-version'`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpLoggingConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              logging: 
                allowed-query-param-names: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_LOGGING_ALLOWED_QUERY_PARAM_NAMES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].client.logging.level=

The level of detail to log on HTTP messages. Supported types are: NONE, BASIC, HEADERS, BODY, BODY_AND_HEADERS. The default value is `NONE`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpLoggingConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.logging.level=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              logging: 
                level: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].client.logging.level="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_LOGGING_LEVEL="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].client.logging.level="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body=

Whether to pretty print the message bodies. The default value is `false`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpLoggingConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              logging: 
                pretty-print-body: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_LOGGING_PRETTY_PRINT_BODY="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size=

Maximum connection pool size used by the underlying HTTP client.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              maximum-connection-pool-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_MAXIMUM_CONNECTION_POOL_SIZE="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].client.read-timeout=

Amount of time(Duration) used when reading the server response.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.read-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              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.azure.keyvault.secret.property-sources[0].client.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_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_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.azure.keyvault.secret.property-sources[0].client.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.azure.keyvault.secret.property-sources[0].client.response-timeout=

Amount of time(Duration) used when waiting for a server to reply.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.response-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              response-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.azure.keyvault.secret.property-sources[0].client.response-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_RESPONSE_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.azure.keyvault.secret.property-sources[0].client.response-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.azure.keyvault.secret.property-sources[0].client.write-timeout=

Amount of time(Duration) each request being sent over the wire.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.client.HttpClientConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].client.write-timeout=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            client: 
              write-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.azure.keyvault.secret.property-sources[0].client.write-timeout="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_WRITE_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.azure.keyvault.secret.property-sources[0].client.write-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.azure.keyvault.secret.property-sources[0].credential.client-certificate-password=

Password of the certificate file.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].credential.client-certificate-password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            credential: 
              client-certificate-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.azure.keyvault.secret.property-sources[0].credential.client-certificate-password="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_CLIENT_CERTIFICATE_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.azure.keyvault.secret.property-sources[0].credential.client-certificate-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.azure.keyvault.secret.property-sources[0].credential.client-certificate-path=

Path of a PEM certificate file to use when performing service principal authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].credential.client-certificate-path=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            credential: 
              client-certificate-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.azure.keyvault.secret.property-sources[0].credential.client-certificate-path="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_CLIENT_CERTIFICATE_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.azure.keyvault.secret.property-sources[0].credential.client-certificate-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.azure.keyvault.secret.property-sources[0].credential.client-id=

Client ID to use when performing service principal authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].credential.client-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            credential: 
              client-id: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.client-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_CLIENT_ID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-id="..."

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

spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-secret=

Client secret to use when performing service principal authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].credential.client-secret=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            credential: 
              client-secret: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.client-secret="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_CLIENT_SECRET="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-secret="..."

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

spring.cloud.azure.keyvault.secret.property-sources[0].credential.managed-identity-enabled=false

Whether to enable managed identity to authenticate with Azure. If true and the client-id is set, will use the client ID as user assigned managed identity client ID.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].credential.managed-identity-enabled=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            credential: 
              managed-identity-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.azure.keyvault.secret.property-sources[0].credential.managed-identity-enabled="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_MANAGED_IDENTITY_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.azure.keyvault.secret.property-sources[0].credential.managed-identity-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.azure.keyvault.secret.property-sources[0].credential.password=

Password to use when performing username/password authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].credential.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            credential: 
              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.azure.keyvault.secret.property-sources[0].credential.password="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_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.azure.keyvault.secret.property-sources[0].credential.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.azure.keyvault.secret.property-sources[0].credential.username=

Username to use when performing username/password authentication with Azure.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.authentication.TokenCredentialConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].credential.username=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            credential: 
              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.azure.keyvault.secret.property-sources[0].credential.username="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_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.azure.keyvault.secret.property-sources[0].credential.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.azure.keyvault.secret.property-sources[0].enabled=true

Whether an Azure Service is enabled.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.AbstractAzureServiceConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].enabled=true

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            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.azure.keyvault.secret.property-sources[0].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_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_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.azure.keyvault.secret.property-sources[0].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.azure.keyvault.secret.property-sources[0].endpoint=

Azure Key Vault endpoint. For instance, 'https://{your-unique-keyvault-name}.vault.azure.net/'.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultPropertySourceProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            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.azure.keyvault.secret.property-sources[0].endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_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.azure.keyvault.secret.property-sources[0].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.azure.keyvault.secret.property-sources[0].name=

Name of this property source.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultPropertySourceProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].name=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            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.azure.keyvault.secret.property-sources[0].name="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_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.azure.keyvault.secret.property-sources[0].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.azure.keyvault.secret.property-sources[0].profile.cloud-type=

Name of the Azure cloud to connect to. Supported types are: AZURE, AZURE_CHINA, AZURE_US_GOVERNMENT, OTHER. The default value is `AZURE`.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.cloud-type=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              cloud-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.azure.keyvault.secret.property-sources[0].profile.cloud-type="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_CLOUD_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.azure.keyvault.secret.property-sources[0].profile.cloud-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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-endpoint=

The Microsoft Entra endpoint to connect to.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                active-directory-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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-version=

The Azure Active Directory Graph API version.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-version=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                active-directory-graph-api-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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-version="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_GRAPH_API_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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-endpoint=

The Azure Active Directory Graph endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                active-directory-graph-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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_GRAPH_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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-id=

The Microsoft Entra resource ID.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                active-directory-resource-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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_RESOURCE_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.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-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.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-endpoint=

The Azure Application Insights endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                azure-application-insights-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.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_AZURE_APPLICATION_INSIGHTS_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.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-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.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix=

The Data Lake analytics catalog and job endpoint suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                azure-data-lake-analytics-catalog-and-job-endpoint-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_AZURE_DATA_LAKE_ANALYTICS_CATALOG_AND_JOB_ENDPOINT_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-store-file-system-endpoint-suffix=

The Data Lake storage file system endpoint suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-store-file-system-endpoint-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                azure-data-lake-store-file-system-endpoint-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-store-file-system-endpoint-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_AZURE_DATA_LAKE_STORE_FILE_SYSTEM_ENDPOINT_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-store-file-system-endpoint-suffix="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-endpoint=

The Azure Log Analytics endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                azure-log-analytics-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.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_AZURE_LOG_ANALYTICS_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.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-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.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-id=

The Data Lake endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                data-lake-endpoint-resource-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.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_DATA_LAKE_ENDPOINT_RESOURCE_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.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-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.azure.keyvault.secret.property-sources[0].profile.environment.gallery-endpoint=

The gallery endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.gallery-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                gallery-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.azure.keyvault.secret.property-sources[0].profile.environment.gallery-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_GALLERY_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.azure.keyvault.secret.property-sources[0].profile.environment.gallery-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.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix=

The Key Vault DNS suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                key-vault-dns-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_KEY_VAULT_DNS_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].profile.environment.management-endpoint=

The management service endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.management-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                management-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.azure.keyvault.secret.property-sources[0].profile.environment.management-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_MANAGEMENT_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.azure.keyvault.secret.property-sources[0].profile.environment.management-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.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-endpoint=

The Microsoft Graph endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                microsoft-graph-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.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_MICROSOFT_GRAPH_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.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-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.azure.keyvault.secret.property-sources[0].profile.environment.portal=

The management portal URL.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.portal=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                portal: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].profile.environment.portal="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_PORTAL="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].profile.environment.portal="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].profile.environment.publishing-profile=

The publishing settings file URL.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.publishing-profile=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                publishing-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.azure.keyvault.secret.property-sources[0].profile.environment.publishing-profile="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_PUBLISHING_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.azure.keyvault.secret.property-sources[0].profile.environment.publishing-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.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-endpoint=

The resource management endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                resource-manager-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.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_RESOURCE_MANAGER_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.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-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.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-endpoint=

The SQL management endpoint.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-endpoint=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                sql-management-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.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-endpoint="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_SQL_MANAGEMENT_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.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-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.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix=

The SQL Server hostname suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                sql-server-hostname-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_SQL_SERVER_HOSTNAME_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix=

The Storage endpoint suffix.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties$AzureEnvironmentConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              environment: 
                storage-endpoint-suffix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_STORAGE_ENDPOINT_SUFFIX="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].profile.subscription-id=

Subscription ID to use when connecting to Azure resources.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.subscription-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              subscription-id: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.subscription-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_SUBSCRIPTION_ID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.subscription-id="..."

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

spring.cloud.azure.keyvault.secret.property-sources[0].profile.tenant-id=

Tenant ID for Azure resources.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.profile.AzureProfileConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].profile.tenant-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            profile: 
              tenant-id: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.tenant-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_TENANT_ID="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.tenant-id="..."

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

spring.cloud.azure.keyvault.secret.property-sources[0].proxy.hostname=

The host of the proxy.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.ProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].proxy.hostname=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            proxy: 
              hostname: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].proxy.hostname="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_HOSTNAME="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].proxy.hostname="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts=

A list of hosts or CIDR to not use proxy HTTP/HTTPS connections through.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.HttpProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            proxy: 
              non-proxy-hosts: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_NON_PROXY_HOSTS="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].proxy.password=

Password used to authenticate with the proxy.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.ProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].proxy.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            proxy: 
              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.azure.keyvault.secret.property-sources[0].proxy.password="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_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.azure.keyvault.secret.property-sources[0].proxy.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.azure.keyvault.secret.property-sources[0].proxy.port=

The port of the proxy.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.ProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].proxy.port=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            proxy: 
              port: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].proxy.port="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_PORT="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].proxy.port="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].proxy.type=

Type of the proxy. For instance of http, 'http', 'socks4', 'socks5'. For instance of amqp, 'http', 'socks'.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.ProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].proxy.type=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            proxy: 
              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.azure.keyvault.secret.property-sources[0].proxy.type="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_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.azure.keyvault.secret.property-sources[0].proxy.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.azure.keyvault.secret.property-sources[0].proxy.username=

Username used to authenticate with the proxy.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.ProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].proxy.username=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            proxy: 
              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.azure.keyvault.secret.property-sources[0].proxy.username="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_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.azure.keyvault.secret.property-sources[0].proxy.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.azure.keyvault.secret.property-sources[0].resource.region=

The region of an Azure resource. For instance, '"eastus"'.

com.azure.spring.cloud.autoconfigure.implementation.properties.resourcemanager.AzureResourceMetadataConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].resource.region=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            resource: 
              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.azure.keyvault.secret.property-sources[0].resource.region="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RESOURCE_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.azure.keyvault.secret.property-sources[0].resource.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.azure.keyvault.secret.property-sources[0].resource.resource-group=

The resource group holds an Azure resource.

com.azure.spring.cloud.autoconfigure.implementation.properties.resourcemanager.AzureResourceMetadataConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].resource.resource-group=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            resource: 
              resource-group: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-group="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RESOURCE_RESOURCE_GROUP="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-group="..."

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

spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-id=

ID of an Azure resource.

com.azure.spring.cloud.autoconfigure.implementation.properties.resourcemanager.AzureResourceMetadataConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].resource.resource-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            resource: 
              resource-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.azure.keyvault.secret.property-sources[0].resource.resource-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RESOURCE_RESOURCE_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.azure.keyvault.secret.property-sources[0].resource.resource-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.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay=

Amount of time(Duration) to wait between retry attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.ExponentialRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            retry: 
              exponential: 
                base-delay: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_EXPONENTIAL_BASE_DELAY="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay=

Maximum permissible amount of time(duration) between retry attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.ExponentialRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            retry: 
              exponential: 
                max-delay: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_EXPONENTIAL_MAX_DELAY="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries=

The maximum number of attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.ExponentialRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            retry: 
              exponential: 
                max-retries: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_EXPONENTIAL_MAX_RETRIES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].retry.fixed.delay=

Amount of time(Duration) to wait between retry attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.FixedRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].retry.fixed.delay=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            retry: 
              fixed: 
                delay: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].retry.fixed.delay="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_FIXED_DELAY="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].retry.fixed.delay="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries=

The maximum number of attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.FixedRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            retry: 
              fixed: 
                max-retries: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_FIXED_MAX_RETRIES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].retry.mode=

The retry backoff mode when retrying. Supported types are: FIXED, EXPONENTIAL.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.RetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].retry.mode=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            retry: 
              mode: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.property-sources[0].retry.mode="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_MODE="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.property-sources[0].retry.mode="..."

The above example assumes 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.azure.keyvault.secret.property-sources[0].secret-keys=

The configured secret keys will be loaded from Azure Key Vaults secret, if configured nothing, then load all the secrets. Only support exact value for secret names, For example, if you configured secret key name `SecretKey1` in Key Vaults secret, you should configure 'SecretKey1' here.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultPropertySourceProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].secret-keys=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            secret-keys: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.property-sources[0].secret-keys="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_SECRET_KEYS="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].secret-keys="..."

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

spring.cloud.azure.keyvault.secret.property-sources[0].service-version=

Secret service version used when making API requests.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultPropertySourceProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.property-sources[0].service-version=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          property-sources[0]: 
            service-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.azure.keyvault.secret.property-sources[0].service-version="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_SERVICE_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.azure.keyvault.secret.property-sources[0].service-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.azure.keyvault.secret.proxy.hostname=

The host of the proxy.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.HttpProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.proxy.hostname=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          proxy: 
            hostname: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.proxy.hostname="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_HOSTNAME="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.proxy.hostname="..."

The above example assumes 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.azure.keyvault.secret.proxy.non-proxy-hosts=

A list of hosts or CIDR to not use proxy HTTP/HTTPS connections through.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.HttpProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.proxy.non-proxy-hosts=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          proxy: 
            non-proxy-hosts: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.proxy.non-proxy-hosts="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_NON_PROXY_HOSTS="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.proxy.non-proxy-hosts="..."

The above example assumes 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.azure.keyvault.secret.proxy.password=

Password used to authenticate with the proxy.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.HttpProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.proxy.password=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          proxy: 
            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.azure.keyvault.secret.proxy.password="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_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.azure.keyvault.secret.proxy.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.azure.keyvault.secret.proxy.port=

The port of the proxy.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.HttpProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.proxy.port=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          proxy: 
            port: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.proxy.port="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_PORT="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.proxy.port="..."

The above example assumes 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.azure.keyvault.secret.proxy.type=

Type of the proxy. For instance of http, 'http', 'socks4', 'socks5'. For instance of amqp, 'http', 'socks'.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.HttpProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.proxy.type=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          proxy: 
            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.azure.keyvault.secret.proxy.type="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_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.azure.keyvault.secret.proxy.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.azure.keyvault.secret.proxy.username=

Username used to authenticate with the proxy.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.proxy.HttpProxyConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.proxy.username=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          proxy: 
            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.azure.keyvault.secret.proxy.username="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_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.azure.keyvault.secret.proxy.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.azure.keyvault.secret.resource.region=

The region of an Azure resource. For instance, '"eastus"'.

com.azure.spring.cloud.autoconfigure.implementation.properties.resourcemanager.AzureResourceMetadataConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.resource.region=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          resource: 
            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.azure.keyvault.secret.resource.region="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RESOURCE_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.azure.keyvault.secret.resource.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.azure.keyvault.secret.resource.resource-group=

The resource group holds an Azure resource.

com.azure.spring.cloud.autoconfigure.implementation.properties.resourcemanager.AzureResourceMetadataConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.resource.resource-group=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          resource: 
            resource-group: "..."

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

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

java -Dspring.cloud.azure.keyvault.secret.resource.resource-group="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RESOURCE_RESOURCE_GROUP="..."

java -jar build/libs/cas.war

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

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

java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.resource.resource-group="..."

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

spring.cloud.azure.keyvault.secret.resource.resource-id=

ID of an Azure resource.

com.azure.spring.cloud.autoconfigure.implementation.properties.resourcemanager.AzureResourceMetadataConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.resource.resource-id=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          resource: 
            resource-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.azure.keyvault.secret.resource.resource-id="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RESOURCE_RESOURCE_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.azure.keyvault.secret.resource.resource-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.azure.keyvault.secret.retry.exponential.base-delay=

Amount of time(Duration) to wait between retry attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.ExponentialRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.retry.exponential.base-delay=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          retry: 
            exponential: 
              base-delay: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.retry.exponential.base-delay="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_EXPONENTIAL_BASE_DELAY="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.retry.exponential.base-delay="..."

The above example assumes 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.azure.keyvault.secret.retry.exponential.max-delay=

Maximum permissible amount of time(duration) between retry attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.ExponentialRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.retry.exponential.max-delay=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          retry: 
            exponential: 
              max-delay: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.retry.exponential.max-delay="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_EXPONENTIAL_MAX_DELAY="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.retry.exponential.max-delay="..."

The above example assumes 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.azure.keyvault.secret.retry.exponential.max-retries=

The maximum number of attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.ExponentialRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.retry.exponential.max-retries=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          retry: 
            exponential: 
              max-retries: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.retry.exponential.max-retries="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_EXPONENTIAL_MAX_RETRIES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.retry.exponential.max-retries="..."

The above example assumes 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.azure.keyvault.secret.retry.fixed.delay=

Amount of time(Duration) to wait between retry attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.FixedRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.retry.fixed.delay=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          retry: 
            fixed: 
              delay: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.retry.fixed.delay="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_FIXED_DELAY="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.retry.fixed.delay="..."

The above example assumes 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.azure.keyvault.secret.retry.fixed.max-retries=

The maximum number of attempts.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.FixedRetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.retry.fixed.max-retries=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          retry: 
            fixed: 
              max-retries: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.retry.fixed.max-retries="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_FIXED_MAX_RETRIES="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.retry.fixed.max-retries="..."

The above example assumes 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.azure.keyvault.secret.retry.mode=

The retry backoff mode when retrying. Supported types are: FIXED, EXPONENTIAL.

com.azure.spring.cloud.autoconfigure.implementation.properties.core.retry.RetryConfigurationProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.retry.mode=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          retry: 
            mode: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with 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.azure.keyvault.secret.retry.mode="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_MODE="..."

java -jar build/libs/cas.war

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

CAS 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.azure.keyvault.secret.retry.mode="..."

The above example assumes 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.azure.keyvault.secret.service-version=

Secret service version used when making API requests.

com.azure.spring.cloud.autoconfigure.implementation.keyvault.secrets.properties.AzureKeyVaultSecretProperties.

_{How can I configure this property?}

Configuration properties can be included 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.azure.keyvault.secret.service-version=...

CAS properties can be specified using the YAML syntax:

spring: 
  cloud: 
    azure: 
      keyvault: 
        secret: 
          service-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.azure.keyvault.secret.service-version="..." -jar build/libs/cas.war

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

export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_SERVICE_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.azure.keyvault.secret.service-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.

# Whether to enable the Azure Key Vault challenge resource verification, default: true.
# spring.cloud.azure.keyvault.secret.challenge-resource-verification-enabled=true

# Represents current application and is used for telemetry/monitoring purposes.
# spring.cloud.azure.keyvault.secret.client.application-id=

# Amount of time(Duration) the request attempts to connect to the remote host and the connection is resolved.
# spring.cloud.azure.keyvault.secret.client.connect-timeout=

# Amount of time(Duration) before an idle connection.
# spring.cloud.azure.keyvault.secret.client.connection-idle-timeout=

# List of headers applied to each request sent with client.
# spring.cloud.azure.keyvault.secret.client.headers=

# The name of the header.
# spring.cloud.azure.keyvault.secret.client.headers[0].name=

# List of values of the header.
# spring.cloud.azure.keyvault.secret.client.headers[0].values=

# Comma-delimited list of allowlist headers that should be logged.
# spring.cloud.azure.keyvault.secret.client.logging.allowed-header-names=

# Comma-delimited list of allowlist query parameters.
# spring.cloud.azure.keyvault.secret.client.logging.allowed-query-param-names=

# The level of detail to log on HTTP messages.
# spring.cloud.azure.keyvault.secret.client.logging.level=

# Whether to pretty print the message bodies.
# spring.cloud.azure.keyvault.secret.client.logging.pretty-print-body=

# Maximum connection pool size used by the underlying HTTP client.
# spring.cloud.azure.keyvault.secret.client.maximum-connection-pool-size=

# Amount of time(Duration) used when reading the server response.
# spring.cloud.azure.keyvault.secret.client.read-timeout=

# Amount of time(Duration) used when waiting for a server to reply.
# spring.cloud.azure.keyvault.secret.client.response-timeout=

# Amount of time(Duration) each request being sent over the wire.
# spring.cloud.azure.keyvault.secret.client.write-timeout=

# Password of the certificate file.
# spring.cloud.azure.keyvault.secret.credential.client-certificate-password=

# Path of a PEM certificate file to use when performing service principal authentication with Azure.
# spring.cloud.azure.keyvault.secret.credential.client-certificate-path=

# Client ID to use when performing service principal authentication with Azure.
# spring.cloud.azure.keyvault.secret.credential.client-id=

# Client secret to use when performing service principal authentication with Azure.
# spring.cloud.azure.keyvault.secret.credential.client-secret=

# Whether to enable managed identity to authenticate with Azure.
# spring.cloud.azure.keyvault.secret.credential.managed-identity-enabled=false

# Password to use when performing username/password authentication with Azure.
# spring.cloud.azure.keyvault.secret.credential.password=

# Username to use when performing username/password authentication with Azure.
# spring.cloud.azure.keyvault.secret.credential.username=

# Whether an Azure Service is enabled.
# spring.cloud.azure.keyvault.secret.enabled=true

# Azure Key Vault endpoint.
# spring.cloud.azure.keyvault.secret.endpoint=

# Name of the Azure cloud to connect to.
# spring.cloud.azure.keyvault.secret.profile.cloud-type=

# The Azure Active Directory endpoint to connect to.
# spring.cloud.azure.keyvault.secret.profile.environment.active-directory-endpoint=

# The Azure Active Directory Graph API version.
# spring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-api-version=

# The Azure Active Directory Graph endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-endpoint=

# The Azure Active Directory resource ID.
# spring.cloud.azure.keyvault.secret.profile.environment.active-directory-resource-id=

# The Azure Application Insights endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.azure-application-insights-endpoint=

# The Data Lake analytics catalog and job endpoint suffix.
# spring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix=

# The Data Lake storage file system endpoint suffix.
# spring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix=

# The Azure Log Analytics endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.azure-log-analytics-endpoint=

# The Data Lake endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-id=

# The gallery endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.gallery-endpoint=

# The Key Vault DNS suffix.
# spring.cloud.azure.keyvault.secret.profile.environment.key-vault-dns-suffix=

# The management service endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.management-endpoint=

# The Microsoft Graph endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.microsoft-graph-endpoint=

# The management portal URL.
# spring.cloud.azure.keyvault.secret.profile.environment.portal=

# The publishing settings file URL.
# spring.cloud.azure.keyvault.secret.profile.environment.publishing-profile=

# The resource management endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.resource-manager-endpoint=

# The domain name for Service Bus.
# spring.cloud.azure.keyvault.secret.profile.environment.service-bus-domain-name=

# The SQL management endpoint.
# spring.cloud.azure.keyvault.secret.profile.environment.sql-management-endpoint=

# The SQL Server hostname suffix.
# spring.cloud.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix=

# The Storage endpoint suffix.
# spring.cloud.azure.keyvault.secret.profile.environment.storage-endpoint-suffix=

# Subscription ID to use when connecting to Azure resources.
# spring.cloud.azure.keyvault.secret.profile.subscription-id=

# Tenant ID for Azure resources.
# spring.cloud.azure.keyvault.secret.profile.tenant-id=

# Whether to enable the Key Vault property source.
# spring.cloud.azure.keyvault.secret.property-source-enabled=true

# List of Azure Key Vault property sources.
# spring.cloud.azure.keyvault.secret.property-sources=

# Whether to enable case-sensitive for secret keys.
# spring.cloud.azure.keyvault.secret.property-sources[0].case-sensitive=

# Whether to enable the Azure Key Vault challenge resource verification, default: true.
# spring.cloud.azure.keyvault.secret.property-sources[0].challenge-resource-verification-enabled=true

# Represents current application and is used for telemetry/monitoring purposes.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.application-id=

# Amount of time(Duration) the request attempts to connect to the remote host and the connection is resolved.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.connect-timeout=

# Amount of time(Duration) before an idle connection.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.connection-idle-timeout=

# The name of the header.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].name=

# List of values of the header.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].values=

# Comma-delimited list of allowlist headers that should be logged.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names=

# Comma-delimited list of allowlist query parameters.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names=

# The level of detail to log on HTTP messages.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.level=

# Whether to pretty print the message bodies.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body=

# Maximum connection pool size used by the underlying HTTP client.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size=

# Amount of time(Duration) used when reading the server response.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.read-timeout=

# Amount of time(Duration) used when waiting for a server to reply.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.response-timeout=

# Amount of time(Duration) each request being sent over the wire.
# spring.cloud.azure.keyvault.secret.property-sources[0].client.write-timeout=

# Password of the certificate file.
# spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-password=

# Path of a PEM certificate file to use when performing service principal authentication with Azure.
# spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-path=

# Client ID to use when performing service principal authentication with Azure.
# spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-id=

# Client secret to use when performing service principal authentication with Azure.
# spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-secret=

# Whether to enable managed identity to authenticate with Azure.
# spring.cloud.azure.keyvault.secret.property-sources[0].credential.managed-identity-enabled=false

# Password to use when performing username/password authentication with Azure.
# spring.cloud.azure.keyvault.secret.property-sources[0].credential.password=

# Username to use when performing username/password authentication with Azure.
# spring.cloud.azure.keyvault.secret.property-sources[0].credential.username=

# Whether an Azure Service is enabled.
# spring.cloud.azure.keyvault.secret.property-sources[0].enabled=true

# Azure Key Vault endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].endpoint=

# Name of this property source.
# spring.cloud.azure.keyvault.secret.property-sources[0].name=

# Name of the Azure cloud to connect to.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.cloud-type=

# The Microsoft Entra endpoint to connect to.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-endpoint=

# The Azure Active Directory Graph API version.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-version=

# The Azure Active Directory Graph endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-endpoint=

# The Microsoft Entra resource ID.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-id=

# The Azure Application Insights endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-endpoint=

# The Data Lake analytics catalog and job endpoint suffix.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix=

# The Data Lake storage file system endpoint suffix.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-store-file-system-endpoint-suffix=

# The Azure Log Analytics endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-endpoint=

# The Data Lake endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-id=

# The gallery endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.gallery-endpoint=

# The Key Vault DNS suffix.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix=

# The management service endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.management-endpoint=

# The Microsoft Graph endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-endpoint=

# The management portal URL.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.portal=

# The publishing settings file URL.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.publishing-profile=

# The resource management endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-endpoint=

# The SQL management endpoint.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-endpoint=

# The SQL Server hostname suffix.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix=

# The Storage endpoint suffix.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix=

# Subscription ID to use when connecting to Azure resources.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.subscription-id=

# Tenant ID for Azure resources.
# spring.cloud.azure.keyvault.secret.property-sources[0].profile.tenant-id=

# The host of the proxy.
# spring.cloud.azure.keyvault.secret.property-sources[0].proxy.hostname=

# A list of hosts or CIDR to not use proxy HTTP/HTTPS connections through.
# spring.cloud.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts=

# Password used to authenticate with the proxy.
# spring.cloud.azure.keyvault.secret.property-sources[0].proxy.password=

# The port of the proxy.
# spring.cloud.azure.keyvault.secret.property-sources[0].proxy.port=

# Type of the proxy.
# spring.cloud.azure.keyvault.secret.property-sources[0].proxy.type=

# Username used to authenticate with the proxy.
# spring.cloud.azure.keyvault.secret.property-sources[0].proxy.username=

# The region of an Azure resource.
# spring.cloud.azure.keyvault.secret.property-sources[0].resource.region=

# The resource group holds an Azure resource.
# spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-group=

# ID of an Azure resource.
# spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-id=

# Amount of time(Duration) to wait between retry attempts.
# spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay=

# Maximum permissible amount of time(duration) between retry attempts.
# spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay=

# The maximum number of attempts.
# spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries=

# Amount of time(Duration) to wait between retry attempts.
# spring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.delay=

# The maximum number of attempts.
# spring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries=

# The retry backoff mode when retrying.
# spring.cloud.azure.keyvault.secret.property-sources[0].retry.mode=

# The configured secret keys will be loaded from Azure Key Vaults secret, if configured nothing, then load all the secrets.
# spring.cloud.azure.keyvault.secret.property-sources[0].secret-keys=

# Secret service version used when making API requests.
# spring.cloud.azure.keyvault.secret.property-sources[0].service-version=

# The host of the proxy.
# spring.cloud.azure.keyvault.secret.proxy.hostname=

# A list of hosts or CIDR to not use proxy HTTP/HTTPS connections through.
# spring.cloud.azure.keyvault.secret.proxy.non-proxy-hosts=

# Password used to authenticate with the proxy.
# spring.cloud.azure.keyvault.secret.proxy.password=

# The port of the proxy.
# spring.cloud.azure.keyvault.secret.proxy.port=

# Type of the proxy.
# spring.cloud.azure.keyvault.secret.proxy.type=

# Username used to authenticate with the proxy.
# spring.cloud.azure.keyvault.secret.proxy.username=

# The region of an Azure resource.
# spring.cloud.azure.keyvault.secret.resource.region=

# The resource group holds an Azure resource.
# spring.cloud.azure.keyvault.secret.resource.resource-group=

# ID of an Azure resource.
# spring.cloud.azure.keyvault.secret.resource.resource-id=

# Amount of time(Duration) to wait between retry attempts.
# spring.cloud.azure.keyvault.secret.retry.exponential.base-delay=

# Maximum permissible amount of time(duration) between retry attempts.
# spring.cloud.azure.keyvault.secret.retry.exponential.max-delay=

# The maximum number of attempts.
# spring.cloud.azure.keyvault.secret.retry.exponential.max-retries=

# Amount of time(Duration) to wait between retry attempts.
# spring.cloud.azure.keyvault.secret.retry.fixed.delay=

# The maximum number of attempts.
# spring.cloud.azure.keyvault.secret.retry.fixed.max-retries=

# The retry backoff mode when retrying.
# spring.cloud.azure.keyvault.secret.retry.mode=

# Secret service version used when making API requests.
# spring.cloud.azure.keyvault.secret.service-version=

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.