Skip to main content

485 Search results for "token"

Apps / Creating GitHub Apps / Authenticate with a GitHub App /

About authentication with a GitHub App

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

GitHub Actions / Security / Security harden deployments /

Configuring OpenID Connect in Azure

identity, and includes a workflow example for the azure/login action that uses tokens to authenticate to Azure and access resources. Prerequisites To learn the

GitHub Actions / Security / Security harden deployments /

Configuring OpenID Connect in HashiCorp Vault

strategy to ensure that access tokens are only allocated in a predictable way. To control how your cloud provider issues access tokens, you must define at least

GitHub Packages / Working with a GitHub Packages registry /

Working with the Apache Maven registry

personal access token (classic). For more information, see "Managing your personal access tokens." You need an access token to publish, install

REST API /

REST API endpoints for apps

an installation access token for an app Suspend an app installation Unsuspend an app installation Create a scoped access token Get an app Get an organization

Code security / Dependabot / Work with Dependabot /

Guidance for the configuration of private registries for Dependabot

and ProGet. You can authenticate with either a username and password, or a token. For more information, see rubygems-server in Configuring access to private

Migrations / GitHub Enterprise Importer / Complete migration /

Accessing your migration logs for GitHub Enterprise Importer

personal access token with access to the destination organization, add --github-target-pat TOKEN, replacing TOKEN with the personal access token. For personal

REST API / Deploy keys /

REST API endpoints for deploy keys

a personal access token, deleting the personal access token will also delete the deploy key. Regenerating the personal access token will not delete the

Code security / Dependabot / Work with Dependabot /

Configuring access to private registries for Dependabot

registries. You can store authentication information, like passwords and access tokens, as encrypted secrets and then reference these in the Dependabot configuration

GitHub Actions / Security / Security harden deployments /

Configuring OpenID Connect in Amazon Web Services

workflow example for the aws-actions/configure-aws-credentials that uses tokens to authenticate to AWS and access resources. Note Support for custom claims