spring-cloud / spring-cloud/spring-cloud-config

Custom cipher

Open
#2,310 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

waiting-for-triage
Dominant language
Java
Stars
2k
Forks
1.3k
Avg merge
2d 59m
Merged PRs (30d)
16

Description

Is it possible to define a pattern so that the decryption is going to an endpoint in charge of returning the decrypted value?

Example

APP:
KEY: '{rest-cipher}value-to-decript'

And that with that pattern it identifies all the properties that start with that and execute a function that does the decryption?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name any files, tests, or entry points. First trace how Spring Cloud Config currently handles encrypted values on the client and server, then define the endpoint pattern, decryption contract, and completion criteria before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring, spring-boot
Domain
backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.