diff --git a/1.4.x/multi/multi__spring_cloud_config_server.html b/1.4.x/multi/multi__spring_cloud_config_server.html index 5d854e13..ff1dc45b 100644 --- a/1.4.x/multi/multi__spring_cloud_config_server.html +++ b/1.4.x/multi/multi__spring_cloud_config_server.html @@ -592,7 +592,7 @@ handle all encryption as well as decryption.

encrypt.* configuration to locate a key), but you need to explicitly switch off -the decryption of outgoing properties using -spring.cloud.config.server.encrypt.enabled=false. If you don’t care -about the endpoints, then it should work if you configure neither the +the decryption of outgoing properties by placing +spring.cloud.config.server.encrypt.enabled=false in bootstrap.[yml|properties]. +If you don’t care about the endpoints, then it should work if you configure neither the key nor the enabled flag.

\ No newline at end of file diff --git a/1.4.x/single/spring-cloud-config.html b/1.4.x/single/spring-cloud-config.html index 15d7b8c6..c121ce8d 100644 --- a/1.4.x/single/spring-cloud-config.html +++ b/1.4.x/single/spring-cloud-config.html @@ -694,9 +694,9 @@ handle all encryption as well as decryption.

encrypt.* configuration to locate a key), but you need to explicitly switch off -the decryption of outgoing properties using -spring.cloud.config.server.encrypt.enabled=false. If you don’t care -about the endpoints, then it should work if you configure neither the +the decryption of outgoing properties by placing +spring.cloud.config.server.encrypt.enabled=false in bootstrap.[yml|properties]. +If you don’t care about the endpoints, then it should work if you configure neither the key nor the enabled flag.

3. Serving Alternative Formats

The default JSON format from the environment endpoints is perfect for consumption by Spring applications because it maps directly onto the Environment abstraction. If you prefer you can consume the same data diff --git a/1.4.x/spring-cloud-config.xml b/1.4.x/spring-cloud-config.xml index 107086fb..f010cf3e 100644 --- a/1.4.x/spring-cloud-config.xml +++ b/1.4.x/spring-cloud-config.xml @@ -1133,9 +1133,9 @@ handle all encryption as well as decryption. instead of doing it in the server. In that case you can still have /encrypt and /decrypt endpoints (if you provide the encrypt.* configuration to locate a key), but you need to explicitly switch off -the decryption of outgoing properties using -spring.cloud.config.server.encrypt.enabled=false. If you don’t care -about the endpoints, then it should work if you configure neither the +the decryption of outgoing properties by placing +spring.cloud.config.server.encrypt.enabled=false in bootstrap.[yml|properties]. +If you don’t care about the endpoints, then it should work if you configure neither the key nor the enabled flag.