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:
1
2
3
4
5
<dependency>
<groupId>org.apereo.cas</groupId>
<artifactId>cas-server-support-configuration-cloud-azure-keyvault</artifactId>
<version>${cas.version}</version>
</dependency>
1
implementation "org.apereo.cas:cas-server-support-configuration-cloud-azure-keyvault:${project.'cas.version'}"
1
2
3
4
5
6
7
8
9
dependencyManagement {
imports {
mavenBom "org.apereo.cas:cas-server-support-bom:${project.'cas.version'}"
}
}
dependencies {
implementation "org.apereo.cas:cas-server-support-configuration-cloud-azure-keyvault"
}
1
2
3
4
5
6
7
8
9
10
dependencies {
/*
The following platform references should be included automatically and are listed here for reference only.
implementation enforcedPlatform("org.apereo.cas:cas-server-support-bom:${project.'cas.version'}")
implementation platform(org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES)
*/
implementation "org.apereo.cas:cas-server-support-configuration-cloud-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.
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:
- Required
- Optional
- Signing & Encryption
- Hibernate & JDBC
- Email Servers
- Groovy Scripting
- LDAP & Active Directory
- Authentication
- Password Encoding
- Principal Transformation
- Password Policy
- Third Party
- Notes
spring.cloud.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.
CAS Property:
|
1 |
spring.cloud.azure.keyvault.secret.challenge-resource-verification-enabled=true |
1
spring:
cloud:
azure:
keyvault:
secret:
challenge-resource-verification-enabled: "true"
1
java -Dspring.cloud.azure.keyvault.secret.challenge-resource-verification-enabled="true" -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CHALLENGE_RESOURCE_VERIFICATION_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.challenge-resource-verification-enabled="true"
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.application-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.application-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
application-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.application-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_APPLICATION_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.application-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.connect-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.connect-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
connect-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.connect-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_CONNECT_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.connect-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.connection-idle-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.connection-idle-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
connection-idle-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.connection-idle-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_CONNECTION_IDLE_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.connection-idle-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.headers
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.headers=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
headers: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.headers="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_HEADERS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.headers="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.headers[0].name
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.headers[0].name=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
headers[0]:
name: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.headers[0].name="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_HEADERS[0]_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.headers[0].name="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.headers[0].values
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.headers[0].values=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
headers[0]:
values: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.headers[0].values="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_HEADERS[0]_VALUES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.headers[0].values="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.logging.allowed-header-names
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.logging.allowed-header-names=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
logging:
allowed-header-names: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.logging.allowed-header-names="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_LOGGING_ALLOWED_HEADER_NAMES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.logging.allowed-header-names="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.logging.allowed-query-param-names
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.logging.allowed-query-param-names=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
logging:
allowed-query-param-names: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.logging.allowed-query-param-names="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_LOGGING_ALLOWED_QUERY_PARAM_NAMES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.logging.allowed-query-param-names="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.logging.level
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.logging.level=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
logging:
level: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.logging.level="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_LOGGING_LEVEL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.logging.level="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.logging.pretty-print-body
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.logging.pretty-print-body=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
logging:
pretty-print-body: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.logging.pretty-print-body="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_LOGGING_PRETTY_PRINT_BODY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.logging.pretty-print-body="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.maximum-connection-pool-size
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.maximum-connection-pool-size=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
maximum-connection-pool-size: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.maximum-connection-pool-size="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_MAXIMUM_CONNECTION_POOL_SIZE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.maximum-connection-pool-size="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.read-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.read-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
read-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.read-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_READ_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.read-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.response-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.response-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
response-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.response-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_RESPONSE_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.response-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.client.write-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.client.write-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
client:
write-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.client.write-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CLIENT_WRITE_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.client.write-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.credential.client-certificate-password
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.credential.client-certificate-password=...
1
spring:
cloud:
azure:
keyvault:
secret:
credential:
client-certificate-password: "..."
1
java -Dspring.cloud.azure.keyvault.secret.credential.client-certificate-password="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_CLIENT_CERTIFICATE_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.client-certificate-password="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.credential.client-certificate-path
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.credential.client-certificate-path=...
1
spring:
cloud:
azure:
keyvault:
secret:
credential:
client-certificate-path: "..."
1
java -Dspring.cloud.azure.keyvault.secret.credential.client-certificate-path="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_CLIENT_CERTIFICATE_PATH="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.client-certificate-path="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.credential.client-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.credential.client-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
credential:
client-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.credential.client-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_CLIENT_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.client-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.credential.client-secret
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.credential.client-secret=...
1
spring:
cloud:
azure:
keyvault:
secret:
credential:
client-secret: "..."
1
java -Dspring.cloud.azure.keyvault.secret.credential.client-secret="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_CLIENT_SECRET="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.client-secret="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.credential.managed-identity-enabled
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.credential.managed-identity-enabled=...
1
spring:
cloud:
azure:
keyvault:
secret:
credential:
managed-identity-enabled: "..."
1
java -Dspring.cloud.azure.keyvault.secret.credential.managed-identity-enabled="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_MANAGED_IDENTITY_ENABLED="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.managed-identity-enabled="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.credential.password
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.credential.password=...
1
spring:
cloud:
azure:
keyvault:
secret:
credential:
password: "..."
1
java -Dspring.cloud.azure.keyvault.secret.credential.password="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.password="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.credential.username
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.credential.username=...
1
spring:
cloud:
azure:
keyvault:
secret:
credential:
username: "..."
1
java -Dspring.cloud.azure.keyvault.secret.credential.username="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_CREDENTIAL_USERNAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.credential.username="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.enabled
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.enabled=true
1
spring:
cloud:
azure:
keyvault:
secret:
enabled: "true"
1
java -Dspring.cloud.azure.keyvault.secret.enabled="true" -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.enabled="true"
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.
CAS Property: spring.cloud.azure.keyvault.secret.endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.cloud-type
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.cloud-type=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
cloud-type: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.cloud-type="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_CLOUD_TYPE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.cloud-type="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.active-directory-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.active-directory-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
active-directory-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.active-directory-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.active-directory-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-api-version
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-api-version=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
active-directory-graph-api-version: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-api-version="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_GRAPH_API_VERSION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-api-version="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
active-directory-graph-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_GRAPH_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.active-directory-graph-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.active-directory-resource-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.active-directory-resource-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
active-directory-resource-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.active-directory-resource-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_RESOURCE_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.active-directory-resource-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.azure-application-insights-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.azure-application-insights-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
azure-application-insights-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.azure-application-insights-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_AZURE_APPLICATION_INSIGHTS_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.azure-application-insights-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
azure-data-lake-analytics-catalog-and-job-endpoint-suffix: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_AZURE_DATA_LAKE_ANALYTICS_CATALOG_AND_JOB_ENDPOINT_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
azure-data-lake-store-file-system-endpoint-suffix: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_AZURE_DATA_LAKE_STORE_FILE_SYSTEM_ENDPOINT_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.azure-data-lake-store-file-system-endpoint-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.azure-log-analytics-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.azure-log-analytics-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
azure-log-analytics-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.azure-log-analytics-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_AZURE_LOG_ANALYTICS_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.azure-log-analytics-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
data-lake-endpoint-resource-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_DATA_LAKE_ENDPOINT_RESOURCE_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.data-lake-endpoint-resource-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.gallery-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.gallery-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
gallery-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.gallery-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_GALLERY_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.gallery-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.key-vault-dns-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.key-vault-dns-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
key-vault-dns-suffix: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.key-vault-dns-suffix="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_KEY_VAULT_DNS_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.key-vault-dns-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.management-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.management-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
management-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.management-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_MANAGEMENT_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.management-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.microsoft-graph-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.microsoft-graph-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
microsoft-graph-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.microsoft-graph-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_MICROSOFT_GRAPH_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.microsoft-graph-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.portal
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.portal=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
portal: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.portal="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_PORTAL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.portal="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.publishing-profile
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.publishing-profile=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
publishing-profile: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.publishing-profile="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_PUBLISHING_PROFILE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.publishing-profile="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.resource-manager-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.resource-manager-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
resource-manager-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.resource-manager-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_RESOURCE_MANAGER_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.resource-manager-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.service-bus-domain-name
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.service-bus-domain-name=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
service-bus-domain-name: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.service-bus-domain-name="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_SERVICE_BUS_DOMAIN_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.service-bus-domain-name="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.sql-management-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.sql-management-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
sql-management-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.sql-management-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_SQL_MANAGEMENT_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.sql-management-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
sql-server-hostname-suffix: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_SQL_SERVER_HOSTNAME_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.sql-server-hostname-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.environment.storage-endpoint-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.environment.storage-endpoint-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
environment:
storage-endpoint-suffix: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.environment.storage-endpoint-suffix="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_ENVIRONMENT_STORAGE_ENDPOINT_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.environment.storage-endpoint-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.subscription-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.subscription-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
subscription-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.subscription-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_SUBSCRIPTION_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.subscription-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.profile.tenant-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.profile.tenant-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
profile:
tenant-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.profile.tenant-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROFILE_TENANT_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.profile.tenant-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-source-enabled
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-source-enabled=true
1
spring:
cloud:
azure:
keyvault:
secret:
property-source-enabled: "true"
1
java -Dspring.cloud.azure.keyvault.secret.property-source-enabled="true" -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCE_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-source-enabled="true"
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].case-sensitive
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].case-sensitive=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
case-sensitive: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].case-sensitive="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CASE_SENSITIVE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].case-sensitive="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].challenge-resource-verification-enabled
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].challenge-resource-verification-enabled=true
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
challenge-resource-verification-enabled: "true"
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].challenge-resource-verification-enabled="true" -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CHALLENGE_RESOURCE_VERIFICATION_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].challenge-resource-verification-enabled="true"
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.application-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.application-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
application-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.application-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_APPLICATION_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.application-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.connect-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.connect-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
connect-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.connect-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_CONNECT_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.connect-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.connection-idle-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.connection-idle-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
connection-idle-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.connection-idle-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_CONNECTION_IDLE_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.connection-idle-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].name
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].name=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
headers[0]:
name: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].name="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_HEADERS[0]_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].name="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].values
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].values=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
headers[0]:
values: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].values="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_HEADERS[0]_VALUES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.headers[0].values="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
logging:
allowed-header-names: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_LOGGING_ALLOWED_HEADER_NAMES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-header-names="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
logging:
allowed-query-param-names: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_LOGGING_ALLOWED_QUERY_PARAM_NAMES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.allowed-query-param-names="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.level
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.level=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
logging:
level: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.logging.level="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_LOGGING_LEVEL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.level="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
logging:
pretty-print-body: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_LOGGING_PRETTY_PRINT_BODY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.logging.pretty-print-body="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
maximum-connection-pool-size: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_MAXIMUM_CONNECTION_POOL_SIZE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.maximum-connection-pool-size="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.read-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.read-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
read-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.read-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_READ_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.read-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.response-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.response-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
response-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.response-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_RESPONSE_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.response-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].client.write-timeout
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].client.write-timeout=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
client:
write-timeout: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].client.write-timeout="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CLIENT_WRITE_TIMEOUT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].client.write-timeout="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-password
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-password=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
credential:
client-certificate-password: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-password="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_CLIENT_CERTIFICATE_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-password="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-path
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-path=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
credential:
client-certificate-path: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-path="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_CLIENT_CERTIFICATE_PATH="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-certificate-path="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
credential:
client-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.client-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_CLIENT_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-secret
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-secret=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
credential:
client-secret: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.client-secret="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_CLIENT_SECRET="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.client-secret="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].credential.managed-identity-enabled
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].credential.managed-identity-enabled=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
credential:
managed-identity-enabled: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.managed-identity-enabled="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_MANAGED_IDENTITY_ENABLED="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.managed-identity-enabled="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].credential.password
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].credential.password=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
credential:
password: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.password="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.password="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].credential.username
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].credential.username=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
credential:
username: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].credential.username="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_CREDENTIAL_USERNAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].credential.username="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].enabled
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].enabled=true
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
enabled: "true"
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].enabled="true" -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_ENABLED="true"
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].enabled="true"
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].name
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].name=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
name: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].name="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_NAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].name="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.cloud-type
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.cloud-type=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
cloud-type: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.cloud-type="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_CLOUD_TYPE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.cloud-type="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
active-directory-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-version
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-version=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
active-directory-graph-api-version: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-version="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_GRAPH_API_VERSION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-api-version="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
active-directory-graph-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_GRAPH_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-graph-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
active-directory-resource-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_ACTIVE_DIRECTORY_RESOURCE_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.active-directory-resource-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
azure-application-insights-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_AZURE_APPLICATION_INSIGHTS_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-application-insights-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
azure-data-lake-analytics-catalog-and-job-endpoint-suffix: "..."
1
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.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_AZURE_DATA_LAKE_ANALYTICS_CATALOG_AND_JOB_ENDPOINT_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-analytics-catalog-and-job-endpoint-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-store-file-system-endpoint-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-store-file-system-endpoint-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
azure-data-lake-store-file-system-endpoint-suffix: "..."
1
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.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_AZURE_DATA_LAKE_STORE_FILE_SYSTEM_ENDPOINT_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-data-lake-store-file-system-endpoint-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
azure-log-analytics-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_AZURE_LOG_ANALYTICS_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.azure-log-analytics-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
data-lake-endpoint-resource-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_DATA_LAKE_ENDPOINT_RESOURCE_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.data-lake-endpoint-resource-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.gallery-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.gallery-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
gallery-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.gallery-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_GALLERY_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.gallery-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
key-vault-dns-suffix: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_KEY_VAULT_DNS_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.key-vault-dns-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.management-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.management-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
management-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.management-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_MANAGEMENT_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.management-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
microsoft-graph-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_MICROSOFT_GRAPH_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.microsoft-graph-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.portal
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.portal=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
portal: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.portal="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_PORTAL="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.portal="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.publishing-profile
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.publishing-profile=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
publishing-profile: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.publishing-profile="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_PUBLISHING_PROFILE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.publishing-profile="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
resource-manager-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_RESOURCE_MANAGER_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.resource-manager-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-endpoint
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-endpoint=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
sql-management-endpoint: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-endpoint="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_SQL_MANAGEMENT_ENDPOINT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-management-endpoint="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
sql-server-hostname-suffix: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_SQL_SERVER_HOSTNAME_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.sql-server-hostname-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
environment:
storage-endpoint-suffix: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_ENVIRONMENT_STORAGE_ENDPOINT_SUFFIX="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.environment.storage-endpoint-suffix="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.subscription-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.subscription-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
subscription-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.subscription-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_SUBSCRIPTION_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.subscription-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].profile.tenant-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].profile.tenant-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
profile:
tenant-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].profile.tenant-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROFILE_TENANT_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].profile.tenant-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].proxy.hostname
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].proxy.hostname=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
proxy:
hostname: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].proxy.hostname="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_HOSTNAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].proxy.hostname="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
proxy:
non-proxy-hosts: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_NON_PROXY_HOSTS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].proxy.non-proxy-hosts="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].proxy.password
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].proxy.password=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
proxy:
password: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].proxy.password="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].proxy.password="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].proxy.port
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].proxy.port=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
proxy:
port: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].proxy.port="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_PORT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].proxy.port="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].proxy.type
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].proxy.type=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
proxy:
type: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].proxy.type="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_TYPE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].proxy.type="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].proxy.username
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].proxy.username=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
proxy:
username: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].proxy.username="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_PROXY_USERNAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].proxy.username="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].resource.region
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].resource.region=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
resource:
region: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].resource.region="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RESOURCE_REGION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].resource.region="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-group
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-group=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
resource:
resource-group: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-group="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RESOURCE_RESOURCE_GROUP="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-group="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
resource:
resource-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RESOURCE_RESOURCE_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].resource.resource-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
retry:
exponential:
base-delay: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_EXPONENTIAL_BASE_DELAY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.base-delay="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
retry:
exponential:
max-delay: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_EXPONENTIAL_MAX_DELAY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-delay="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
retry:
exponential:
max-retries: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_EXPONENTIAL_MAX_RETRIES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].retry.exponential.max-retries="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.delay
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.delay=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
retry:
fixed:
delay: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.delay="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_FIXED_DELAY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.delay="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
retry:
fixed:
max-retries: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_FIXED_MAX_RETRIES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].retry.fixed.max-retries="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].retry.mode
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].retry.mode=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
retry:
mode: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].retry.mode="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_RETRY_MODE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].retry.mode="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].secret-keys
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].secret-keys=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
secret-keys: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].secret-keys="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_SECRET_KEYS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].secret-keys="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.property-sources[0].service-version
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.property-sources[0].service-version=...
1
spring:
cloud:
azure:
keyvault:
secret:
property-sources[0]:
service-version: "..."
1
java -Dspring.cloud.azure.keyvault.secret.property-sources[0].service-version="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROPERTY_SOURCES[0]_SERVICE_VERSION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.property-sources[0].service-version="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.proxy.hostname
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.proxy.hostname=...
1
spring:
cloud:
azure:
keyvault:
secret:
proxy:
hostname: "..."
1
java -Dspring.cloud.azure.keyvault.secret.proxy.hostname="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_HOSTNAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.proxy.hostname="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.proxy.non-proxy-hosts
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.proxy.non-proxy-hosts=...
1
spring:
cloud:
azure:
keyvault:
secret:
proxy:
non-proxy-hosts: "..."
1
java -Dspring.cloud.azure.keyvault.secret.proxy.non-proxy-hosts="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_NON_PROXY_HOSTS="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.proxy.non-proxy-hosts="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.proxy.password
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.proxy.password=...
1
spring:
cloud:
azure:
keyvault:
secret:
proxy:
password: "..."
1
java -Dspring.cloud.azure.keyvault.secret.proxy.password="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_PASSWORD="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.proxy.password="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.proxy.port
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.proxy.port=...
1
spring:
cloud:
azure:
keyvault:
secret:
proxy:
port: "..."
1
java -Dspring.cloud.azure.keyvault.secret.proxy.port="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_PORT="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.proxy.port="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.proxy.type
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.proxy.type=...
1
spring:
cloud:
azure:
keyvault:
secret:
proxy:
type: "..."
1
java -Dspring.cloud.azure.keyvault.secret.proxy.type="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_TYPE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.proxy.type="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.proxy.username
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.proxy.username=...
1
spring:
cloud:
azure:
keyvault:
secret:
proxy:
username: "..."
1
java -Dspring.cloud.azure.keyvault.secret.proxy.username="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_PROXY_USERNAME="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.proxy.username="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.resource.region
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.resource.region=...
1
spring:
cloud:
azure:
keyvault:
secret:
resource:
region: "..."
1
java -Dspring.cloud.azure.keyvault.secret.resource.region="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RESOURCE_REGION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.resource.region="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.resource.resource-group
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.resource.resource-group=...
1
spring:
cloud:
azure:
keyvault:
secret:
resource:
resource-group: "..."
1
java -Dspring.cloud.azure.keyvault.secret.resource.resource-group="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RESOURCE_RESOURCE_GROUP="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.resource.resource-group="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.resource.resource-id
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.resource.resource-id=...
1
spring:
cloud:
azure:
keyvault:
secret:
resource:
resource-id: "..."
1
java -Dspring.cloud.azure.keyvault.secret.resource.resource-id="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RESOURCE_RESOURCE_ID="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.resource.resource-id="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.retry.exponential.base-delay
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.retry.exponential.base-delay=...
1
spring:
cloud:
azure:
keyvault:
secret:
retry:
exponential:
base-delay: "..."
1
java -Dspring.cloud.azure.keyvault.secret.retry.exponential.base-delay="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_EXPONENTIAL_BASE_DELAY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.retry.exponential.base-delay="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.retry.exponential.max-delay
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.retry.exponential.max-delay=...
1
spring:
cloud:
azure:
keyvault:
secret:
retry:
exponential:
max-delay: "..."
1
java -Dspring.cloud.azure.keyvault.secret.retry.exponential.max-delay="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_EXPONENTIAL_MAX_DELAY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.retry.exponential.max-delay="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.retry.exponential.max-retries
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.retry.exponential.max-retries=...
1
spring:
cloud:
azure:
keyvault:
secret:
retry:
exponential:
max-retries: "..."
1
java -Dspring.cloud.azure.keyvault.secret.retry.exponential.max-retries="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_EXPONENTIAL_MAX_RETRIES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.retry.exponential.max-retries="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.retry.fixed.delay
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.retry.fixed.delay=...
1
spring:
cloud:
azure:
keyvault:
secret:
retry:
fixed:
delay: "..."
1
java -Dspring.cloud.azure.keyvault.secret.retry.fixed.delay="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_FIXED_DELAY="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.retry.fixed.delay="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.retry.fixed.max-retries
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.retry.fixed.max-retries=...
1
spring:
cloud:
azure:
keyvault:
secret:
retry:
fixed:
max-retries: "..."
1
java -Dspring.cloud.azure.keyvault.secret.retry.fixed.max-retries="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_FIXED_MAX_RETRIES="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.retry.fixed.max-retries="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.retry.mode
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.retry.mode=...
1
spring:
cloud:
azure:
keyvault:
secret:
retry:
mode: "..."
1
java -Dspring.cloud.azure.keyvault.secret.retry.mode="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_RETRY_MODE="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.retry.mode="..."
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.
CAS Property: spring.cloud.azure.keyvault.secret.service-version
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
.properties
files:
1
spring.cloud.azure.keyvault.secret.service-version=...
1
spring:
cloud:
azure:
keyvault:
secret:
service-version: "..."
1
java -Dspring.cloud.azure.keyvault.secret.service-version="..." -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory. Note the placement of the system property which must be
specified before the CAS web application is launched.
1
2
3
export SPRING_CLOUD_AZURE_KEYVAULT_SECRET_SERVICE_VERSION="..."
java -jar build/libs/cas.war
cas.war
with an embedded server container and can be found in the build/libs
directory.
1
java -jar build/libs/cas.war --spring.cloud.azure.keyvault.secret.service-version="..."
cas.war
with an embedded server container and can be found in the build/libs
directory.
Configuration Metadata
The collection of configuration properties listed in this section are automatically generated from the CAS source and components that contain the actual field definitions, types, descriptions, modules, etc. This metadata may not always be 100% accurate, or could be lacking details and sufficient explanations.
Be Selective
This section is meant as a guide only. Do NOT copy/paste the entire collection of settings into your CAS configuration; rather pick only the properties that you need. Do NOT enable settings unless you are certain of their purpose and do NOT copy settings into your configuration only to keep them as reference. All these ideas lead to upgrade headaches, maintenance nightmares and premature aging.
YAGNI
Note that for nearly ALL use cases, declaring and configuring properties listed here is sufficient. You should NOT have to explicitly massage a CAS XML/Java/etc configuration file to design an authentication handler, create attribute release policies, etc. CAS at runtime will auto-configure all required changes for you. If you are unsure about the meaning of a given CAS setting, do NOT turn it on without hesitation. Review the codebase or better yet, ask questions to clarify the intended behavior.
Naming Convention
Property names can be specified in very relaxed terms. For instance cas.someProperty
, cas.some-property
, cas.some_property
are all valid names. While all
forms are accepted by CAS, there are certain components (in CAS and other frameworks used) whose activation at runtime is conditional on a property value, where
this property is required to have been specified in CAS configuration using kebab case. This is both true for properties that are owned by CAS as well as those
that might be presented to the system via an external library or framework such as Spring Boot, etc.
When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value
.
The only possible exception to this rule is when naming actuator endpoints; The name of the
actuator endpoints (i.e. ssoSessions
) MUST remain in camelCase mode.
Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas
. All other settings are controlled and provided
to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with
the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition
or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the
way you intend.
Validation
Configuration properties are automatically validated on CAS startup to report issues with configuration binding, specially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.
Indexed Settings
CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value
. The index [0]
is meant to be
incremented by the adopter to allow for distinct multiple configuration blocks.