How deeply does Quarkus in Action cover security context?

Explains injection, principal lookup, anonymous handling, and filtering, but does not detail authentication-provider internals.

Security context

As explained in Quarkus in Action

A security context is information describing the authenticated principal and associated security state for a request or interaction.

A security context exposes the authenticated principal and related security state for the current request. A REST endpoint can inspect it without passing user identity through every method explicitly. section 6.2.1 section 6.6

Use the context to connect request authentication with application behavior:

Inject jakarta.ws.rs.core.SecurityContext into a REST resource. section 6.2.1
Call getUserPrincipal() to obtain the current principal, then read its name. section 6.2.1 section 6.6
Handle an empty context explicitly when unauthenticated requests remain allowed. section 6.2.1
Use the principal to associate records with users or filter results to the current user. section 6.2.1

Associate a reservation with its principal

String userId = context.getUserPrincipal() != null ? context.getUserPrincipal().getName() : "anonymous"; reservation.userId = userId; section 6.2.1

How Quarkus in Action covers it

liveBook manning.com

Read Quarkus in Action on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Spring Security in Action, Second EditionA security context is a Spring Security object that holds authentication information associated with the current execution or request.
liveBook manning.com

Kubernetes for DevelopersA Kubernetes security context is a set of Pod or container settings that controls security-related execution properties such as the user identity.
liveBook manning.com

Google Anthos in ActionA Kubernetes security context is a pod or container specification field that controls identity, privilege, and filesystem security settings at runtime.

Compare how 4 books explain security context →

Related concepts

thread localuses · Thread-local data is data whose value or instance is independently associated with each executing thread.
authentication filterconfigured by · An authentication filter is a request-processing component that intercepts authentication requests and delegates them to an authentication mechanism.
privileged containerconfigures · A privileged container is a container granted broad host-level permissions or capabilities that substantially reduce its normal isolation from the host.
SecurityContextHolderused by · SecurityContextHolder is a Spring Security utility that provides access to the security context associated with the current execution.
non-root userconfigures · A non-root user is an operating-system account without the unrestricted administrative privileges of the root or superuser account.
authenticationhas part · Authentication is the process of establishing or verifying the identity of a user, service, device, or other communicating entity.

This explainer was generated by Manning's knowledge graph from the text of Quarkus in Action. The section links point to the parts of the book it draws on.