Duende IdentityServer vs. PingFederate
Duende IdentityServer and PingFederate can both run on infrastructure you control. Duende IdentityServer is a .NET framework: your identity server is a dedicated ASP.NET Core host, configured and extended in C#. PingFederate is Ping Identity's federation server: a Java application you deploy and operate, configured through an admin console, Admin API or Terraform, and extended with Java plugins. Choose Duende IdentityServer to build identity into your .NET system. Choose PingFederate for a standalone federation server that works with the rest of Ping's suite.
PingFederate is Ping Identity's federation server. It provides single sign-on across OpenID Connect, SAML and WS-Federation, and acts as an OAuth authorization server for APIs. You deploy it yourself, as containers or a .zip, or Ping hosts it for you in a dedicated tenant (PingOne Advanced Services) or in Ping Government Identity Cloud, which holds FedRAMP High and DoD IL5 authorizations. Custom logic is written as Java plugins on the PingFederate SDK, login pages are Velocity HTML templates or a custom app built on the PingFederate Authentication API, and MFA comes through integrations such as PingID, PingOne MFA or Duo.
Duende IdentityServer takes a different approach: identity as code. It is a standards-based identity server for .NET, supporting OpenID Connect and OAuth, plus SAML 2.0 in IdentityServer 8.0 and later (included in Advanced, a paid add-on for Standard). An optional first-party User Management component (also 8.0 and later) handles users, MFA and passkeys. You host it in your own ASP.NET Core identity host, configure clients and resources in C# or a database, and write claim logic, login pages and policies as ordinary code. It runs on supported .NET versions, in the cloud, on-premises or on air-gapped networks. License validation happens locally, with no outbound calls. Other outbound traffic depends on your host, your infrastructure and the integrations you configure, such as external identity providers. You control your host, your data, the user experience and the release cycle.
This comparison was last checked on November 2, 2026. Both products change regularly, so some details may be out of date by the time you read this. Ping details come from Ping's public website and documentation.
How Do Duende IdentityServer and PingFederate Compare?
Each product leads in different areas. The table below compares them capability by capability.
PingFederate leads on WS-Federation as an identity provider, outgoing provisioning, SAML in every deployment, a built-in admin console, and Ping-hosted options.
Duende IdentityServer leads on building and extending identity in C# inside your own .NET app.
Both support OpenID Connect, OAuth, CIBA, PAR, DPoP and Windows desktop sign-in.
| Capability | Duende IdentityServer | PingFederate |
|---|---|---|
| Operating model | Self-hosted in an ASP.NET Core identity host you own | Self-managed software you deploy and operate (containers or .zip), or hosted by Ping (PingOne Advanced Services, Ping Government Identity Cloud) |
| Runtime | .NET and ASP.NET Core | Java (PingFederate 13.1 supports JDK 17, 21 and 25) |
| Configuration | Code and/or Entity Framework configuration stores. Versioned with your app when kept in code | Admin console, Admin API and Terraform provider |
| Login UI | You build the UI (full control) in your identity host, starting from Duende's UI templates if you want | Velocity HTML templates (copied to each node in a cluster), or a custom app built on the Authentication API |
| Extensibility | | Java plugins on the PingFederate SDK |
| User store | Your database (for example ASP.NET Identity) or optional Duende User Management (8.0 and later) | External data stores (LDAP directories and SQL databases), plus registration and profile management (local identity profiles, stored in PingDirectory) |
| Provisioning (SCIM) | Incoming SCIM 2.0 in User Management (IdentityServer 8.1 and later). No outgoing provisioning | Incoming (SCIM 1.1 and 2.0) and outgoing (SCIM 1.1) |
| MFA / passwordless | User Management (passkeys, TOTP, OTP, recovery codes) | PingID, PingOne MFA or other supported integrations such as Duo. Available methods depend on the integration |
| Social / enterprise connections | External providers you configure (static or dynamic) | IdP connections plus supported adapters and integration kits |
| Windows desktop SSO | Windows authentication through ASP.NET Core (IIS, HTTP.sys or the Negotiate handler), configured in code | Kerberos adapter, configured in the admin console |
| SAML 2.0 | SAML 2.0 in IdentityServer 8.0 and later (included in Advanced; add-on for Standard; not available on Lite) | Native |
| WS-Federation | Sign-in through external WS-Federation providers through ASP.NET Core authentication handler. Acting as a WS-Federation identity provider isn't supported. | Native |
| CIBA | Supported (Standard and Advanced) | Supported |
| PAR and DPoP | Supported in every current plan | PAR supported; DPoP from version 11.3 |
| FAPI 2.0 certification | OpenID Certified for FAPI 2.0 Security Profile, Second Implementer's Draft (private_key_jwt + DPoP and OpenID Connect profiles), May 12, 2025 | OpenID Certified for the Australia FAPI 2.0 ConnectID profile (Third Implementer's Draft). PingFederate 11.2, April 2023 |
| Data residency | Wherever you deploy | Wherever you deploy it, or Ping's cloud when Ping hosts it |
| US government | Can be deployed within an environment you authorize and operate, including air-gapped networks | Self-managed inside your boundary, or hosted in Ping Government Identity Cloud (FedRAMP High and DoD IL5) |
How Do PingFederate Concepts Map to Duende IdentityServer?
Many identity concepts carry over from PingFederate, but few map one-to-one. Use this table to plan what you rebuild. Custom logic moves from Java plugins and templates into C#.
| PingFederate | Duende IdentityServer | Notes |
|---|---|---|
| OAuth client | Client | Grant types, scopes and token lifetimes are set per client, in code or a configuration store |
| OAuth scopes | API scopes and identity resources | Model API permissions as API scopes, identity claims as identity resources, and API audiences as API resources |
| Access token manager | Client token settings, API resources and scopes, and claim logic. No single equivalent | A PingFederate access token manager also holds the attribute contract, resource URIs, access control and session validation. Token type (JWT or reference) is one part. Reference tokens are validated through introspection |
| Attribute contract and mapping | | Partial match. IProfileService shapes user claims in C#, and they can be unit tested. Client and resource claims are configured separately |
| IdP adapter (Java SDK) | ASP.NET Core authentication handler, or your own login code | Re-expressed in C#. There is no Java plugin runtime |
| Authentication policy | Login logic in your identity host | Branching becomes ordinary code, reviewed in pull requests |
| IdP connection | External provider (static or dynamic) | Dynamic providers are included in Advanced |
| SP connection (SAML) | SAML service provider | Covers SAML SP connections only. Requires SAML 2.0 support in IdentityServer |
| Data store (LDAP, JDBC) | Your user store | ASP.NET Identity, User Management or a custom store. Connecting an existing LDAP or SQL store may need integration code |
| Velocity templates | Razor pages, or your UI framework | You own the UI and branding |
| Admin console and Admin API | Code and configuration stores | Duende does not ship a built-in admin console. Treat any admin UI as separate work |
| Endpoints and discovery | Standard endpoints under /connect, listed in the discovery document at /.well-known/openid-configuration | Discovery points clients at the new endpoints. You still migrate client registrations, secrets, redirect URIs and scopes, and update APIs to trust the new issuer |
When Is Duende IdentityServer the Right Fit for You?
IdentityServer fits teams that build on .NET and want the token server to be a versioned, testable part of their own system: their code, their database, their UI and their pipeline. When configuration lives in code, a new client or claim ships through the same review and release process as any other change. You choose where it runs and how data is stored. Your team also owns implementation, upgrades and operations.
PingFederate fits organizations already invested in Ping's suite, teams that prefer configuring identity in an admin console over writing code, and buyers who want Ping to host it.
The two also work together. Keep PingFederate as the upstream identity provider for workforce sign-in, and run IdentityServer as the token server for your .NET apps and APIs. Users sign in through PingFederate. Your apps get tokens shaped by your own code.
What About Ping's Hosted Options?
PingOne Advanced Services runs PingFederate in a dedicated tenant that Ping manages. Ping Government Identity Cloud does the same for US public sector buyers. PingOne is a separate product: Ping's multi-tenant cloud service for workforce and customer identity.
If you are weighing a hosted Ping service, the question changes from framework versus server to where identity runs. IdentityServer is software you deploy and run yourself, and your team decides when it changes, within Duende's support policy.
How Do You Migrate to Duende IdentityServer?
Federate first. Stand up an IdentityServer host, add PingFederate as an upstream OpenID Connect provider (or SAML, with IdentityServer 8.0 and the SAML add-on), and move applications one at a time. If PingFederate authenticates users against an LDAP directory you keep, your IdentityServer login code can be implemented to validate credentials against that same directory, so users keep their passwords. MFA enrollments, sessions and user identifiers need their own migration plan. Rebuild adapters, policies and templates as C# and Razor as you go. For the full playbook, read Common Approaches to Migrating to Duende IdentityServer.