SAML2P Downloads

Breaking change in storing scope-related claims. The properties key/value pairs on a scope used the key "claims" to hold an array of acceptable claims for the scope. To prevent any possible name clashes the key has been renamed to "urn:com:rocksolidknowledge:scope:property:claims"

SAML tables can not exist outside the default schema

samlBuilder.AddSamlConfigurationStore(options =>
{
 options.DefaultSchema = "custom_schema",
 options.ConfigureDbContext = //..,
} 

• The SAML response containing the "NotBefore" and "NotOnOrAfter" using the wrong time, resulting in a Microsoft.IdentityModel.Tokens.SecurityTokenExpiredException : IDX10223: Lifetime validation failed. The token is expired. ValidTo (UTC): '16.02.2024 11:32:02', Current time (UTC): '16.02.2024 12:30:02'.

• Support for .Net 8.0
• Duende IdentityServer version 7.0 ( not compatible with any version below, use RSK.SAML 8.x.x )
• Support for OpenIddict version 5.1 
• We have added the ability to specify which assertion consumer services endpoint to use when generating IdentityProvider Initiated single sign-on responses.

Note the Saml+OpenIddict template uses a beta NuGet package when using MySql. We will release an updated template once a released package becomes available.

• Now supports OpenIddict Version 5

• Fixed issue with OpenIddict Session Service when logging into multiple service providers

• Support for the OpenIddict identity framework.
  • IDP
  • SP
• Allow overriding the way metadata is parsed to an XElement by overriding the ParseMetadataDocument method of the SamlMetadataParser . The default implementation removes the namespaces from the provided XML.
• Configuring SAML options using a fluent builder syntax is now easier. The SamlBuilder class now has a configure method for each concrete options class. This class returns a builder object, allowing options to be configured fluently.

• Dropped support for .Net core 3.1. 

Why is there no  Rsk.Saml version 7

For many years, we have versioned the various SAML-dependent packages independently. This process was getting too complex. So, as of version 8, all RSK.SAML package's major and minor numbers will be versioned in lockstep. Patch releases for each Nuget package will be independent. Since we had dependent packages with a major version 7, we have started this new approach from version 8.