spring-cloud / spring-cloud/spring-cloud-config
Decryption not working on non-embedded tomcat environments.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Hello all,
Have a scenario where we have Cloud Config, Eureka, Zuul and Spring Boot Client setup. When running all using embedded tomcats decryption of client properties works (using config server encryption)...
Issue we're having when running the infrastructure on non embeded tomcats (built as .war files) and deployed the decryption of configuration ceases to work and the clients are receiving the configs unencrypted '{cipher}etc-etc', thus meaning jibberish to the client.
The encrypt/decrypt endpoints work fine from the config server point of view, just wondering whether there is an extra client or configuration service config that is needed to enable decryption to work in a standalone setup.
Thanks in advance.
J
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report provides no files, tests, or entry points. Start by reproducing the configuration flow with embedded and non-embedded Tomcat deployments, then compare the client behavior and confirm that the deployed clients receive decrypted properties rather than values beginning with {cipher}.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100