-
Notifications
You must be signed in to change notification settings - Fork 63.1k
Open
Labels
contentThis issue or pull request belongs to the Docs Content teamThis issue or pull request belongs to the Docs Content teamgithub appsContent related to GitHub AppsContent related to GitHub Appsnever-staleDo not close as staleDo not close as stale
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
- https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/managing-private-keys-for-github-apps#storing-private-keys)
- https://docs.github.com/en/apps/creating-github-apps/about-creating-github-apps/best-practices-for-creating-a-github-app#private-keys
What part(s) of the article would you like to see updated?
In two places in GitHub app docs, here and here, there is a statement that "Consider storing your GitHub App's private key in a key vault, such as Azure Key Vault, and making it sign-only." As previously discussed, this information is provided without an example of how to do this.
This can now be done with az keyvault key sign, likely due to a recent fix in this space. This documentation should be updated with clear examples of how to do this, comparable to what already exists for JWT tokens.
Additional information
This is a documentation improvement related to GitHub app security.
Metadata
Metadata
Assignees
Labels
contentThis issue or pull request belongs to the Docs Content teamThis issue or pull request belongs to the Docs Content teamgithub appsContent related to GitHub AppsContent related to GitHub Appsnever-staleDo not close as staleDo not close as stale