A lightweight, easy-to-use library for working with JSON Web Tokens (JWT) in .NET applications. Features include token validation, custom claims, signature verification, and audience validation, making it an ideal choice for developers looking to secure their .NET applications efficiently.
$ dotnet add package Abblix.JWTAbblix.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.
System.Text.Json.Nodes and .NET crypto primitives (RSA, ECDsa, AES) directly — no Microsoft.IdentityModel.Tokens dependencyRSA-OAEP-256 (SHA-256), AES-GCM key wrapping (A128GCMKW/A192GCMKW/A256GCMKW), and direct key agreement (dir) per RFC 7518JsonWebKey classes now validate key operations (sign, verify, encrypt, decrypt) before useMicrosoft.IdentityModel.Tokens confirm full compatibility across unsigned JWTs, all signing algorithms, and JWE encryption combinationsJsonObject-based programming model handles numbers, arrays, and nested objects without string conversionsdotnet add package Abblix.JWT
| 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 |
To learn more about the Abblix OIDC Server product, visit our Documentation site and explore the Getting Started Guide.