SShortSingh.
Back to feed

ASP.NET Core Authentication: Schemes, Cookies, JWT, OAuth and OIDC Explained

0
·18 views

A detailed technical guide published on DEV Community walks developers through the authentication system in ASP.NET Core, covering its scheme-based, pluggable architecture. The guide explains how every authentication mechanism — whether cookie-based or JWT bearer token — ultimately produces a ClaimsPrincipal that populates HttpContext.User. It covers the two most common authentication approaches: cookie authentication for browser applications and JWT bearer tokens for APIs. The article also clarifies the frequently misunderstood distinction between OAuth 2.0, an authorization delegation protocol, and OpenID Connect, an authentication protocol built on top of it. Additional topics include multi-scheme applications, token validation, refresh tokens, and how authentication integrates with ASP.NET Core's middleware and authorization systems.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Hungary releases Communist-era files naming up to 60,000 former agents

Hungary has opened archives from its Communist era, revealing the identities of as many as 60,000 former agents. The documents were made public in a release reported by Euronews on November 4, 2026. The disclosure allows the public to examine records tied to the country's former state security apparatus. The source article provided only limited details beyond the headline and link, so further specifics about the files and their scope remain unconfirmed.

0
ProgrammingHacker News ·

Blog Post Revisits Hackintosh Revival Aided by AI Tools

A blog post at naut.ca, dated November 5, 2026, discusses reviving the Hackintosh concept, which refers to running macOS on non-Apple hardware. The article reportedly credits AI assistance as part of the effort. The item was shared on Hacker News, where it received 3 points and no comments at the time of capture. The source text provided is limited to the link and metadata, so further details of the author's methods and findings cannot be confirmed.

0
ProgrammingDEV Community ·

WordPress 7.0 Adds a Built-In AI Client and Connectors Screen

WordPress 7.0, codenamed Armstrong, was released on 20 May 2026, about six weeks behind its original schedule. The update adds a provider-agnostic AI Client to core, along with a Connectors screen for storing provider credentials and the JavaScript side of the Abilities API. Editor-facing changes include a command palette, a redesigned dashboard, a font management page, improved revisions, and new blocks. Real-time collaborative editing, the release's intended centerpiece, was pulled twelve days before launch because it was not ready, and the cycle returned to beta. Core ships no AI model or vendor key, and the AI features stay inactive until an administrator saves a provider key.

0
ProgrammingDEV Community ·

HotKV tops Redis, Valkey and Dragonfly on most commands in three-node cluster test

A benchmark compared HotKV, Redis, Valkey and Dragonfly deployed as three-node clusters on AWS servers, matching how Redis and Valkey are typically scaled across cores. HotKV posted the highest throughput on eight of nine tested commands, reaching 92.3 million GETs per second versus 57.3 million for Redis, 52.9 million for Valkey and 22.5 million for Dragonfly. Redis and Valkey led on APPEND, and some load generators were near their limits, so the reported figures are lower bounds. The authors argue that a cluster layout is fairer than the earlier single-instance tests, since Redis and Valkey run one thread per process. All tests ran with persistence disabled on 5 million keys with 256-byte values, using median results from two 15-second runs.