SSO on managed Open edX: SAML or OIDC with your identity provider

Short answer (updated November 17, 2026)

Cubite runs managed Open edX from $1,260 a month for up to 1,000 concurrent learners, and SSO (SAML / OIDC) implementation is included in every tier: Lean $1,260 a month, Resilient $1,850 a month and Scale from $3,400 a month. Cubite sets up the Open edX side against your identity provider over SAML 2.0 or OIDC, and your IT team registers the platform in your identity provider. Managed Moodle includes the same SSO implementation in every tier, from $690 a month.

What Cubite sets up

On managed Open edX, Cubite configures your platform's side of SAML or OIDC, adds your identity provider as a sign-in option and sets how accounts are created at a learner's first sign-in, as part of the SSO (SAML / OIDC) implementation included in every tier. In Open edX's own documentation, SSO is called third-party authentication (docs.openedx.org, read November 17, 2026).

What managed Open edX includes

Will SSO on managed Open edX work with our identity provider?

If it supports SAML 2.0 or OIDC, yes: SSO (SAML / OIDC) implementation is included in every Cubite managed Open edX tier, from $1,260 a month. Open edX's current release supports SAML 2.0 identity providers, has sign-in with Google, Facebook, LinkedIn, Azure Active Directory and Apple available by default, and can add other OAuth2-based providers in its settings (edx-platform, release/verawood, read November 17, 2026).

What your IT team does

Cubite does the work on the Open edX side. Your IT team does the identity provider's side:

  • For SAML: register the platform in your identity provider with the SAML metadata URL Cubite sends you, and send Cubite your identity provider's metadata URL and entity ID.
  • For OIDC or another OAuth2 provider: register the platform as an application in your identity provider, with the redirect address Cubite gives you, and give Cubite the client ID and client secret your provider issues.
  • Choose what your identity provider sends. For SAML, Open edX takes a user ID that identifies each learner, and can also take the full name, given name and surname, a username hint and the email address.
  • Agree with Cubite how accounts are created at a learner's first sign-in and whether their details sync at each sign-in (the next two answers), then try the sign-in with a few accounts of your own before learners use it.

The Open edX side of these steps follows Open edX's SAML and OAuth2 guides on docs.openedx.org and its settings on the release/verawood branch, read November 17, 2026.

What happens at a learner's first SSO sign-in to Open edX?

On managed Open edX from Cubite, as on any Open edX platform, a learner's first SSO sign-in creates their Open edX account from the details your identity provider sends and links it to that provider. Each identity provider's entry in Open edX sets whether the learner first confirms those details on a registration form and confirms their email address: in the current release's code, a SAML provider skips both by default and an OAuth2 provider asks for both (edx-platform, release/verawood, read November 17, 2026). Cubite sets these with you as part of the SSO implementation.

Does a name or email change in our identity provider reach Open edX?

Not by default. On managed Open edX from Cubite, as on any Open edX platform, each SSO account is a full Open edX account with its own copy of the learner's details, copied once when the account is created. An identity provider's entry can instead sync the details at every SSO sign-in, and Open edX then tells the learner when the sync changes their email address (edx-platform, release/verawood, read November 17, 2026).

Can SSO learners still sign in to Open edX with a password?

By default, yes, once they set one. On managed Open edX from Cubite, as on any Open edX platform, an account created through SSO gets a generated password the learner never sees; they can set their own with reset password and then sign in either way. Open edX also has a setting, off by default, that allows SSO sign-in only and turns off password sign-in and registration. One account can be linked to several identity providers, and a provider can be linked or unlinked at any time (Open edX's SSO documentation and edx-platform, release/verawood, read November 17, 2026).

Is SSO priced separately on managed Open edX?

No. SSO (SAML / OIDC) implementation is part of every Cubite managed Open edX tier: Lean $1,260 a month, Resilient $1,850 a month and Scale from $3,400 a month, with no setup fee on any tier.

SSO on Cubite LMS and managed Moodle

Managed Moodle includes SSO (SAML / OIDC) implementation in every tier, from $690 a month.

On Cubite LMS, SSO with Google, GitHub or Facebook sign-in is included at $290; SAML SSO and SCIM are Enterprise, on request and scoped with your contract.

Cubite LMS Growth also includes signed-token sign-in: your own portal or app signs a learner in to your Cubite site with a short-lived signed token that can name the learner's groups, so learners need no second password. It is not SAML or SCIM.

Managed MoodleCubite LMS plans

Talk to a person

Book a 30-minute call, or email amir@cubite.io.

Support

How can we help?

Send us a message and we'll get back to you shortly.

We typically respond within 24 hours