-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Support credential vending in Gravitino #4398
Labels
epic
Key feature
Comments
This is the Proposal of the secret management system, which should be related to credentials vending https://docs.google.com/document/d/1CUUtUXJHU89zbaOUkQRMVTfbAS5qlg_xiz5y6kHd37s/edit |
based on the design of @lw-yang , proposed a new design https://docs.google.com/document/d/1fovK0ylSmI45ynrCPcnRZqzyPDn7DRNb_ExdbjVPq0k/edit |
This was referenced Sep 23, 2024
This was referenced Nov 20, 2024
This was referenced Dec 6, 2024
Abyss-lord
pushed a commit
to Abyss-lord/gravitino
that referenced
this issue
Dec 29, 2024
…er (apache#5995) ### What changes were proposed in this pull request? add credential cache for Gravitino server, not support for Iceberg rest server yet. ### Why are the changes needed? Fix: apache#4398 ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? testing in local env, get credential from Gravitino server and see whether it's fetched from remote or local cache
This was referenced Jan 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the proposal
As a centralized service, Gravitino should provide a mechanism to let third-party applications/service integrate with it to get temporary access to the underlying services, like S3, HDFS, HMS, etc on behalf of their users. the credential vending mechanism is heavily adopted in the cloud service. So Gravitino should provide a similar mehanism.
Task list
The text was updated successfully, but these errors were encountered: