-
Notifications
You must be signed in to change notification settings - Fork 94
Adjust RBAC scope best-practices for SSH private keys #84
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
base: main
Are you sure you want to change the base?
Adjust RBAC scope best-practices for SSH private keys #84
Conversation
@FlorentATo : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit 5d6880a: ✅ Validation status: passed
For more details, please refer to the build report. |
@msmbaldwin - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Co-authored-by: Regan Downer <[email protected]>
Co-authored-by: Regan Downer <[email protected]>
Learn Build status updates of commit a4e0ae5: ✅ Validation status: passed
For more details, please refer to the build report. |
Learn Build status updates of commit f742998: ✅ Validation status: passed
For more details, please refer to the build report. |
This suggestion expends the list of exception to include user-scoped roles for reading individual private SSH key from Bastion UI.
This scenario allows cloud administrators to use of a single instance of Key Vault to centrally manage users' private SSH keys, while restricting access to individual keys to said users using Azure RBAC.
This is useful in situations where having a local copy of the private key isn't desired (e.g. for users with decentralized access).
URL: https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-guide?tabs=azure-cli