Keycloak and Open edX SSO integration
Signing Open edX learners and staff in through Keycloak with Open edX third-party authentication over SAML 2.0 or OAuth2, including attribute mapping, account linking and auto-registration choices.

Connecting Open edX to identity providers, commerce, badges, notebooks, external graders, object storage and automation tools through documented features and plugins in the Tutor index.
Signing Open edX learners and staff in through Keycloak with Open edX third-party authentication over SAML 2.0 or OAuth2, including attribute mapping, account linking and auto-registration choices.
Selling Open edX courses through WordPress and WooCommerce with the Open edX Commerce plugin or the Webhook Receiver, now that the legacy e-commerce service is deprecated, and running WordPress as the marketing site.
Issuing digital badges from Open edX through its Credly and Accredible integrations: service accounts, badge templates or groups, enabling the feature in the LMS and Credentials, and mapping badges to course completion.
Embedding Jupyter notebooks in Open edX courses with the Tutor Jupyter plugin, which installs the Jupyter XBlock and runs JupyterHub with per-learner Docker containers, and the limits for Kubernetes production use.
Grading code submissions in Open edX with XQueue external graders and Codejail sandboxes: the event bus based XQueue flow, watcher setup and the security boundary for running untrusted learner code.
Planning Open edX file and media storage on S3-compatible object storage now that the Tutor MinIO plugin is deprecated and removed in Willow, including edx-val storage settings moving to Django STORAGES.
Connecting Open edX events to CRMs, HR systems and messaging with the Tutor Webhooks plugin and an n8n instance deployed alongside the platform, and what to keep out of automated flows for privacy.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.