AurorisNet.IdentityServer 1.0.1

There is a newer version of this package available.
See the version list below for details.
dotnet add package AurorisNet.IdentityServer --version 1.0.1
                    
NuGet\Install-Package AurorisNet.IdentityServer -Version 1.0.1
                    
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="AurorisNet.IdentityServer" Version="1.0.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="AurorisNet.IdentityServer" Version="1.0.1" />
                    
Directory.Packages.props
<PackageReference Include="AurorisNet.IdentityServer" />
                    
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 AurorisNet.IdentityServer --version 1.0.1
                    
#r "nuget: AurorisNet.IdentityServer, 1.0.1"
                    
#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 AurorisNet.IdentityServer@1.0.1
                    
#: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=AurorisNet.IdentityServer&version=1.0.1
                    
Install as a Cake Addin
#tool nuget:?package=AurorisNet.IdentityServer&version=1.0.1
                    
Install as a Cake Tool

AurorisNet.IdentityServer

An embeddable OpenID Connect server for the directory you already run, built on ASP.NET Core 10 and OpenIddict. Host sign-in endpoints beside your own application endpoints and let people use their existing directory accounts.

This project is independent of Duende IdentityServer.

Features

  • Directory sign-in. Authenticate browsers through Negotiate/Kerberos, IIS Windows Authentication, or a trusted Kerberos-aware Apache or Nginx proxy.
  • OpenID Connect. Discovery, JWKS, authorization and token endpoints. Authorization code with PKCE is the recommended flow; implicit and hybrid support is available for older clients.
  • Directory claims. Read a stable subject, profile attributes and direct group memberships from Active Directory, Samba AD or FreeIPA. Map allowlisted groups to roles.
  • Windows and Linux. Host with Kestrel or behind IIS, Apache or Nginx. The Windows directory provider uses Windows-only APIs; the LDAP providers support both platforms.
  • Deployment settings. Configure clients, callback hosts, directory access and persistent signing and encryption keys in your application.

How sign-in works

  1. Your client application redirects the browser to the authorization endpoint.
  2. The host or authenticating proxy verifies the user's directory credentials. A browser that trusts the identity hostname and holds a Kerberos ticket signs in automatically.
  3. IdentityServer reads the user's directory profile and allowed direct groups, then redirects the browser to the application's callback with an authorization code.
  4. The application exchanges the code and PKCE verifier for tokens at the token endpoint.

The service is intended for intranets where browsers can obtain directory Kerberos tickets. Password sign-in, multi-factor authentication and account self-service require a separate solution.

Install

Add the package to a .NET 10 ASP.NET Core web application:

dotnet add package AurorisNet.IdentityServer

The package includes IdentityServer.Core.dll and automatically installs its AurorisNet.ActiveDirectory dependency. Namespaces and extension methods are under IdentityServer. Supply your own application settings; the package does not install demonstration settings or a standalone host.

Embed in your application

Use the shared host builder in Program.cs:

using IdentityServer;

IdentityServerHost.Run<Startup>(args);

Register the server and your controllers in Startup.cs:

using IdentityServer;
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;

public class Startup(IConfiguration configuration)
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddIdentityServer(configuration);
        services.AddControllers();
    }

    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
        app.UseIdentityServer(env);
        app.UseEndpoints(endpoints => endpoints.MapControllers());
    }
}

UseIdentityServer adds routing, CORS, authentication and authorization. Map your endpoints after it. Application routes require sign-in by default; use [AllowAnonymous] for routes intended to be public. The embedding guide describes route authentication, proxy requirements and custom profile providers.

Configure and deploy

Create appsettings.json in your host application using the configuration example and the guide for your environment:

  • Set the public HTTPS issuer, allowed hosts, clients and callback hosts.
  • Choose browser authentication and directory settings. On Linux, configure Kerberos and an LDAP provider for Active Directory, Samba AD or FreeIPA.
  • Set the group-name allowlist if applications need role claims.
  • Persist token keys outside the deployment folder. On Linux, also supply a key-protection password through your deployment's secret configuration.
  • Configure explicit proxy trust when hosting behind Apache or Nginx.

The shared host reads appsettings.json, optional appsettings.Local.json, environment variables and command-line arguments, in that order. It does not load environment-specific JSON files or .NET user secrets. It logs to the console and daily files.

After starting the configured host, check /.well-known/openid-configuration for its discovery document, then follow the sign-in verification guide.

Documentation and support

License

MIT

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 (1)

Showing the top 1 NuGet packages that depend on AurorisNet.IdentityServer:

Package Downloads
AurorisNet.Umbraco.IdentityServer.SSO

Single sign-on for Umbraco 18 backoffice users and members through an OpenID Connect identity server: the site's own embedded IdentityServer with Windows authentication, or an external one. Adds the login buttons and automatic redirect, a password fallback when the server is unreachable, account seeding from configuration, and retirement of deleted accounts that have signed in.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.2.1 47 11/19/2026
1.2.0 52 11/18/2026
1.1.1 108 11/16/2026
1.1.0 75 11/16/2026
1.0.1 106 11/1/2026