ASP.NET SAML SP Single Sign-On (SSO) module gives the ability to enable SAML Single Sign-On for your ASP.NET applications. Using Single Sign-On you can use only one password to access your ASP.NET application and services. Our module is compatible with all the SAML compliant Identity providers. Here we will go through a step-by-step guide to configure Single Sign-On (SSO) between ASP.NET and Keycloak considering Keycloak as IdP.
Follow the steps below to configure Keycloak as IdP
|Client ID||The SP-EntityID / Issuer from the plugin's Service Provider Metadata tab|
|Name||Provide a name for this client|
|Description||Provide a description|
|Name ID Format|
|Root URL||Leave empty or Base URL of Service Provider|
|Valid Redirect URIs||The ACS (Assertion Consumer Service) URL from the plugin's Service Provider Metadata tab|
|Assertion Consumer Service POST Binding URL||The ACS (Assertion Consumer Service) URL from the plugin's Service Provider Metadata tab|
|Logout Service Redirect Binding URL (Optional)||The Single Logout URL from the plugin's Service Provider Metadata tab|
Download setup file
User Attribute Mapping is mandatory for enabling users to successfully login into ASP.NET application. We will be setting up user profile attributes for ASP.NET applications using below settings.
You can configure the DotNetNuke SAML 2.0 Single Sign-On (SSO) module with any Identity Provider such as ADFS, Azure AD, Bitium, centrify, G Suite, JBoss Keycloak, Okta, OneLogin, Salesforce, AWS Cognito, OpenAM, Oracle, PingFederate, PingOne, RSA SecureID, Shibboleth-2, Shibboleth-3, SimpleSAML, WSO2 or even with your own custom identity provider.
If you are looking to Single Sign-On into your sites with any SAML compliant Identity Provider then we have a separate solution for that. We do provide SSO solutions for the following:
|SAML SSO into DotNetNuke (DNN) site||Click here|
|SAML SSO into SiteFinity site||Click here|
|SAML SSO into Umbraco site||Click here|
Need Help? We are right here!