LiJie20190102 opened a new issue, #14399:
URL: https://github.com/apache/gravitino/issues/14399
### Describe the subtask
**Priority:** P0
**Dependencies:** #<id-2>, #<id-3>. May proceed in parallel with #<id-5>.
**Problem:** Sensitive server configuration values such as
`gravitino.entity.store.relational.jdbcPassword` are stored in cleartext in
`gravitino.conf`. The entity store's own password cannot live in the secret
table backed by
that same entity store, so it must be encrypted directly with the master key.
**Scope:**
- A recognizable marker syntax for ciphertext values so plaintext and
ciphertext coexist in
the same file (exact syntax settled during development, per design doc
ยง5.5).
- Transparent decryption once at startup with the in-memory master key; the
first supported
key is `gravitino.entity.store.relational.jdbcPassword`, with additional
keys enabled
incrementally.
- Backward-compatible parsing: a value without the marker is used as-is.
- An encrypted value with no resolvable master key fails startup with an
explicit error; no
default-key fallback.
- The marker applies to server configuration only; entity properties keep the
`urn:gravitino-secret` recognition rule.
- Unit tests for marker parsing, decryption, plaintext compatibility, and
startup failure.
#14396
### Parent issue
#14396
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
