liveBook · Manning

Security token

A security token is a credential or assertion presented to a service to convey authenticated identity, authorization, or session information.

How 2 Manning books explain it

Acing the Certified Kubernetes Administrator Exam, Second Edition

An authentication token is a credential value presented by a client or workload to authenticate access to an API or service.

How it is used
Authenticates users, pods, and workload tools before Kubernetes API requests receive authorization decisions.
How deep it goes
Explains mounting, credential-generation mechanisms, exposure risks, and permission verification, but does not detail token cryptography.
Examples
Uses namespace defaults, mounted pod credentials, disabled automounting, role bindings, and kubectl auth can-i verification.
What you can do after
Apply it via kubectl to authenticate workloads, restrict their permissions, disable unnecessary mounts, and test effective access.

Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains security token →

.NET in Action, Second Edition

An authentication token is a credential presented by a client to convey verified identity information to a service.

How it is used
Authenticates HTTP requests and supports subsequent authorization decisions in a web API.
How deep it goes
Defines the credential, explains JWT verification and configuration, but defers the complex history of OpenID Connect.
Examples
Uses JWT bearer configuration, external identity providers, and an authorized CatalogController as concrete examples.
What you can do after
Apply it via ASP.NET Core Identity by configuring JWT bearer authentication and enabling authorization in a web API.

Read how .NET in Action, Second Edition explains security token →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.