Abblix.JWT 2.3.0

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Abblix.JWT --version 2.3.0
                    
NuGet\Install-Package Abblix.JWT -Version 2.3.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Abblix.JWT" Version="2.3.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Abblix.JWT" Version="2.3.0" />
                    
Directory.Packages.props
<PackageReference Include="Abblix.JWT" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Abblix.JWT --version 2.3.0
                    
#r "nuget: Abblix.JWT, 2.3.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Abblix.JWT@2.3.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Abblix.JWT&version=2.3.0
                    
Install as a Cake Addin
#tool nuget:?package=Abblix.JWT&version=2.3.0
                    
Install as a Cake Tool

Abblix JWT

Abblix.JWT provides complete JWT signing, encryption, validation, and management built entirely on .NET cryptographic primitives and System.Text.Json.Nodes. It implements RFC 7515 (JWS), RFC 7516 (JWE), and RFC 7518 (JWA) with a JWT-optimized architecture that eliminates the Microsoft.IdentityModel.Tokens dependency.

What's New in Version 2.3

  • JOSE critical-header processing (RFC 7515 §4.1.11): an extension point binds each critical parameter name to its handling logic; an unhandled critical parameter is rejected
  • Algorithm-pinned verification keys (RFC 7517 §4.4): a key that declares an algorithm is filtered out for any other, closing within-family algorithm confusion
  • Enforced HMAC key length (RFC 7518 §3.2): an HMAC key shorter than its hash output is rejected
  • Typed JWS header accessors (RFC 7515 §4.1.2 to §4.1.8): strongly-typed access to the key-locator and key-material header parameters
  • Granular key-resolution diagnostics: an issuer with no signing keys is distinguished from one whose keys matched neither the key identifier nor the algorithm

Key Features

  • Signing Algorithms: RSA (RS256/RS384/RS512, PS256/PS384/PS512), ECDSA (ES256/ES384/ES512), HMAC (HS256/HS384/HS512)
  • Encryption Algorithms: RSA-OAEP, RSA-OAEP-256, AES-GCM key wrapping (A128GCMKW/A192GCMKW/A256GCMKW), direct key agreement (dir)
  • Content Encryption: A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • Native JSON Types: JsonObject-based programming model handles numbers, arrays, and nested objects without string conversions
  • Exception-Free Validation: Try pattern throughout the validation pipeline for better performance
  • JWK Management: Full JSON Web Key lifecycle with operation capability checks

Implemented Standards

Installation

dotnet add package Abblix.JWT

Part of the Abblix OIDC Server Ecosystem

Package Description
Abblix.Utils Utility library with crypto, URI, and JSON helpers
Abblix.DependencyInjection Advanced .NET DI extensions with aliasing, composites, and decorators
Abblix.JWT JWT signing, encryption, and validation (this package)
Abblix.OIDC.Server Core OpenID Connect server implementation
Abblix.OIDC.Server.MVC ASP.NET MVC integration for OIDC server

Getting Started

To learn more about the Abblix OIDC Server product, visit our Documentation site and explore the Getting Started Guide.

Contacts

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (6)

Showing the top 5 NuGet packages that depend on Abblix.JWT:

Package Downloads
Abblix.OIDC.Server

OpenID Connect and OAuth 2.0 server for ASP.NET Core, certified by the OpenID Foundation. Add a complete identity provider and authorization server to your own .NET application: every OIDC flow, PKCE, PAR, DPoP, JARM, CIBA, device flow, token exchange and FAPI 2.0. Runs on .NET 8, 9 and 10.

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.SecurityEvents

Security Event Tokens (RFC 8417) for .NET with Subject Identifiers (RFC 9493), push (RFC 8935) and poll (RFC 8936) delivery, and OpenID Back-Channel Logout. Build, sign, deliver and validate security events between identity providers and relying parties.

Abblix.JWT.Azure

Azure Key Vault integration for Abblix JWT and Abblix OIDC Server: sign tokens and unwrap keys with private keys that never leave the vault. Keep your OpenID Connect signing keys in Azure.

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.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.4.0 246 9/5/2026
2.3.0 230 6/9/2026
2.2.0 395 2/18/2026
2.1.0 596 12/8/2025
2.0.1 691 12/1/2025
2.0.0 267 11/26/2025
1.6.0 360 8/14/2025
1.5.0 324 6/25/2025
1.4.0 355 4/9/2025
1.3.1 317 12/3/2024
1.3.0.1 292 11/28/2024
1.3.0 292 11/13/2024
1.2.0.1 278 10/16/2024
1.2.0 272 10/11/2024
1.1.0 394 7/9/2024
1.0.100 322 5/3/2024
Loading failed

JWE-encrypted token handling, JOSE critical-header processing (RFC 7515), JWS verification key pinned to its declared algorithm (RFC 7517), enforced HMAC key length (RFC 7518), typed accessors for JWS header parameters, and granular key-resolution diagnostics. Full details: https://github.com/Abblix/Oidc.Server/releases/tag/v2.3