ITfoxtec.Identity.Saml2.MvcCore 4.20.1

ITfoxtec.Identity.Saml2.MvcCore

ITfoxtec.Identity.Saml2.MvcCore adds ASP.NET Core MVC integration helpers for ITfoxtec.Identity.Saml2. Use it when an ASP.NET Core application needs SAML 2.0 sign-on, logout, metadata, and binding handling without writing the MVC plumbing yourself.

The package is maintained by FoxIDs. The ITfoxtec name remains in the package and namespaces for compatibility with existing integrations.

What it adds

• ASP.NET Core service registration with AddSaml2.
• ASP.NET Core middleware registration with UseSaml2.
• Request conversion from ASP.NET Core requests to SAML 2.0 requests.
• IActionResult helpers for Redirect, POST, Artifact, SOAP, and metadata responses.
• Cookie authentication integration for SAML 2.0 login and logout flows.

The underlying SAML 2.0 implementation supports message signing, signature validation, encrypted assertions, metadata, Redirect Binding, POST Binding, Artifact Binding, Azure Key Vault certificate scenarios, RSA and ECDSA signing, signature algorithm and XML canonicalization validation allowlists, configurable AES-CBC/AES-GCM assertion encryption, RSA key encryption, XML Encryption 1.1 RSA-OAEP, and interoperability with Microsoft Entra ID (Azure AD), AD FS, Azure AD B2C, Danish NemLog-in3 (MitID), Danish Context Handler (Faelleskommunal Adgangsstyring), and other SAML 2.0 solutions.

Supported frameworks

• .NET 10.0
• .NET 9.0
• .NET 8.0
• .NET 7.0
• .NET 6.0
• .NET Framework 4.6.2 and 4.8

Getting started

dotnet add package ITfoxtec.Identity.Saml2.MvcCore

Start with the ASP.NET Core sample: TestWebAppCore. It shows configuration binding, AddSaml2, UseSaml2, metadata generation, login, assertion consumer service, single logout, and IdP-initiated sign-on.

More information is available on the project page and in the GitHub source.

Direct integration or FoxIDs bridge

Use ITfoxtec.Identity.Saml2.MvcCore when you need to implement SAML 2.0 directly in your ASP.NET Core application.

If your application already supports OpenID Connect or WS-Federation, FoxIDs can be the cleaner integration point. FoxIDs handles the SAML 2.0 connection to the external identity provider or relying party, while the application continues to use the protocol it already supports. This can avoid adding another federation protocol implementation to the application.

Consider FoxIDs when you need:

• A SAML 2.0 to OpenID Connect bridge, or SAML 2.0 to WS-Federation bridge.
• SAML 2.0 integration without changing an application that already supports OpenID Connect or WS-Federation.
• Hosted or self-hosted federation infrastructure across SAML 2.0, OpenID Connect, OAuth 2.0, and WS-Federation.
• A place to operate protocol translation, certificates, metadata, and partner-specific federation configuration outside the application code.
• Architecture guidance or implementation support for SAML 2.0 migrations and complex federation setups.

FoxIDs uses ITfoxtec.Identity.Saml2 for SAML 2.0 protocol handling. The library and FoxIDs are complementary: use the package when SAML 2.0 belongs in your application, and use FoxIDs when SAML 2.0 is better handled as an external identity bridge or federation service.

Support

Use GitHub issues for bugs and feature requests. For implementation questions, use Stack Overflow with the itfoxtec-identity-saml2 tag.

Implementation help, architecture guidance, and custom samples are available from FoxIDs by contacting anders@foxids.com.