SpringCloud/spring-cloud-config
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Some clarifications on encryption and multiple keys

Browse Source
This commit is contained in:
Dave Syer
2015-12-18 10:23:28 +00:00
parent 9a65a2f1a8
commit 99b6064dc7
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/src/main/asciidoc/spring-cloud-config.adoc
View File

@@ -508,15 +508,17 @@ are special characters ('+' is particularly tricky).
Take the encrypted value and add the `{cipher}` prefix before you put
it in the YAML or properties file, and before you commit and push it
to a remote, potentially insecure store. The `/encrypt` and `/decrypt`
endpoints also both accept paths of the form `/*/{name}/{profiles}`
which can be used to control cryptography per application (name)
and profile when clients call into the main Environment resource.
to a remote, potentially insecure store.
The `/encrypt` and `/decrypt` endpoints also both accept paths of the
form `/*/{name}/{profiles}` which can be used to control cryptography
per application (name) and profile when clients call into the main
Environment resource.
NOTE: to control the cryptography in this granular way you must also
provide a `@Bean` of type `TextEncryptorLocator` that creates a
different encryptor per name and profiles. The one that is provided
by default does not do this.
by default does not do this (so all encryptions use the same key).
The `spring` command line client (with Spring Cloud CLI extensions
installed) can also be used to encrypt and decrypt, e.g.