Articles

Are you looking to support SAML clients or external SAML identity providers in your IdentityServer? If so, this tutorial will help you implement a cross-protocol SSO.

Rsk.Saml v5 includes new features, improvements and breaking changes. Such as support for .NET 6, Duende IdentityServer v6 and HTTP Artifact binding.

SAML implementations typically exchange sensitive user data via the browser. This considerably increases the attack surface of your Single Sign-On (SSO) solution. Luckily, SAML offers an alternative mechanism called HTTP Artifact binding that allows protocol messages to be transported more securely.

SAML works really well for server-side applications, providing single sign-on across your applications. But can you use SAML with modern application types such as SPAs and mobile apps?

When will products be supporting Duende IdentityServer? Will I have to pay for my component to work with Duende IdentityServer? How can I keep up to date with product releases?

SAML support for Duende IdentityServer is now available. Over the past few months, we have been updating our SAML component to work with both IdentityServer4 and Duende IdentityServer. As a result, we have split our component into separate packages to handle SAML identity provider and service provider functionality.

SAML support for IdentityServer4 v4 is now available. Over the past few months, we have been building new features in our SAML IdP & SP component, culminating in 6 minor releases and 2 major releases.

SAML single sign-on (SSO) allows the end-user to securely authenticate across multiple applications by logging in once using one set of credentials. However, authentication is only the first half of the story.

Microsoft released ASP.NET Core 3.0 a few weeks ago, which means breaking changes for everyone! However, you will be pleased to know that there are no breaking changes for the IdentityServer4 commercial components. Our products are now multi-targeting .NET Standard 2.0 and .NET Core 3.0, using a single codebase.

Rock Solid Knowledge is pleased to announce version 2.4 of the IdentityServer4 SAML component. This release includes new features for both SAML Service Providers and Identity Providers, based on user feedback and sponsored development.

When using SAML, we have two methods for starting Single Sign-On (SSO): SP-initiated or IdP-initiated. Both have their use cases, but one is more secure than the other. No points for guessing from the title.

We are pleased to announce the full release of .NET Core support for the IdentityServer4 SAML and WS-Federation components...

Security Assertion Markup Language (SAML) is used to communicate authentication data between two parties. Implementing IdentityServer4 in the world of OpenID Connect? You could call it a "legacy" protocol...

We are pleased to announce the first preview release of the IdentityServer4.Saml built using .NET Standard 2.0...