Studio SSO was retired in the identity wiki. CMS_OAUTH2_KEY_SSO is still in the LMS settings. The client id still exists at the authorization server. Authors who bookmark /login on the CMS host can still start that code flow.
Retiring a “log into Studio via LMS” app is two objects: the LMS OAuth client configuration, and the issuer’s client. Removing the wiki page is neither.
Inventory CMS_OAUTH2_KEY_SSO (and its secret) after Studio SSO is supposed to be gone.
What the Studio SSO client actually is
On Open edX, CMS (Studio) can authenticate authors through the LMS OAuth2 provider. Tutor renders CMS_OAUTH2_KEY_SSO (and a matching secret) into LMS / CMS settings. That key is the OAuth2 client id the CMS uses when it sends authors to the LMS to sign in.
It is separate from:
-
JWT_COMMON_SECRET_KEY/JWT_AUTH(token signing between LMS and CMS) OAUTH_OIDC_ISSUER- third-party OAuth clients you created for mobile apps
A leftover JWT secret is a different note. This one is leftover client credentials for a SSO path you believe you turned off.
Run this only against an Open edX / Tutor instance you own.
Why the client survives
The project that added Studio SSO copied CMS_OAUTH2_KEY_SSO into config.yml (or let Tutor generate it). A later project put authors on a campus IdP in front of Studio and declared LMS-mediated SSO dead. Nobody ran tutor config to clear the key, and nobody deleted the OAuth2 application row inside the LMS (Django admin / OAuth2 provider applications).
The LMS OAuth2 provider still has a redirect URI pointing at the CMS host. That URI is leftover trust of the same class as a Moodle™ redirect_uri.
The fixture
On a test Tutor install you own:
- Print or inspect (do not paste secrets into tickets):
CMS_OAUTH2_KEY_SSO CMS_OAUTH2_SECRET_SSO # name may vary slightly by Tutor version; record the actual key LMS_HOST CMS_HOST - In the LMS Django admin (or the oauth2_provider applications table), find the application whose client id equals
CMS_OAUTH2_KEY_SSO. Record redirect URIs, skip authorization flag, and whether it is still active. - From a throwaway browser profile, hit the CMS login URL that would start SSO. Record whether you are redirected to the LMS authorize endpoint with that client id.
# only against a site you own curl -sS -D - -o /dev/null \ -w "%{http_code} %{url_effective}\n" \ "$CMS/login" - If Studio SSO is retired by policy, disable or delete the application, remove the Tutor config keys, restart LMS and CMS, and repeat the curl. Expect the CMS login to use the IdP path you replaced it with, not
client_id=$CMS_OAUTH2_KEY_SSO.
Keep a row:
| Field | Policy | Config | OAuth application | Live redirect |
|---|---|---|---|---|
| Studio SSO via LMS | retired / live | key set? | row present? | authorize URL still used? |
Alert when:
- Policy says retired and the OAuth application row is still active.
- Redirect URIs on that application include a retired CMS hostname.
- The secret in Tutor config does not match the application secret (someone rotated one side).
-
CMS_OAUTH2_KEY_SSOis the empty string in config but the Django application still exists (or the reverse).
What this inventory is not
This is not a JWT shared-secret check and not an MFE login URL list. It answers one question: after Studio SSO via the LMS was retired, is CMS_OAUTH2_KEY_SSO still an active OAuth2 client with a redirect URI on a CMS host you run.
Disclosure: I work on GuardLMS, a product of Ldesign Media. GuardLMS’s Open edX connector is alpha. CMS_OAUTH2_KEY_SSO is a Tutor-rendered LMS OAuth client for Studio SSO; confirm the setting name on your Tutor 22 / Verawood.2 install before you alert.
