Search Results :

×

Centralized SSO for Enterprise Apps using Magento Credentials

Organizations running Adobe Commerce (Magento) often require seamless access to external enterprise applications such as ASP.NET-based service platforms. Requiring users to log in again after authenticating in Magento creates friction across systems. This is addressed by configuring Magento as a SAML Identity Provider (IdP) using the miniOrange SAML IdP extension. Once users authenticate in Magento, they can securely access the ASP.NET Service Provider (SP) without re-authentication. Magento sends a signed SAML assertion containing verified identity attributes, enabling secure and centralized authentication across platforms.
Magento SAML IDP- Identity Provider to ASP.net

Rev up Security with Magento Identity Provider

Magento as SAML Identity Provider (IdP)
Automatic SSO into ASP.NET Application
Secure Identity Assertion (No Credential Sharing)
Role-Based Access & Organization-Level Authorization

Magento as SAML Identity Provider (IdP)


Magento is configured as the governing identity authority using the miniOrange SAML IdP extension. All authentication originates from Magento, ensuring centralized credential management and identity control.

Automatic SSO into ASP.NET Application


Once authenticated in Magento, users are automatically logged into the ASP.NET application via a secure SAML assertion. No additional login prompts appear, ensuring a seamless cross-platform experience.

Secure Identity Assertion (No Credential Sharing)


Magento issues a signed SAML assertion containing verified identity attributes. User credentials are never shared with the ASP.NET application. The Service Provider validates issuer authenticity, audience, and assertion expiry before establishing a session.

Role-Based Access & Organization-Level Authorization


The ASP.NET application uses incoming SAML attributes to identify the authenticated user, apply role-based access controls, and enforce company-level as well as organization-based authorization policies. This ensures users are granted appropriate permissions based on their Magento profile and company association.

Why choose Magento-based Centralized SSO?

Magento Identity Provider(IDP) - Centralized Identity Management

Centralized Identity Management

Magento acts as the single source of truth for authentication and identity attributes across systems.

Magento Identity Provider(IDP) - Improved Security Posture

Improved Security Posture

Credentials remain within Magento. The ASP.NET application trusts signed SAML assertions instead of handling passwords directly.

Magento Identity Provider(IDP) - Reduced Login Friction

Reduced Login Friction

Users authenticate once in Magento and gain immediate access to the ASP.NET application without re-authentication.

Magento Identity Provider(IDP) - Accurate B2B Authorization

Accurate B2B Authorization

Company-level attributes enable structured access control and support complex enterprise workflows.

Popular Usecase

Unified B2B Authentication Between Magento and ASP.NET Applications

Enterprises running Magento storefronts alongside ASP.NET-based business applications require consistent identity and access control across platforms. By configuring Magento as the SAML IdP, organizations enable one-time authentication with secure attribute transmission for customer identification, role assignment, and company-level authorization. This ensures frictionless access while maintaining enterprise-grade security.

Magento SAML IDP | Magento and ASP.NET Applications
Magento SAML IDP | Scalable SAML IDP Architecture for Integrations

Scalable SAML IDP Architecture for Future Integrations

This Magento-as-IdP architecture is designed to be extensible, allowing organizations to integrate additional ASP.NET applications, onboard partner portals or internal enterprise tools, and standardize authentication across multiple systems. The same SAML identity layer can be reused without duplicating authentication logic, making it a scalable and sustainable long-term identity strategy.

Frequently Asked Questions

FAQ | Module FAQsModule Inquiries

Does miniOrange store any user data?

miniOrange does not store or transfer any data which is coming from the Identity provider (IdP) to the Magento. All the data remains within your premises / server.

Are the licenses a one-time payment or an annual subscription?

The extension licenses are subscription-based and need to be renewed annually. Renewing ensures you receive extension updates, including security patches and compatibility adjustments for the latest versions. The extension licenses are subscription based and you have to pay annually.

What is one instance?

A Magento instance refers to a single installation of a Magento site. It refers to each individual website where the extension is active. In the case of a single site Magento, each website will be counted as a single instance.

Do we need to purchase for all multisite/subsites?

No, you only need to pay for the sites where you want to activate the extension in your Magento multisite network.

Need seperate license for my non-production environment?

Yes, we have an instance based licensing policy. The extension's licencing is linked to the domain of the Magento instance, thus if you have a dev-staging-prod environment, you'll need three licences (with discounts applicable on pre-production environments).

Want to Schedule a Demo?

mo-form

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

Something went wrong. Please submit your query again

Hello there!

Need Help? We are right here!

support