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 Salesforce Community considering Salesforce Community as IdP.
|Connected App Name||Provide a name for Connected App|
|API Name||Provide a API name|
|Contact Email||Provide a Contact Email|
|Entity ID||SP-EntityID / Issuer from Service Provider Metadata tab of the plugin|
|ACS URL||ACS (AssertionConsumerService) URL from Service Provider Metadata tab of the plugin|
|Name ID Format||urn:oasis:names:tc:SAML:2.0:nameid-format:unspecified|
There are two ways detailed below with which you can configure your SAML identity provider metadata in the module.
Note: If you need any assistance with adding the integration code in your application please reach out to us at firstname.lastname@example.org
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 Nopcommerce site||Click here|
|SAML SSO into Umbraco site||Click here|
|SAML SSO into SiteFinity site||Click here|
Need Help? We are right here!