DotNetNuke SAML SP Single Sign-On (SSO) module gives the ability to enable SAML Single Sign-On for your DotNetNuke applications. Using Single Sign-On you can use only one password to access your DotNetNuke 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 DotNetNuke and Salesforce considering Salesforce 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|
You have successfully configured Salesforce as SAML IdP (Identity Provider) for achieving Salesforce SSO login into your DotNetNuke (DNN) Site.
There are two ways detailed below with which you can configure your SAML identity provider metadata in the module.
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, Okta, OneLogin, Keycloak, Google, AWS Cognito, OpenAM, Oracle, PingFederate, PingOne, RSA SecureID, Shibboleth-2, Shibboleth-3, SimpleSAML, WSO2 or even with your own custom identity provider.
Not able to find your identity provider? Mail us on firstname.lastname@example.org and we'll help you set up SSO with your IDP and for quick guidance (via email/meeting) on your requirement and our team will help you to select the best suitable solution/plan as per your requirement.
Need Help? We are right here!