About authentication with a GitHub App - GitHub Docs
docs.github.com · 324 words · saved by 1 readers
Your GitHub App can authenticate as itself, as an app installation, or on behalf of a user.
Your GitHub App can authenticate as itself, as an app installation, or on behalf of a user. Authentication as a GitHub App To authenticate as itself, your app will use a JSON Web Token (JWT). Your app should authenticate as itself when it needs to generate an installation access token. An installation access token is required to authenticate as an app installation. Your app should also authenticate as itself when it needs to make API requests to manage resources related to the app. For example, when it needs to list the accounts where it is installed. For more information, see…
saved by
related reading
- Authenticating as a GitHub App installation - GitHub Docsdocs.github.com
- About creating GitHub Apps - GitHub Docsdocs.github.com
- Building a GitHub App that responds to webhook events - GitHub Docsdocs.github.com
- Auth | Supabase Docssupabase.com
- How to Manage GitHub Actions Secretsinfisical.com
- Authenticate Using Google with JavaScript | Firebase Authenticationfirebase.google.com
- GitHub - cased/skyline: The missing automation for creating GitHub Appsgithub.com
- Secure AI Agent & User Authentication | Auth0auth0.com
- Overview - Notion Docsdevelopers.notion.com
- What is Private Key JWT: Deep dive into asymmetric client authentication — WorkOSworkos.com
- Display the Sign In With Google button | Web guides | Google for Developersdevelopers.google.com
- Authorization Academy - What is Authorization?osohq.com