DNN OAuth Single Sign-On (SSO) module gives the ability to enable OAuth Single Sign-On for your DotNetNuke site.Using Single Sign-On you can use only one password to access your DotNetNuke site and services. Our module is compatible with all the OAuth compliant Identity providers. Here we will go through a step-by-step guide to configure Single Sign-On (SSO) between DNN and PingFederate considering PingFederate as OAuth Provider.
Ping Federate Endpoints and Scope:
Client ID : | Click Here |
Client Secret : | Click Here |
Scope: | openid |
Authorize Endpoint: | https://{your-base-url}/as/authorization.oauth2 |
Access Token Endpoint: | https://{your-base-url}/as/token.oauth2 |
Get User Info Endpoint: | https://{your-base-url}/idp/userinfo.oauth2 |
You can configure the ASP.NET 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.
Application | LINK |
SAML SSO into DotNetNuke (DNN) site | Click here |
SAML SSO into SiteFinity site | Click here |
SAML SSO into Umbraco site | Click here |