Skip to main content

Open Learning Social Auth

An Open edX plugin implementing MIT social auth backend

Version Compatibility

Compatible with all edx releases

For this plugin’s compatibility with Open edX, see the Open edX Release Compatibility table.

Installing The Plugin

For detailed installation instructions, please refer to the plugin installation guide.

Installation required in:

  • LMS

Configurations

This section outlines the steps for integrating your application with ol-social-auth for various deployment scenarios. Please refer to the corresponding documentation for detailed instructions.

  • Devstack: To configure ol-social-auth with an edx-platform instance provisioned using devstack, follow the instructions here

  • Tutor: To configure ol-social-auth with an edx-platform instance provisioned using tutor, follow the instructions here also

How to use

Make sure to properly configure the plugin following the links in the above “Configurations” section before use.

  • Install the plugin in the lms following the installation steps above.

  • Verify that you are not logged in on edx-platform.

  • Create a new user in your MIT application and verify that a corresponding user is successfully created on the edX platform.

Expired Token Cleanup

This plugin includes a scheduled Celery task (ol_clear_expired_tokens) that automatically removes expired OAuth2 access tokens, refresh tokens, and grant tokens from the database.

Behavior:

  • Runs every Monday at 9:00 AM (server time) via Celery Beat by default. The schedule can be customized by overriding the ol_clear_expired_tokens entry in CELERYBEAT_SCHEDULE.

  • Uses django-oauth-toolkit’s clear_expired() to delete tokens that have exceeded the configured expiration threshold.

  • Sets REFRESH_TOKEN_EXPIRE_SECONDS to 30 days (overriding the edx-platform default of 90 days). Tokens revoked or expired longer than 30 days ago will be cleaned up.

Note: If running this plugin for the first time on a database with a large backlog of expired tokens (millions of rows), consider running the edx_clear_expired_tokens management command manually first to reduce the initial volume before relying on the scheduled task.

Metadata

Release files for ol-social-auth 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ol-social-auth 0.3.0
File Size Uploaded Provenance Actions
ol_social_auth-0.3.0.tar.gz 4.8 kB Without provenance Details for ol_social_auth-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ol-social-auth 0.3.0
File Interpreter ABI Platform Actions
ol_social_auth-0.3.0-py3-none-any.whl Python 3 none any Details for ol_social_auth-0.3.0-py3-none-any.whl

Total release size: 11.9 kB

Release files / ol_social_auth-0.3.0.tar.gz

Download URL ol_social_auth-0.3.0.tar.gz
Size 4.8 kB
Tags Source
SHA-256 checksum
How to use checksums
1ba7c86544f37c0b5e6fd031745637bdf4766c2d85ecf16018790384fa40eeb0
BLAKE2b-256 checksum
How to use checksums
0d0647d38100de6c424510c5d5bee9348d5ee52efe28f2a04f96a154ede2a17d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.7

Release files / ol_social_auth-0.3.0-py3-none-any.whl

Download URL ol_social_auth-0.3.0-py3-none-any.whl
Size 7.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
403448894667f84c0ede6d6edc831c4c34cbcebaa3a93e60e3294418cb08b525
BLAKE2b-256 checksum
How to use checksums
983296bef2305e44144651c63399b68145255efe4ac2e9b6f391270d6cdbfbcd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.7

Security for ol-social-auth 0.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page