Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit997f34e

Browse files
committed
Merge pull requestgithub#677 from github/izuzak-no-implicit-flow-in-oauth
Add a note to OAuth docs to clarify that GitHub's OAuth implementation doesn't support the implicit flow
2 parents1b50009 +3fc836e commit997f34e

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

‎content/v3/oauth.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ and Client Secret. The Client Secret should not be shared.
2020
**You may create a[personal access token](https://github.com/settings/tokens/new)
2121
for your own use or implement the web flow below to allow other users to authorize your application.**
2222

23+
GitHub's OAuth implementation supports the standard[authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1). Developers should implement the web application flow described below to obtain an authorization code and then exchange it for a token. (The[implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.)
24+
2325
##Web Application Flow
2426

2527
This is a description of the OAuth2 flow from 3rd party web sites.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp