Abblix.OIDC.Server
3.0.0
Prefix Reserved
dotnet add package Abblix.OIDC.Server --version 3.0.0
NuGet\Install-Package Abblix.OIDC.Server -Version 3.0.0
<PackageReference Include="Abblix.OIDC.Server" Version="3.0.0" />
<PackageVersion Include="Abblix.OIDC.Server" Version="3.0.0" />
<PackageReference Include="Abblix.OIDC.Server" />
paket add Abblix.OIDC.Server --version 3.0.0
#r "nuget: Abblix.OIDC.Server, 3.0.0"
#:package Abblix.OIDC.Server@3.0.0
#addin nuget:?package=Abblix.OIDC.Server&version=3.0.0
#tool nuget:?package=Abblix.OIDC.Server&version=3.0.0
Abblix OIDC Server
Abblix OIDC Server is a .NET library implementing the server side of OpenID Connect and OAuth 2.0: a certified provider you embed in your own ASP.NET Core application instead of running a separate identity product. It is certified by the OpenID Foundation across all login and logout profiles, builds on the standard .NET DI container, and uses its own JWT implementation built on .NET cryptographic primitives.
What's New in Version 3.0
Version 3.0 changes how a host registers and configures the server. Read Upgrading to 3.0 before moving a 2.x deployment.
🚀 Features
- Multi-tenancy: one server serves several issuers, each a tenant with its own clients, scopes, resources, keys and pages, declared in the settings or kept in a store of the host's own and changed while the server runs
- Every JWT validation states the token types it accepts (RFC 8725)
- Tracing and metrics for the protocol endpoints
- A default scope per client, the resources each client may get an access token for, and one resource per access token
- Per-client budgets on introspection and revocation
- A host step before anything is issued
- Revoking one user's tokens at one client
✏️ Improvements
- Revocation reaches every token of a grant
- A refresh token reuse policy
- Three limits on guessing a user code
- Each logout channel is the deployment's own choice, and a logout confirmation is a value the server issues
- A client authentication JWT names the issuer as its only audience (RFC 10070)
- Any port on a loopback redirect address
Implemented Standards
Abblix OIDC Server implements the following standards for authorization and security:
OAuth 2.0
- The OAuth 2.0 Authorization Framework: RFC 6749
- Bearer Token Usage: RFC 6750, HTTP Authentication: RFC 9110, Section 11
- Token Revocation: RFC 7009
- Token Introspection: RFC 7662
- Proof Key for Code Exchange (PKCE): RFC 7636
- Device Authorization Grant: RFC 8628
- Dynamic Client Registration: RFC 7591 and RFC 7592
- Mutual-TLS Client Authentication: RFC 8705
- Demonstrating Proof of Possession (DPoP): RFC 9449
- Resource Indicators: RFC 8707
- JWT Access Tokens: RFC 9068
- JWT-Secured Authorization Request (JAR): RFC 9101
- Pushed Authorization Requests (PAR): RFC 9126
- Authorization Server Issuer Identification: RFC 9207
- Multiple Response Types: Specification
- Form Post Response Mode: Specification
JSON Web Token (JWT)
- JWS: RFC 7515, JWE: RFC 7516, JWK: RFC 7517, JWA: RFC 7518, JWT: RFC 7519
- JWT Client Authentication: RFC 7523
- Authentication Method Reference Values: RFC 8176
OpenID Connect
- Core 1.0: Specification
- Discovery 1.0 / Authorization Server Metadata: Specification, RFC 8414
- Dynamic Client Registration 1.0: Specification
- Session Management 1.0: Specification
- RP-Initiated Logout 1.0: Specification
- Front-Channel Logout 1.0: Specification
- Back-Channel Logout 1.0: Specification
- Client-Initiated Backchannel Authentication (CIBA): Specification
- Pairwise Pseudonymous Identifiers (PPID): OpenID Connect Core Section 8
Install
dotnet add package Abblix.OIDC.Server
Note: Most applications should use Abblix.OIDC.Server.MVC or Abblix.OIDC.Server.MinimalAPI, which include this package plus the ASP.NET Core endpoint wiring.
Related Packages
| Package | Description |
|---|---|
| Abblix.Utils | Utility library with crypto, URI, and JSON helpers |
| Abblix.DependencyInjection | .NET DI extensions with aliasing, composites, and decorators |
| Abblix.JWT | JWT signing, encryption, and validation using .NET crypto primitives |
| Abblix.JWT.Vault | Signing and decryption keys held in HashiCorp Vault / OpenBao Transit |
| Abblix.JWT.Azure | Signing and decryption keys held in Azure Key Vault |
| Abblix.OIDC | The OAuth 2.0 and OpenID Connect vocabulary the server shares with its client |
| Abblix.OIDC.Server | Core OpenID Connect server implementation (this package) |
| Abblix.OIDC.Server.MVC | ASP.NET Core MVC integration |
| Abblix.OIDC.Server.MinimalAPI | ASP.NET Core Minimal API integration |
| Abblix.SecurityEvents | Security Event Tokens (RFC 8417) and Subject Identifiers (RFC 9493): building, validation, and the delivery data types |
| Abblix.SecurityEvents.CAEP | The CAEP 1.0 event dictionary: session and access lifecycle |
| Abblix.SecurityEvents.RISC | The RISC 1.0 event dictionary: account risk incidents |
| Abblix.SharedSignals | OpenID Shared Signals Framework 1.0 transmitter and receiver |
| Abblix.SharedSignals.MinimalAPI | SSF endpoints as ASP.NET Core Minimal API route handlers |
| Abblix.SharedSignals.Redis | Redis-native event outbox for multi-replica transmitters |
| Abblix.OIDC.Server.SharedSignals | A Shared Signals transmitter per tenant |
Getting Started
To learn more about the Abblix OIDC Server product, visit our Documentation site and explore the Getting Started Guide.
License
Abblix.OIDC.Server is licensed under the Abblix license agreement. See LICENSE.md.
Contacts
- General inquiries: info@abblix.com
- Support and security reports: support@abblix.com
- Website: Abblix OIDC Server
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net11.0 is compatible. |
-
net11.0
- Abblix.DependencyInjection (>= 3.0.0)
- Abblix.JWT (>= 3.0.0)
- Abblix.OIDC (>= 3.0.0)
- Abblix.SecurityEvents (>= 3.0.0)
- Google.Protobuf (>= 3.36.2)
- Microsoft.Extensions.Caching.Memory (>= 11.0.0)
- Microsoft.Extensions.Configuration (>= 11.0.0)
- Microsoft.Extensions.Configuration.Binder (>= 11.0.0)
- Microsoft.Extensions.DependencyInjection (>= 11.0.0)
- Microsoft.Extensions.Http (>= 11.0.0)
- Microsoft.Extensions.Logging (>= 11.0.0)
- System.Threading.RateLimiting (>= 11.0.0)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on Abblix.OIDC.Server:
| Package | Downloads |
|---|---|
|
Abblix.OIDC.Server.MVC
ASP.NET Core MVC integration for Abblix OIDC Server, the certified OpenID Connect and OAuth 2.0 provider. Controllers, model binding and routing for every protocol endpoint: add it to a controller-based application and get a complete identity provider. |
|
|
Abblix.OIDC.Server.MinimalAPI
ASP.NET Core Minimal API integration for Abblix OIDC Server, the certified OpenID Connect and OAuth 2.0 provider. Every protocol endpoint as a route handler with no MVC dependency: the lightest way to host an identity provider in .NET. |
|
|
Abblix.OIDC.Server.SharedSignals
Runs an Abblix Shared Signals transmitter on a multi-tenant Abblix OIDC Server: each tenant's streams, queued events, delivery claims, issuer and signing keys are its own. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 3.0.0 | 203 | 11/18/2026 |
| 2.4.0 | 270 | 9/5/2026 |
| 2.3.0 | 295 | 6/9/2026 |
| 2.2.0 | 440 | 2/18/2026 |
| 2.1.0 | 536 | 12/8/2025 |
| 2.0.1 | 713 | 12/1/2025 |
| 2.0.0 | 299 | 11/26/2025 |
| 1.6.0 | 367 | 8/14/2025 |
| 1.5.0 | 312 | 6/25/2025 |
| 1.4.0 | 361 | 4/9/2025 |
| 1.3.1 | 337 | 12/3/2024 |
| 1.3.0.1 | 279 | 11/28/2024 |
| 1.3.0 | 278 | 11/13/2024 |
| 1.2.0.1 | 288 | 10/16/2024 |
| 1.2.0 | 282 | 10/11/2024 |
| 1.1.0 | 409 | 7/9/2024 |
| 1.0.100 | 298 | 5/3/2024 |
Run a certified OpenID Provider inside your own ASP.NET Core application instead of operating a separate identity product. Abblix OIDC Server is a library: it builds on the standard .NET dependency injection container, stores nothing you do not choose to store, and passes the OpenID Foundation conformance suite in every login and logout profile. What you get: authorization code with PKCE, hybrid and implicit flows, client credentials, device authorization, CIBA, token exchange (RFC 8693) and Rich Authorization Requests (RFC 9396); pushed authorization requests, signed and encrypted request objects, JARM responses and sender-constrained tokens through DPoP or mutual TLS; dynamic client registration and management, discovery and Authorization Server Metadata (RFC 8414), token introspection and revocation, front-channel and back-channel logout, session management. New in 3.0: multi-tenancy, with tenants declared in the settings or kept in a store of the host's own and changed while the server runs; every JWT validation states the token types it accepts (RFC 8725); a client authentication JWT names the issuer as its only audience (RFC 10070); tracing and metrics; per-client budgets on introspection and revocation; a default scope per client and the resources each client may get an access token for; a refresh token reuse policy; and a host step before anything is issued. It runs on .NET 11. Host it through the MVC or the Minimal API integration package. Full details: https://github.com/Abblix/Oidc.Server/releases/tag/v3.0