The short answer
Three SSO options:
- OpenID Connect (OIDC) via the built-in Social Login Key (Microsoft, Google, custom providers): default for Entra ID or Google Workspace.
- SAML, when your identity team or provider prefers it, via a custom app or broker.
- LDAP for on-premises Active Directory, with group-to-role mapping.
Pick what your provider supports best, then focus on user matching, roles and offboarding: where SSO succeeds or fails.
Choosing between OIDC, SAML and LDAP
| OpenID Connect | SAML | LDAP | |
|---|---|---|---|
| Typical identity provider | Microsoft Entra ID, Google Workspace, Okta | Okta, Entra ID, ADFS, other enterprise IdPs (some Okta and other enterprise set-ups prefer it) | On-premises Active Directory |
| How it works | Browser redirect, signed ID token | Browser redirect, signed XML assertion | ERP checks credentials against the directory |
| True single sign-on | Yes | Yes | No: users type directory credentials into the ERP |
| MFA enforced by your IdP | Yes | Yes | Not by the IdP's sign-in page |
| In ERPNext | Standard Social Login Key | Custom app or broker | Standard LDAP settings |
| Our usual view | Default choice | When policy requires it | Only where there is no cloud identity |
LDAP gives one password, which helps, but it is not modern single sign-on: your provider's multi-factor prompts and conditional access do not come with it.
How Microsoft describes OIDC and SAML
Microsoft describes OpenID Connect as an extension of OAuth 2.0 that enables SSO using an ID token, and SAML as an XML-based standard for exchanging authentication data between an identity provider and an application. Both are well supported. SAML is not one of the standard social login options, which is why it needs a custom app or broker.
The pitfalls we see most often
| Pitfall | What goes wrong, and the fix |
|---|---|
| Careless email matching | A changed name or domain alias means no sign-in or a duplicate user. Agree the identifier before go-live |
| Generous auto-created users | A broad default role lets anyone in your tenant into accounting. New users get no role, or a minimal one, until approved |
| Roles drifting from the directory | Moving from sales to purchasing should change roles. LDAP rechecks groups at sign-in; with OIDC or SAML, provider groups or a named ERP administrator drive ERP roles, not both: mixing starts drift |
| Offboarding that leaves access | Disabling someone in Entra ID stops new sign-ins, but an ERP session can last until it expires. Also disable the ERP user, end sessions, revoke API keys (offboarding checklist) |
| Password sign-in left open | Old ERP passwords bypass your MFA policy. Decide who, if anyone, still uses one |
| No break-glass account | If the identity provider fails, or your internet link drops and the ERP cannot reach a cloud provider, someone must still get in: one or two local administrators with long, stored passwords and MFA, and a record of who may use them |
| Secrets expiring quietly | A lapsed client secret or signing certificate locks everyone out at once. Record expiry dates with reminders, or document renewal |
| Portal users caught up | Customers and suppliers should usually sign in separately from staff, without a confusing SSO button |
| Integrations on personal accounts | Use dedicated API credentials with limited roles, not a person's account SSO will later disable |
Rather talk it through? If you are planning SSO for ERPNext or Prometheus and want the role mapping and offboarding designed properly, we can walk through your identity set-up with you. Talk to a Promatics specialist
A pre-launch checklist
- Protocol (OIDC, SAML or LDAP) agreed with whoever runs identity
- Matching identifier agreed; existing ERP users checked against the directory
- New users get no role, or a minimal one, until approved
- Source of truth for roles (directory groups or ERP) documented
- MFA and conditional access enforced at the identity provider
- Password sign-in limited to named break-glass accounts
- Offboarding disables the ERP user, ends sessions, revokes API keys
- Secret and certificate expiry dates recorded, with reminders
- Portal users and integration accounts kept out of staff SSO
- Tested on a test site: user, manager, leaver, failed sign-in
How we build it
- Test site firstNever straight in production.
- Standard settingsSocial Login Key or LDAP, where they are enough.
- Custom appSAML, group role mapping or provisioning rules, under version control.
- Upgrade-safeNot overwritten by ERPNext upgrades; re-tested each release.
- DocumentationConfiguration, role mapping and offboarding steps handed over.
See ERPNext and Prometheus customisation for the wider range of work we do.
When to bring in help
One company on Google Workspace or Entra ID, few users, simple roles? A capable administrator can configure OIDC from the documentation above. Bring in help when roles must follow directory groups, SAML is required, you run several companies or portals, or an auditor or insurer will ask how access is granted and removed: there, a small mistake leaves a door open nobody notices until it matters.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- Social Login Key, Frappe Framework documentation
- Setting up LDAP, ERPNext documentation (Frappe)
- OpenID Connect (OIDC) on the Microsoft identity platform, Microsoft Learn
- SAML authentication with Microsoft Entra ID, Microsoft Learn
- Role Based Permissions, ERPNext documentation (Frappe)
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.