RFC 6749
E184245
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 6749 canonical | 4 |
| The OAuth 2.0 Authorization Framework | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1634859 — 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: RFC 6749 Context triple: [OAuth 2.0, standardizedIn, RFC 6749]
-
A.
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.
-
B.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
C.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
D.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
E.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
- 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: RFC 6749 Target entity description: RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
A.
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.
-
B.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
C.
RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
D.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
E.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
Internet standard specification ⓘ OAuth 2.0 specification ⓘ |
| addresses | third-party application access to HTTP services ⓘ |
| appliesTo |
browser-based applications
ⓘ
native applications ⓘ server-side applications ⓘ web applications ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
OAuth 2.0 authorization endpoint
ⓘ
OAuth 2.0 authorization framework ⓘ
linked to:
OAuth 2.0
OAuth 2.0 authorization grant types ⓘ OAuth 2.0 token endpoint ⓘ access token ⓘ authorization server ⓘ client ⓘ client credentials ⓘ redirect URI ⓘ refresh token ⓘ resource owner ⓘ resource server ⓘ roles in OAuth 2.0 ⓘ scope parameter ⓘ |
| definesGrantType |
authorization code grant
ⓘ
client credentials grant ⓘ implicit grant ⓘ resource owner password credentials grant ⓘ |
| focusesOn |
HTTP-based APIs
ⓘ
delegated authorization ⓘ secure access to protected resources ⓘ |
| language | English ⓘ |
| obsoletes | RFC 5849 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| recommends | use of TLS ⓘ |
| relatedTo |
OAuth 2.0
ⓘ
RFC 6750 ⓘ |
| rfcNumber | 6749 ⓘ |
| securityConsiderations |
phishing attacks
ⓘ
redirect URI manipulation ⓘ token leakage ⓘ |
| standardizes |
interaction between client and authorization server
ⓘ
interaction between client and resource server ⓘ |
| status | Proposed Standard ⓘ |
| title |
The OAuth 2.0 Authorization Framework
ⓘ
linked to:
OAuth 2.0
|
| useCase | secure delegated access to web resources ⓘ |
| usesProtocol | HTTP ⓘ |
| workingGroup | OAuth Working Group ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 6749 Description of subject: RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.