OidcForge 4.2.0

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

OidcForge

OpenID Connect and OAuth 2.0 framework for ASP.NET Core on .NET 10 — a maintained fork of IdentityServer4 4.x.

It implements the protocol endpoints (authorize, token, userinfo, introspection, revocation, device authorization, end session, discovery and JWKS), the validators and stores behind them, and the extensibility points of IdentityServer4, so an application written against IdentityServer4 4.x migrates by changing the package reference and recompiling.

dotnet add package OidcForge

Targets net10.0. Namespaces and assembly names are unchanged (IdentityServer4.*).

Quick start

using IdentityServer4.Models;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddIdentityServer(options => options.KeyManagement.Enabled = true)
    .AddInMemoryApiScopes(new[] { new ApiScope("api1", "My API") })
    .AddInMemoryClients(new[]
    {
        new Client
        {
            ClientId = "client",
            AllowedGrantTypes = GrantTypes.ClientCredentials,
            ClientSecrets = { new Secret("secret".Sha256()) },   // use a real secret store in production
            AllowedScopes = { "api1" }
        }
    });

var app = builder.Build();
app.UseIdentityServer();
app.Run();

The token endpoint is /connect/token, discovery is at /.well-known/openid-configuration. For a complete walk-through see the Quickstarts.

Automatic signing key management

Signing keys are created, announced in the discovery document, used for signing, retired and deleted for you (opt-in: options.KeyManagement.Enabled = true). Defaults: a new key is published 14 days before it signs, signs for 90 days, and stays published for another 14 days.

services.AddIdentityServer(options =>
{
    options.KeyManagement.Enabled = true;
    options.KeyManagement.SigningAlgorithms = new[] { "RS256", "ES256" };   // one key per algorithm
    options.KeyManagement.KeyPath = "/var/lib/myapp/keys";                  // default file store
});
  • Keys are protected with ASP.NET Core data protection — in a server farm all instances must share the data protection keys.
  • Store keys in the database instead of files with OidcForge.EntityFramework (AddOperationalStore), or implement ISigningKeyStore and register it with AddSigningKeyStore<T>().
  • Keys added with AddSigningCredential keep signing first; all keys are published.

What to know when you migrate from IdentityServer4 4.x

  • Client redirect URIs are Uri values, matched by exact string comparison; fragments are rejected.
  • Authorization codes are single use; reuse of a consumed one-time refresh token revokes the user's refresh tokens for that client.
  • The client IP (ip claim) comes from the connection. Behind a reverse proxy use UseForwardedHeaders with KnownProxies.
  • Custom IPersistedGrantStore and IAuthorizationCodeStore implementations need the new atomic GetAndRemove… members.

The complete list with a step-by-step guide is in the release notes of the release; the changes of this package are in its own release notes.

Status

Not certified by the OpenID Foundation, not affiliated with Duende Software or the .NET Foundation, no commercial support. Covered by 1,200 automated tests. Report vulnerabilities privately — see SECURITY.MD. Other issues: issue tracker.

License

Apache 2.0. Copyright (c) Brock Allen & Dominick Baier; modifications copyright (c) Yaroslav Tatarenko.

Product Compatible and additional computed target framework versions.
.NET 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 (2)

Showing the top 2 NuGet packages that depend on OidcForge:

Package Downloads
OidcForge.EntityFramework

EntityFramework persistence configuration APIs (maintained fork of IdentityServer4)

OidcForge.AspNetIdentity

ASP.NET Core Identity integration (maintained fork of IdentityServer4)

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.2.0 146 10/2/2026