Abblix.OIDC.Server.MVC 3.0.0

Prefix Reserved
dotnet add package Abblix.OIDC.Server.MVC --version 3.0.0
                    
NuGet\Install-Package Abblix.OIDC.Server.MVC -Version 3.0.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.OIDC.Server.MVC" Version="3.0.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Abblix.OIDC.Server.MVC" Version="3.0.0" />
                    
Directory.Packages.props
<PackageReference Include="Abblix.OIDC.Server.MVC" />
                    
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.OIDC.Server.MVC --version 3.0.0
                    
#r "nuget: Abblix.OIDC.Server.MVC, 3.0.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.OIDC.Server.MVC@3.0.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.OIDC.Server.MVC&version=3.0.0
                    
Install as a Cake Addin
#tool nuget:?package=Abblix.OIDC.Server.MVC&version=3.0.0
                    
Install as a Cake Tool

Abblix OIDC Server MVC

Abblix.OIDC.Server.MVC integrates the Abblix OIDC Server with ASP.NET Core MVC, providing controller classes, model binding, and routing for the OpenID Connect endpoints. This is the recommended package for controller-based ASP.NET Core applications; hosts without MVC take Abblix.OIDC.Server.MinimalAPI instead.

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

  • The endpoints are mapped with MapOidcControllers(), at the routes OidcRouteOptions sets
  • Every tenant of a multi-tenant server is served through the same controllers

✏️ Improvements

  • The MVC and Minimal API hosts read a request the same way

Key Features

  • Standard MVC Integration: Uses ASP.NET controller classes and model binding on routes the package maps itself - no custom middleware required
  • OIDC Endpoint Controllers: Authorization, token, userinfo, introspection, revocation, device authorization, and more
  • Session Management: Check session iframe and RP-initiated logout with CSP nonce support
  • Front-Channel & Back-Channel Logout: Complete logout notification via both channels
  • Discovery Endpoint: Auto-configured /.well-known/openid-configuration metadata
  • Dynamic Client Registration: REST API for client management per RFC 7591/7592
  • Host-owned interactive pages: login and consent stay in your application - MVC, Razor Pages or anything else - while the package serves the protocol endpoints

Install

dotnet add package Abblix.OIDC.Server.MVC

This package includes Abblix.OIDC.Server, Abblix.OIDC, Abblix.JWT, Abblix.DependencyInjection, and Abblix.Utils as transitive dependencies.

Quick Start

using Abblix.Jwt;
using Abblix.Oidc.Server.Features.Consents;
using Abblix.Oidc.Server.Features.MultiTenancy;
using Abblix.Oidc.Server.Mvc;

var builder = WebApplication.CreateBuilder(args);

// Grants every client everything it asks for, which suits only clients of your own;
// to ask the end user for consent, register your own IUserConsentsProvider instead
builder.Services.AddConsentGrantedForEveryClient();

// The server serves tenants; a host serving one issuer declares one
builder.Services.AddOidcServices(options => options.Tenants.Add(new TenantDefinition
{
    Id = "main",
    // The address the app is served on, read from the "Issuer" setting
    Issuer = new Uri(builder.Configuration["Issuer"]
        ?? throw new InvalidOperationException("Set Issuer to the address the app is served on")),
    LoginUri = new Uri("/Auth/Login", UriKind.Relative),
    SigningKeys = [JsonWebKeyFactory.CreateRsa(PublicKeyUsages.Signature)],
    Clients = [ /* client configurations */ ],
    Scopes = [ /* scope definitions */ ],
}));

var app = builder.Build();

app.UseAuthentication();
app.UseAuthorization();
app.MapOidcControllers();
app.Run();

The issuer comes from configuration, so add it to appsettings.json first, for example "Issuer": "https://localhost:5001".

The library's controllers carry no route of their own, so app.MapControllers() and a conventional route such as {controller}/{action} never reach them. MapOidcControllers() maps each enabled endpoint at the path OidcRouteOptions gives it, and a disabled endpoint is not mapped at all, so it answers 404. The call returns a convention builder for the endpoints it mapped, so cross-cutting conventions apply to all of them at once and to none of the host's routes, and an optional prefix mounts every endpoint under a sub-path:

using Abblix.Oidc.Server.AspNetCore;
using Abblix.Oidc.Server.Mvc;

builder.Services.Configure<OidcRouteOptions>(routes => routes.Token = "/oauth2/token");

app.MapOidcControllers(prefix: "/auth") // e.g. /auth/oauth2/token, /auth/.well-known/jwks
    .RequireRateLimiting("oidc");

The mapped endpoints appear in your API description, and so in any OpenAPI document built from it, such as Swashbuckle's or Microsoft.AspNetCore.OpenApi's. Call .ExcludeFromDescription() on what MapOidcControllers() returns to leave them out, or .WithGroupName("oidc") and declare an "oidc" document to give them one of their own.

A configuration section keyed as in version 2.4 (base, token, introspect, jwks and the rest, values such as ~/oauth2 or [route:base]/issue) still sets the paths, through services.ConfigureRoutes(configuration.GetSection("Routes")). The same call resolves tokens such as [route:ApiPrefix?v1] in your own controllers' route templates; a controller carrying one needs the call even with an empty section, since nothing else resolves its fallback.

Endpoint URLs

A host that needs an OIDC endpoint's URL - to point an external identity provider's callback back at the authorization endpoint, say - asks IOidcEndpointResolver:

var authorizationUrl = resolver.Resolve(OidcEndpoints.Authorize);

Both transport adapters register it, so this code is written once and survives a change of adapter; an endpoint the host does not serve resolves to null.

Implemented Standards

This package provides ASP.NET Core MVC endpoints for the full suite of standards implemented by the Abblix OIDC Server core, including:

  • OAuth 2.0: Authorization Code, Implicit, Client Credentials, Device Authorization (RFC 6749, RFC 8628), PKCE (RFC 7636), PAR (RFC 9126), JAR (RFC 9101), DPoP (RFC 9449)
  • OpenID Connect: Core 1.0, Discovery, Dynamic Client Registration, Session Management, RP-Initiated/Front-Channel/Back-Channel Logout, CIBA
  • JWT: JWS (RFC 7515), JWE (RFC 7516), JWT Access Tokens (RFC 9068)

For the complete standards list, see the Abblix.OIDC.Server package documentation.

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.OIDC.Server Core OpenID Connect server implementation
Abblix.OIDC.Server.MVC ASP.NET Core MVC integration (this package)
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.SharedSignals OpenID Shared Signals Framework 1.0 transmitter and receiver

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.MVC is licensed under the Abblix license agreement. See LICENSE.md.

Contacts

Product Compatible and additional computed target framework versions.
.NET net11.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
3.0.0 215 11/18/2026
2.4.0 248 9/5/2026
2.3.0 245 6/9/2026
2.2.0 392 2/18/2026
2.1.0 532 12/8/2025
2.0.1 694 12/1/2025
2.0.0 261 11/26/2025
1.6.0 325 8/14/2025
1.5.0 272 6/25/2025
1.4.0 319 4/9/2025
1.3.1 294 12/3/2024
1.3.0.1 229 11/28/2024
1.3.0 241 11/13/2024
1.2.0.1 260 10/16/2024
1.2.0 244 10/11/2024
1.1.0 365 7/9/2024
1.0.100 268 5/3/2024
Loading failed

Every protocol endpoint as an MVC controller - authorization, token, introspection, revocation, discovery, keys, UserInfo, pushed authorization, device authorization, CIBA, dynamic client registration and management, end-session and check-session - with routes you can move, JARM and signed introspection responses, and a default cross-origin policy for the OIDC endpoints so a browser client works without extra configuration. Endpoints beyond the core set are opt-in. Referencing both transport adapters is refused at startup with a message naming the package to drop. New in 3.0: the endpoints are mapped with MapOidcControllers, at the routes OidcRouteOptions sets, and serve every tenant of a multi-tenant server. Full details: https://github.com/Abblix/Oidc.Server/releases/tag/v3.0