Skip to main content
ドキュメントには� �繁に更新が� えられ、その都度公開されています。本ページの翻訳はま� 未完成な部分があることをご了承く� さい。最新の情� �については、英語のドキュメンテーションをご参照く� さい。本ページの翻訳に問題がある� �合はこちらまでご連絡く� さい。

このバージョンの GitHub Enterprise はこの日付をもって終了となりました: 2022-06-03. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、最新バージョンのGitHub Enterpriseにアップグレードしてく� さい。 アップグレードに関する支援については、GitHub Enterprise supportに連絡してく� さい。

Authorizing OAuth Apps

You can connect your GitHub Enterprise Server identity to third-party applications using OAuth. When authorizing an OAuth App, you should ensure you trust the application, review who it's developed by, and review the kinds of information the application wants to access.

When an OAuth App wants to identify you by your account on GitHub Enterprise Serverインスタンス, you'll see a page with the app's developer contact information and a list of the specific data that's being requested.

OAuth App access

OAuth App can have read or write access to your GitHub Enterprise Server data.

  • Read access only allows an app to look at your data.
  • Write access allows an app to change your data.

Tip: 認可されたインテグレーションを定期的にレビューすることをおすすめします。 しばらくの間使われていないアプリケーションやトークンは削除してく� さい。 詳しい情� �については「認可されたインテグレーションのレビュー」を参照してく� さい。

About OAuth scopes

Scopes are named groups of permissions that an OAuth App can request to access both public and non-public data.

When you want to use an OAuth App that integrates with GitHub Enterprise Server, that app lets you know what type of access to your data will be required. If you grant access to the app, then the app will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests user:email scope, the app will have read-only access to your private email addresses. For more information, see "About scopes for OAuth App."

Note: Currently, you can't scope source code access to read-only.

ユーザ/アプリケーション/スコープの組み合わせごとに、発行できるトークン数には10という上限があります。 If an application creates more than 10 tokens for the same user and the same scopes, the oldest tokens with the same user/application/scope combination will be revoked.

Types of requested data

OAuth App can request several types of data.

Type of dataDescription
Commit statusYou can grant access for an app to report your commit status. Commit status access allows apps to determine if a build is a successful against a specific commit. Apps won't have access to your code, but they can read and write status information against a specific commit.
DeploymentsDeployment status access allows apps to determine if a deployment is successful against a specific commit for public and private repositories. Apps won't have access to your code.
GistsGist access allows apps to read or write to both your public and secret Gists.
HooksWebhooks access allows apps to read or write hook configurations on repositories you manage.
NotificationsNotification access allows apps to read your GitHub Enterprise Server notifications, such as comments on issues and pull requests. However, apps remain unable to access anything in your repositories.
Organizations and teamsOrganization and teams access allows apps to access and manage organization and team membership.
Personal user dataUser data includes information found in your user profile, like your name, e-mail address, and location.
RepositoriesRepository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level.
Repository deleteApps can request to delete repositories that you administer, but they won't have access to your code.

Requesting updated permissions

When OAuth App request new access permissions, they will notify you of the differences between their current permissions and the new permissions.