SecurityContext API
E836337
The SecurityContext API is a Jakarta Security component that provides programmatic access to authentication and authorization information for the currently executing user within a Jakarta EE application.
All labels observed (1)
| Label | Occurrences |
|---|---|
| SecurityContext API canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T10019537 — 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: SecurityContext API Context triple: [Jakarta Security, defines, SecurityContext API]
-
A.
Permissions API
The Permissions API is a web platform interface that allows developers to query and manage user permission states (such as notifications, geolocation, and camera access) in a standardized way across browsers.
-
B.
Security Service
The Security Service, commonly known as MI5, is the United Kingdom’s domestic counter-intelligence and security agency responsible for protecting national security against threats such as terrorism and espionage.
-
C.
Security Area
The Security Area is the segment of the IETF responsible for developing and overseeing standards and protocols related to Internet and network security.
-
D.
User-based Security Model
The User-based Security Model is a framework for providing authentication, privacy, and access control in SNMPv3 by defining security based on individual user identities and associated cryptographic keys.
-
E.
Permissions API specification
The Permissions API specification is a web standard that defines a unified way for web applications to query and manage user permission states for powerful browser features like notifications, geolocation, and camera access.
- 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: SecurityContext API Target entity description: The SecurityContext API is a Jakarta Security component that provides programmatic access to authentication and authorization information for the currently executing user within a Jakarta EE application.
-
A.
Permissions API
The Permissions API is a web platform interface that allows developers to query and manage user permission states (such as notifications, geolocation, and camera access) in a standardized way across browsers.
-
B.
Security Service
The Security Service, commonly known as MI5, is the United Kingdom’s domestic counter-intelligence and security agency responsible for protecting national security against threats such as terrorism and espionage.
-
C.
Security Area
The Security Area is the segment of the IETF responsible for developing and overseeing standards and protocols related to Internet and network security.
-
D.
User-based Security Model
The User-based Security Model is a framework for providing authentication, privacy, and access control in SNMPv3 by defining security based on individual user identities and associated cryptographic keys.
-
E.
Permissions API specification
The Permissions API specification is a web standard that defines a unified way for web applications to query and manage user permission states for powerful browser features like notifications, geolocation, and camera access.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf |
Jakarta Security API component
ⓘ
programmatic security API ⓘ |
| abstracts | container-specific security details ⓘ |
| allows |
accessing security context information independent of underlying container
ⓘ
checking if a caller is in a given role ⓘ retrieving the current caller principal ⓘ triggering authentication mechanisms ⓘ |
| belongsToSpecification |
Jakarta Security specification
ⓘ
linked to:
Jakarta Security
|
| category |
application security
ⓘ
enterprise Java security ⓘ |
| conformsTo | Jakarta Security specification versions starting from Jakarta EE 8 era ⓘ |
| designedFor |
Jakarta RESTful Web Services resources
ⓘ
linked to:
Jakarta RESTful Web Services
enterprise beans ⓘ server-side components ⓘ servlets ⓘ |
| exposes |
methods to check caller roles
ⓘ
methods to obtain caller principal ⓘ methods to perform authentication ⓘ methods to query authentication status ⓘ |
| goal |
provide a consistent security API across Jakarta EE technologies
ⓘ
simplify programmatic security in Jakarta EE ⓘ |
| integratesWith |
Jakarta Authentication
ⓘ
Jakarta Authorization ⓘ Jakarta RESTful Web Services ⓘ Servlet containers ⓘ |
| introducedInContextOf | modernization of Java EE security under Jakarta EE ⓘ |
| partOf |
Jakarta EE
ⓘ
Jakarta Security ⓘ |
| provides |
programmatic access to authentication information
ⓘ
programmatic access to authorization information ⓘ |
| relatedTo |
HttpAuthenticationMechanism API
ⓘ
IdentityStore API ⓘ |
| replaced | some programmatic security use cases from Java EE security APIs ⓘ |
| scope | currently executing user ⓘ |
| standardizedBy |
Eclipse Foundation Jakarta EE Working Group
ⓘ
linked to:
Jakarta EE Working Group
|
| supports |
container-managed security integration
ⓘ
identity store–based authentication ⓘ role-based access control ⓘ |
| targetAudience | Jakarta EE application developers ⓘ |
| usedFor |
custom authentication flows
ⓘ
fine-grained access control decisions in code ⓘ integration with external identity providers ⓘ |
| usedIn | Jakarta EE applications ⓘ |
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: SecurityContext API Description of subject: The SecurityContext API is a Jakarta Security component that provides programmatic access to authentication and authorization information for the currently executing user within a Jakarta EE application.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.