582812b3ec
website: Copy files during build. website: Allow for mixed env builds. website: Reduce build size. website: Expose build. website: Add build memory debugging. WIP: Disable broken links check to compare memory usage. website: Update deps. website: Clean up API paths. website: Flesh out 3.8 fixes. Format. website: Update ignore paths. Website: Clean up integrations build. website: Fix paths. website: Optimize remark. website: Update deps. website: Format. website: Remove linking. website: Fix paths. wip: Attempt API only build. Prep. Migrate render to runtime. Tidy sidebar. Clean up templates. docs: Move directory. WIP docs: Flesh out split. website: Fix issue where routes have collisions.
1.2 KiB
1.2 KiB
title
| title |
|---|
| GitHub compatibility |
The OAuth2 provider also exposes a GitHub-compatible endpoint. This endpoint can be used by applications, which support authenticating against GitHub Enterprise, but not generic OpenID Connect.
To use any of the GitHub Compatibility scopes, you have to use the GitHub Compatibility Endpoints.
| Endpoint | URL |
|---|---|
| Authorization | /login/oauth/authorize |
| Token | /login/oauth/access_token |
| User Info | /user |
| User Teams Info | /user/teams |
To access the user's email address, a scope of user:email is required. To access their groups, read:org is required. Because these scopes are handled by a different endpoint, they are not customisable as a Scope Mapping.
Special scopes for GitHub compatibility
user: No-op, is accepted for compatibility but does not give access to any resourcesread:user: Same as aboveuser:email: Allows read-only access to/user, including email addressread:org: Allows read-only access to/user/teams, listing all the user's groups as teams.