OAuth 2.0
protocol
Overview
Developed byInternet Engineering Task Force (IETF)
LicenseOpen Standard
Open source✓ Open Source
Use caseauthorization framework for third-party access to user resources
Technical
Protocols
Integrates with
Knowledge graph stats
Claims31
Avg confidence95%
Avg freshness100%
Last updatedUpdated yesterday
WikidataQ97371579
Trust distribution
100% unverified
Governance
Not assessed
OAuth 2.0
concept
Industry-standard authorization framework for delegated API access
Compare with...defined in rfc
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| RFC 6749 | ○Unverified | High | Fresh | 1 |
primary use case
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| authorization framework for third-party access to user resources | ○Unverified | High | Fresh | 1 |
| Authorization framework for third-party application access | ○Unverified | High | Fresh | 1 |
| Authorization framework for third-party applications | ○Unverified | High | Fresh | 1 |
| authorization framework for delegated access to APIs and resources | ○Unverified | High | Fresh | 1 |
supports flow type
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| implicit flow | ○Unverified | High | Fresh | 1 |
| Authorization Code Flow | ○Unverified | High | Fresh | 1 |
| Client Credentials Flow | ○Unverified | High | Fresh | 1 |
supersedes
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| OAuth 1.0 | ○Unverified | High | Fresh | 1 |
specification type
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| RFC 6749 | ○Unverified | High | Fresh | 1 |
open source
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| true | ○Unverified | High | Fresh | 1 |
used by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Clerk | ○Unverified | High | Fresh | 1 |
| Auth0 | ○Unverified | High | Fresh | 1 |
| Facebook Login | ○Unverified | High | Fresh | 1 |
| Twitter API | ○Unverified | High | Fresh | 1 |
| Google APIs | ○Unverified | High | Fresh | 1 |
| GitHub API | ○Unverified | High | Fresh | 1 |
first released
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| 2012 | ○Unverified | High | Fresh | 1 |
standardized by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| IETF | ○Unverified | High | Fresh | 1 |
developed by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) | ○Unverified | High | Fresh | 1 |
| Internet Engineering Task Force | ○Unverified | High | Fresh | 1 |
| IETF OAuth Working Group | ○Unverified | High | Fresh | 1 |
supports protocol
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| HTTPS | ○Unverified | High | Fresh | 1 |
successor of
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| OAuth 1.0 | ○Unverified | High | Fresh | 1 |
published year
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| 2012 | ○Unverified | High | Fresh | 1 |
license type
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Open Standard | ○Unverified | High | Fresh | 1 |
extended by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| RFC 7636 (PKCE) | ○Unverified | High | Fresh | 1 |
based on
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| bearer token authentication | ○Unverified | High | Fresh | 1 |
integrates with
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| OpenID Connect | ○Unverified | High | Fresh | 1 |
alternative to
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| SAML authentication | ○Unverified | Moderate | Fresh | 1 |
| SAML | ○Unverified | Moderate | Fresh | 1 |