From e86170fbf77886773d1da212e9e722efd64685af Mon Sep 17 00:00:00 2001 From: Dave Syer Date: Fri, 18 Mar 2016 11:56:27 +0000 Subject: [PATCH] Clarify how to get encrypted properies to clients Fixes gh-349 --- docs/src/main/asciidoc/spring-cloud-config.adoc | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/src/main/asciidoc/spring-cloud-config.adoc b/docs/src/main/asciidoc/spring-cloud-config.adoc index 65f92598..80872148 100644 --- a/docs/src/main/asciidoc/spring-cloud-config.adoc +++ b/docs/src/main/asciidoc/spring-cloud-config.adoc @@ -671,6 +671,17 @@ TIP: the `{name:value}` prefixes can also be added to plaintext posted to the `/encrypt` endpoint, if you want to let the Config Server handle all encryption as well as decryption. +=== Serving Encrypted Properties + +Sometimes you want the clients to decrypt the configuration locally, +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 +key nor the enabled flag. + == Serving Plain Text Instead of using the `Environment` abstraction (or one of the