Overview

Organizations using DNN (DotNetNuke) often serve diverse user groups such as employees, customers, vendors, clients, and regional partners. These users typically authenticate through different Identity Providers (IDPs) like Azure AD, Okta, ADFS, PingFederate, Google Workspace, or custom SAML/OAuth providers.

The need for a centralized multi-IDP layer becomes essential to streamline authentication, enhance security, and support varied identity sources within one DNN portal.

Prerequisites

The organization:

• Runs one or more DNN portals used by multiple internal and external user groups.
• Requires authentication through different IDPs based on User groups.
• Wants to avoid managing separate modules or custom scripts for each IDP.

The Challenge

Business Challenges

• Fragmented login experience for internal and external users.
• Difficulty onboarding users from different organizations or regions.
• Higher support tickets due to incorrect or confusing login paths.
• Poor scalability when adding new partners/IDPs.
• Inconsistent access experience across user groups.

Technical Challenges

• No native support for dynamic IDP routing.
• Manual management of multiple IDP integrations.
• Difficulty enforcing uniform security policies.
• Inconsistent user provisioning and role mapping.
• Complex access control when identity sources differ.

Our Solution

miniOrange delivers Multi-IDP support for DNN, allowing organizations to integrate multiple Identity Providers within a single portal with centralized control, seamless routing, and consistent access policies.

1. Centralized Multi-IDP Management

• Configure all IDPs from a single console.
• Add new IDPs without modifying the DNN portal.
• Manage metadata, endpoints, certificates, and mappings centrally.

2. Consistent Access Control

Regardless of which IDP authenticates the user:

• Roles and claims are mapped centrally.
• Security policies apply uniformly.
• Administrators maintain full control over permissions.

3. Scalable Identity Architecture

• Quickly onboard new partner organizations or subsidiaries.
• No custom development required.
• Suitable for growing and distributed enterprises.

User Journey: How Multi-IDP SSO Works in a Single DNN Portal

Meet Sarah, an internal employee and a regular user of the DNN portal. But Sarah is not alone.

The same DNN portal is accessed by three different user groups, each using a different Identity Provider (IDP):

• Employees → Azure AD
• Vendors → Okta
• Partners → Google Workspace

miniOrange Multi-IDP Support ensures all these users seamlessly authenticate into the same DNN portal, each through their own IDP.

Below is Sarah’s authentication journey along with others like her.

1. Employee Login (Azure AD)

She visits the DNN portal and clicks “Login with Azure AD”.

Authentication Flow:

1. The DNN portal redirects her request to Azure AD.
2. She enters her Microsoft credentials and completes MFA.
3. Azure AD sends a secure SSO response to miniOrange.
4. The plugin validates the response and logs Sarah into the DNN portal.
5. Her roles (e.g., Employee, HR_Access) are assigned based on Azure AD claims.

Outcome:

Sarah enters the portal with content meant only for employees.

2. Vendor Login (Okta)

An external supplier, John, also accesses the same DNN portal.
He selects “Login with Vendor (Okta)”.

Authentication Flow:

1. John is redirected to the Okta IDP login.
2. He completes authentication using his company’s Okta account.
3. Okta returns an SSO response to the DNN portal.
4. The plugin verifies it and logs John into the portal.
5. John is mapped to vendor roles such as Vendor_ReadOnly or Supplier_Manager.

Outcome:

John sees only vendor-specific dashboards, purchase orders, and invoices.

3. Partner Login (Google Workspace)

A regional partner, Alicia, accesses the same DNN portal.
She clicks “Login with Google Workspace”.

Authentication Flow:

1. The portal redirects her to Google Workspace.
2. Alicia signs in with her Google account.
3. Google sends a SAML or OAuth response back to the portal.
4. The plugin validates it and logs her into the DNN system.
5. Her access is mapped to partner-specific roles.

Outcome:

Alicia sees only partner content (documents, project updates, etc.).

Result

After implementing multi-IDP support in DNN, organizations achieve:

• Simplified login process across diverse user groups.
• Drastically reduced confusion and support tickets.
• Faster integration of new partners or subsidiaries.
• Uniform role and access enforcement regardless of IDP.
• Centralized governance across all identity providers.
• A scalable, future-proof authentication architecture.

Additional Resources

1. DNN SSO and SCIM User Provisioning
2. DNN SSO and Two-factor Authentication
3. DNN Multi Portal
4. DNN SAML SSO
5. DNN Two Factor Authentication

We'll Reach Out to You at the Earliest

Enter your email Write your Query Submit

 Thank you for your response. We will get back to you soon.

Something went wrong. Please submit your query again