HTTP authentication framework
E205826
The HTTP authentication framework is the standardized mechanism in HTTP for challenging clients and transmitting credentials to control access to web resources.
All labels observed (3)
| Label | Occurrences |
|---|---|
| HTTP Digest Access Authentication | 1 |
| HTTP authentication framework canonical | 1 |
| WWW-Authenticate | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1844249 — 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: HTTP authentication framework Context triple: [RFC 7235, defines, HTTP authentication framework]
-
A.
FLASK security architecture
FLASK security architecture is a flexible, fine-grained access control framework originally developed for the Flask microkernel to support mandatory access control policies and later used as the foundation for systems like SELinux.
-
B.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
C.
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.
-
D.
Kerberos
Kerberos is a small, irregularly shaped moon of Pluto discovered in 2011 as part of the Pluto system’s complex family of satellites.
-
E.
Kerberos
Kerberos is a network authentication protocol that uses secret-key cryptography to securely verify the identity of users and services in distributed systems.
- 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: HTTP authentication framework Target entity description: The HTTP authentication framework is the standardized mechanism in HTTP for challenging clients and transmitting credentials to control access to web resources.
-
A.
FLASK security architecture
FLASK security architecture is a flexible, fine-grained access control framework originally developed for the Flask microkernel to support mandatory access control policies and later used as the foundation for systems like SELinux.
-
B.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
C.
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.
-
D.
Kerberos
Kerberos is a small, irregularly shaped moon of Pluto discovered in 2011 as part of the Pluto system’s complex family of satellites.
-
E.
Kerberos
Kerberos is a network authentication protocol that uses secret-key cryptography to securely verify the identity of users and services in distributed systems.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP protocol feature
ⓘ
web authentication framework ⓘ |
| allowsExtension | new authentication schemes ⓘ |
| allowsScheme |
AWS4-HMAC-SHA256 authentication
ⓘ
Basic authentication ⓘ Bearer authentication ⓘ Digest authentication ⓘ HOBA ⓘ Mutual authentication ⓘ Negotiate authentication ⓘ SCRAM authentication ⓘ |
| appliesToProtocol |
HTTP/1.1
ⓘ
HTTP/2 ⓘ HTTP/3 ⓘ |
| backwardsCompatibleWith | HTTP/1.0 Basic authentication ⓘ |
| definedInStandard | RFC 7235 ⓘ |
| hasComponent |
authentication parameters
ⓘ
challenge syntax ⓘ credentials syntax ⓘ |
| introduced | 1997 ⓘ |
| operatesAtLayer | application layer ⓘ |
| partOf |
HTTP
ⓘ
surface form:
Hypertext Transfer Protocol
|
| purpose |
challenge clients for credentials
ⓘ
control access to HTTP resources ⓘ transmit authentication credentials ⓘ |
| relatedTo |
HTTP authorization
ⓘ
access control ⓘ web security ⓘ |
| revisedByStandard | RFC 9110 ⓘ |
| securityProperty |
does not mandate encryption
ⓘ
recommends use with TLS ⓘ |
| specifiedInSection |
RFC 7235
ⓘ
surface form:
RFC 7235 Section 2
|
| standardizedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| standardizedIn |
HTTP Working Group
ⓘ
surface form:
IETF HTTP Working Group
|
| supportsConcept |
authentication scheme
ⓘ
challenge ⓘ credentials ⓘ origin server ⓘ protection space ⓘ proxy server ⓘ realm ⓘ status code 401 Unauthorized ⓘ status code 407 Proxy Authentication Required ⓘ user agent ⓘ |
| usesHeader |
Authorization
ⓘ
Proxy-Authenticate ⓘ Proxy-Authorization ⓘ WWW-Authenticate ⓘ |
| usesMechanism | challenge-response ⓘ |
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: HTTP authentication framework Description of subject: The HTTP authentication framework is the standardized mechanism in HTTP for challenging clients and transmitting credentials to control access to web resources.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.