Fdyay.IdentityServer
An OAuth 2.0 / OpenID Connect and SAML 2.0 authorization server for .NET 10, built to be configured the way
Duende IdentityServer 8.0.1 is: the same builder calls,
stores and services, under namespaces that mirror Duende's, so a host moving across mostly swaps the root of its
using lines.
Packages
| Package | What it is |
|---|---|
Fdyay.IdentityServer.Core |
The protocol engine: models, stores, validation, token creation, events, key management. No ASP.NET Core dependency. |
Fdyay.IdentityServer.AspNetCore |
The endpoints, hosting, cookie authentication, interaction services, local API authentication and DPoP for an ASP.NET Core host. |
Fdyay.IdentityServer.UI |
The interactive pages (sign-in, consent, sign-out, device, CIBA, grants) as a Razor class library. |
Fdyay.IdentityServer.Saml |
A native SAML 2.0 identity provider: SSO, single logout and metadata. |
Fdyay.IdentityServer.Federation |
External identity providers: OpenID Connect, OAuth 2.0 and SAML 2.0, registered statically or stored as rows. |
Fdyay.IdentityServer.AspNetIdentity |
ASP.NET Core Identity's users and cookie as this server's. |
Fdyay.IdentityServer.Dapper |
Persistence for clients, resources, grants, keys and sessions over SQLite or SQL Server. |
Fdyay.AccessTokenManagement |
Client side: client credentials tokens obtained, cached, renewed and attached to an HttpClient. |
Fdyay.AccessTokenManagement.OpenIdConnect |
Client side: a signed-in user's access token, refreshed from the session's refresh token. |
Where to look
- Guides: from a minimal server to every feature: server and configuration, the protocols (DPoP, CIBA, token exchange, resource indicators and more), interaction and extensibility — each with code included from a sample project the build compiles and a test boots, so no snippet can fall behind the API.
- Migrating from Duende: what a Duende IdentityServer 8 host changes, and where this server differs on purpose.
- Protocol flows: every request and response of each OAuth 2.0, OpenID Connect and SAML flow, with a sequence diagram, recorded from the integration tests against the demo host on every CI run.
- Configuration reference: every options type, each setting's configuration key, type, default and description, generated from the compiled code and checked against it on every build.
- API reference: every public type and member of the nine packages, generated from the source on each release.
- Duende parity: what Duende IdentityServer 8.0.1 has, and where each piece is here.
These pages are generated from the code in the same CI run that publishes the packages, so they describe the release they ship with.