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 PingFederate considering PingFederate as IdP.

Download And Extract Package

• Download miniOrange ASP.NET SAML 2.0 Module.
• For Setting up the module, extract the asp-net-saml-sso-module-xxx.zip, you will find a DLL file miniorange-saml-sso.dll, a configuration file saml.config and a integration.md file which contain the steps for adding the module into your application.

Steps to configure PingFederate Single Sign-On (SSO) Login into ASP.NET

1. Add module on DNN page

• Add miniorange-saml-sso.dll in the bin folder (where your other DLL files exist) for your application.
• Register miniorangesamlsso module in your application according to the provided steps in the integration.md file.
• Add the provided configuration file saml.config in the root directory for your application.
• After integration open browser and browse the module dashboard with URL below:
https://<your-application-base-url>?ssoaction=config
• If it pops up the registration page or login page, you have successfully added the miniOrange saml sso module for your application.


• Register or Login for configuring the module.

2. Configure PingFederate as Identity Provider

• Login to your PingFederate User Admin dashboard.
• Click on the OAuth Server in the left navigation menu.
• Under Clients, click on Create New.

• Enter the Client ID, Name and Description. Select Client Secret in Client Authentication and click on Generate Secret. Take a note of your Client ID & Client Secret which you will require in Step 3 to configure miniOrange ASP.NET OAuth Client.

• Copy the Redirect/Callback URL from the miniOrange ASP.NET OAuth Client and enter it in Redirect URIs field and click on Add. Select the Authorization Code grant type and click on Save.

• You have successfully completed your Ping Federate App OAuth Server side configurations.



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

3. Configure ASP.NET SAML Module as Service Provider

• After configuring your OAuth Provider, it will provide you with Client ID, Client Secret, Authorize Endpoint, Access Token Endpoint and Get User Info Endpoint. Configure these values under respective fields.
• Fill all the required details and click on Save Configuration.

4: Test Configuration

• Click on the Test Configuration button to test the configuration.

5: Attribute Mapping

• After testing the configuration, Map your application attributes with the Identity Provider (IdP) attributes.
• Note: All the mapped attributes will be stored in the session so that you can access them in your application.

6: Integration Code

• You can also find the Integration code in the Integration Code tab in the module. Just copy-paste that code snippet wherever you want to access the user attributes.
• Note: All the mapped attributes will be stored in the session so that you can access them in your application.

7: Login Settings

• Use the following URL as a link in your application from where you want to perform SSO:
• https://<your-application-base-url>/?ssoaction=login
• For example you can use it as:
• <a href="https://<your-application-base-url>/?ssoaction=login">Login</a>

8: Add following link in your application for Single Sign-On (SSO

• Use the following URL as a link in your application from where you want to perform SLO:
• https://<your-application-base-url>/?ssoaction=logout
• For example you can use it as:
• <a href="https://<your-application-base-url>/?ssoaction=logout">Logout</a>

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: