OAuth Working Group

E697199

IETF working group standards development organization unit

The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

All labels observed (3)

Label	Occurrences
IETF OAuth Working Group	1
OAuth WG	1
OAuth Working Group canonical	1

How this entity was disambiguated

This entity first appeared as the object of triple T7933983 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: OAuth Working Group
Context triple: [RFC 6749, workingGroup, OAuth Working Group]

A. HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
B. OAuth 2.0
OAuth 2.0 is an industry-standard authorization framework that enables applications to obtain limited access to user resources on HTTP services without exposing user credentials.
C. OpenID Connect
OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
D. W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
E. W3C Working Group
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: OAuth Working Group
Target entity description: The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.

A. HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
B. OAuth 2.0
OAuth 2.0 is an industry-standard authorization framework that enables applications to obtain limited access to user resources on HTTP services without exposing user credentials.
C. OpenID Connect
OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
D. W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
E. W3C Working Group
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
F. None of above. chosen

Statements (49)

Predicate	Object
instanceOf	IETF working group ⓘ standards development organization unit ⓘ
abbreviation	OAuth WG ⓘ linked to: OAuth Working Group
area	Security Area ⓘ
field	authorization protocols ⓘ identity and access management ⓘ web security ⓘ
goal	develop and maintain OAuth protocol standards ⓘ enable secure delegated authorization on the web ⓘ
hasCommunicationChannel	mailing list ⓘ
meetsAt	IETF meetings ⓘ
parentOrganization	Internet Engineering Task Force ⓘ
produces	Internet-Drafts ⓘ RFCs ⓘ
scope	authorization framework ⓘ client and authorization server interaction ⓘ security best practices for OAuth ⓘ token usage ⓘ
standardizes	Bearer Token Usage ⓘ JSON Web Token Profile for OAuth 2.0 Access Tokens ⓘ linked to: JSON Web Tokens (JWT) OAuth 2.0 ⓘ OAuth 2.0 Authorization Server Issuer Identification ⓘ OAuth 2.0 Authorization Server Metadata ⓘ OAuth 2.0 Demonstrating Proof-of-Possession at the Application Layer (DPoP) ⓘ OAuth 2.0 Device Authorization Grant ⓘ linked to: OAuth 2.0 OAuth 2.0 Dynamic Client Registration ⓘ linked to: Dynamic Client Registration OAuth 2.0 Incremental Authorization ⓘ linked to: OAuth 2.0 OAuth 2.0 JWT Secured Authorization Request (JAR) ⓘ linked to: OAuth 2.0 OAuth 2.0 JWT-Secured Authorization Response Mode (JARM) ⓘ OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens ⓘ OAuth 2.0 Pushed Authorization Requests ⓘ linked to: OAuth 2.0 OAuth 2.0 Resource Indicators ⓘ linked to: OAuth 2.0 OAuth 2.0 Rich Authorization Requests ⓘ linked to: OAuth 2.0 OAuth 2.0 Security Best Current Practice ⓘ OAuth 2.0 Security Topics ⓘ linked to: OAuth 2.0 OAuth 2.0 Step-up Authentication Challenge Protocol ⓘ linked to: OAuth 2.0 OAuth 2.0 Token Exchange ⓘ linked to: OAuth 2.0 OAuth 2.0 Token Introspection ⓘ linked to: OAuth 2.0 OAuth 2.0 Token Revocation ⓘ linked to: OAuth 2.0 OAuth 2.0 for Browser-Based Apps ⓘ linked to: OAuth 2.0 OAuth 2.0 for Native Apps ⓘ linked to: OAuth 2.0 OAuth 2.1 ⓘ linked to: OAuth 2.0 Proof Key for Code Exchange ⓘ
topic	access tokens ⓘ authorization server security ⓘ client authentication ⓘ secure authorization ⓘ
usesProcess	IETF consensus process ⓘ
website	https://datatracker.ietf.org/wg/oauth ⓘ

How these facts were elicited

Referenced by (3)

Full triples — surface form annotated when it differs from this entity's canonical label.

RFC 6749 → workingGroup → OAuth Working Group ⓘ

RFC 6750 → standardsBody → IETF OAuth Working Group ⓘ

linked to: OAuth Working Group

OAuth Working Group → abbreviation → OAuth WG ⓘ