Clarify how authentication works for /applications. · CreamCoderz/developer.github.com@3f03245 · GitHub

CreamCoderz / developer.github.com Public

forked from github/developer.github.com

• Notifications You must be signed in to change notification settings
• Fork 0
• Star 0

• Code
• Pull requests
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit 3f03245

Browse filesBrowse the repository at this point in the historyBrowse files

GithubGeekJoelLOL

committed

Clarify how authentication works for /applications.

1 parent 2096c3e commit 3f03245
Copy full SHA for 3f03245

1 file changed

+4-2Lines changed: 4 additions & 2 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• content/v3
  • oauth.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎content/v3/oauth.md‎

Copy file name to clipboardExpand all lines: content/v3/oauth.md

+4-2Lines changed: 4 additions & 2 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -286,8 +286,10 @@ You can only send one of these scope keys at a time.
286	286
287	287	OAuth applications can use a special API method for checking OAuth token
288	288	validity without running afoul of normal rate limits for failed login attempts.
289		- This method uses **OAuth application client_id and secret** using **Basic
290		- Authentication.** Invalid tokens will return `404 NOT FOUND`.
	289	+ Authentication works differently with this particular endpoint. You must use
	290	+ Basic Authentication when accessing it, where the username is the OAuth
	291	+ application `client_id` and the password is its `client_secret`. Invalid tokens
	292	+ will return `404 NOT FOUND`.
291	293
292	294	GET /applications/:client_id/tokens/:access_token
293	295

0 commit comments

Comments

0 (0)