nopStation Enterprise Single Sign-On
Let employees, wholesale buyers and partners sign in to your store with the Microsoft, Okta, Google or other work account they already use. Customer roles and price tiers follow your directory—and sign-in runs directly between your store and your identity provider, with no third-party broker.
Runs inside your nopCommerce store · IIS, Linux or Docker · Multi-store ready
Direct sign-in · No third-party broker
The Problem
The moment you sell to businesses or run a staff store, separate store passwords create extra work for your team and extra risk for your customers.
Staff and buyers juggle one more login, forget it, and open support tickets. Weak or reused passwords become your security problem.
Someone has to verify each new B2B account and assign the right customer role or price tier by hand—slowly, and not always correctly.
When someone leaves their company, their store account keeps working until somebody remembers to disable it.
nopStation SSO hands sign-in to the directory your customers’ organizations already manage. Access and roles follow it at every sign-in, and optional SCIM deactivates accounts as soon as someone leaves.
What You Get
A plugin that lives inside your store, speaks SAML 2.0 and OpenID Connect, and keeps control, data and sign-in traffic on your own infrastructure.
Guided presets for the major providers, plus Generic for any other SAML 2.0 or OIDC directory. Connect several at once.
Untrusted issuers, invalid certificates, blocked domains and risky email matches are rejected or held for review—so mistakes fail closed.
Directory groups become nopCommerce customer roles at every sign-in. Add SCIM to keep accounts aligned as people join or leave.
No SaaS broker in the middle. Deploy with your store on IIS, Linux or Docker, and keep an emergency admin login if the IdP is down.
Presets fill in the right endpoints and claim names for major providers. Generic covers any other standards-based SAML 2.0 or OpenID Connect directory.
Generic is designed for providers such as Shibboleth, Salesforce, ForgeRock, CyberArk and SiteMinder—check claim and role mapping in the built-in simulator before go-live. WS-Federation is not supported; use SAML 2.0 or OIDC instead.
How It Works
Setup happens in nopCommerce Admin—no custom code.
Choose a preset or Generic, import the metadata or discovery URL, and copy the store’s redirect / ACS URL into your IdP.
Map directory groups to customer roles and price tiers, choose how existing accounts are linked, and test it all in the simulator.
Staff and buyers sign in with their work account. Every sign-in, role change and rejection is recorded in the audit log.
For Store Operators
Configure providers, approve risky links and see why a sign-in was blocked—without leaving your store’s admin area.
Basic and Advanced setup modes, metadata import, and a simulator to check claim and role mapping before go-live.
See which customers are linked to which IdP, approve email collisions, and see exactly why a sign-in was blocked.
Searchable history of sign-ins, role changes and configuration updates, kept with your nopCommerce data.
Administrators can still reach Admin if the identity provider is unavailable or storefront password login is turned off.
Use Cases
Verified buyers land in the right customer role and contract price tier automatically—far fewer manual account approvals.
Staff sign in with their work account, and company-domain rules decide who can buy.
Point each storefront at the right identity provider while customers and providers stay scoped per store.
Signed federation, dual-certificate support and an in-store audit trail for teams that face strict security reviews.
For IT & Security Teams
Answers
Talk to nopStation
Book a call with our team to walk through your identity provider, store setup and role-mapping needs.