To configure an asymmetric key you can either set the key as a
PEM-encoded text value (in encrypt.key), or via a keystore (e.g. as
created by the keytool utility that comes with the JDK). The
-keystore properties are encrypt.keyStore. with equals to
-location (a Resource location), password (to unlock the
-keystore) and alias (to identify which key in the store is to be
+keystore properties are encrypt.keyStore.* with * equal to
location (a Resource location),
password (to unlock the keystore) and
alias (to identify which key in the store is to be
used).
The encryption is done with the public key, and a private key is @@ -522,8 +933,8 @@ individual bean by name. This functionality is exposed in the
The Config Client has an Environment pre-processor for decrypting
property values locally. It follows the same rules as the Config
-Server, and has the same external configuration via encrypt.. Thus
-you can use encrypted values in the form {cipher} and as long as
+Server, and has the same external configuration via encrypt.*. Thus
+you can use encrypted values in the form {cipher}* and as long as
there is a valid key then they will be decrypted before the main
application context gets the Environment.
Environment.
For a Spring Boot Actuator application there are some additional management endpoints:
-* POST to /env to update the Environment and rebind @ConfigurationProperties and log levels
-* /refresh for re-loading the boot strap context and refreshing the @RefreshScope beans
-* /restart for closing the ApplicationContext and restarting it (disabled by default)
-* /pause and /resume for calling the Lifecycle methods (stop() and start() on the ApplicationContext)
For a Spring Boot Actuator application there are some additional management endpoints:
+POST to /env to update the Environment and rebind @ConfigurationProperties and log levels
/refresh for re-loading the boot strap context and refreshing the @RefreshScope beans
/restart for closing the ApplicationContext and restarting it (disabled by default)
/pause and /resume for calling the Lifecycle methods (stop() and start() on the ApplicationContext)
Environment
which is the source of external properties for any Spring
-application. Bootstrap properties are added with hight precedence, so
+application. Bootstrap properties are added with high precedence, so
they cannot be overridden by local configuration.