lasdf1234 opened a new issue, #12296: URL: https://github.com/apache/gravitino/issues/12296
### Describe the feature Add a durable `GravitinoSecretProvider` implementation so entity connection secrets survive Gravitino process restarts. Initial scope: - Persist ciphertext outside entity `properties` (dedicated store / table) - Keep the master key outside the DB (env / file / optional KMS) - Support `writeSecret` / `readSecret` / `deleteSecret` across provider reopen - Register via existing `gravitino.secret.provider.<name>.*` configuration ### Motivation `InMemorySecretsProvider` is process-local and loses secrets on restart, so it is only suitable for tests and local quick-start. Production deployments need a restart-safe backend that does not keep plaintext secrets in entity metadata. ### Describe the solution Implement an encrypted local backend behind `GravitinoSecretProvider` (for example JDBC/table storage with AEAD such as AES-GCM, using `SecretWriteContext` as AAD). Document master-key configuration and basic rotation caveats. Reuse the provider registry introduced for entity secrets (#12218). -- 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]
