enterprise-integrated-channels
Purpose
An integrated channel is an abstraction meant to represent a third-party system which provides an API that can be used to transmit EdX data to the third-party system. The most common example of such a third-party system is an enterprise-level learning management system (LMS). LMS users are able to discover content made available by many different content providers and manage the learning outcomes that are produced by interaction with the content providers. In such a scenario, EdX would be the content provider while a system like SAP SuccessFactors would be the integrated channel.
Getting Started with Development
Please see the Open edX documentation for guidance on Python development in this repo.
Running tests locally
Once inside an LMS Devstack container, you’ll want to run unit tests via tox:
tox
tox will run tests via the pytest inside a virtual environment. If you want to pass arguments to pytest, you can pass them after a -- in the command:
tox -- tests/test_channel_integrations/test_api/test_base_views.py -v
It’s necessary to use tox both because of its use of a python virtual environment (which helps stay isolated from the edxapp python virtual environment), and because it adds the mock_apps/ directory to the PYTHONPATH.
Getting Help
Documentation
Start by going through the documentation. If you need more help see below.
More Help
If you’re having trouble, we have discussion forums at https://discuss.openedx.org where you can connect with others in the community.
Our real-time conversations are on Slack. You can request a Slack invitation, then join our community Slack workspace.
For anything non-trivial, the best path is to open an issue in this repository with as many details about the issue you are facing as you can provide.
https://github.com/openedx/enterprise-integrated-channels/issues
For more information about these options, see the Getting Help page.
License
The code in this repository is licensed under the AGPL 3.0 unless otherwise noted.
Please see LICENSE.txt for details.
Contributing
Contributions are very welcome. Please read How To Contribute for details.
This project is currently accepting all types of contributions, bug fixes, security fixes, maintenance work, or new features. However, please make sure to discuss your new feature idea with the maintainers before beginning development to maximize the chances of your change being accepted. You can start a conversation by creating a new issue on this repo summarizing your idea.
The Open edX Code of Conduct
All community members are expected to follow the Open edX Code of Conduct.
People
The assigned maintainers for this component and other project details may be found in Backstage. Backstage pulls this data from the catalog-info.yaml file in this repo.
Reporting Security Issues
Please do not report security issues in public. Please email security@openedx.org.
1 maintainer
Metadata
1 maintainer
Release files for enterprise-integrated-channels 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| enterprise_integrated_channels-0.3.0.tar.gz | 699.7 kB | With provenance | Details for enterprise_integrated_channels-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| enterprise_integrated_channels-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for enterprise_integrated_channels-0.3.0-py3-none-any.whl |
Total release size: 1.1 MB
Release files / enterprise_integrated_channels-0.3.0.tar.gz
| Download URL | enterprise_integrated_channels-0.3.0.tar.gz |
|---|---|
| Size | 699.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e0a71d602d7309498af9f7159699be78bca0c21bba430a5010f96fd404c94c9
|
|
BLAKE2b-256 checksum How to use checksums |
eecc15a247d2a23b9a40ccc4325561086223c0caa0d9eb96cb2017aa78132ff6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / enterprise_integrated_channels-0.3.0-py3-none-any.whl
| Download URL | enterprise_integrated_channels-0.3.0-py3-none-any.whl |
|---|---|
| Size | 363.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b7e5644946524f1d52f766f53e9ea0d6c741447ab27fe8fcb386945eb3fd589c
|
|
BLAKE2b-256 checksum How to use checksums |
2f3d0410b95bb26c890974e52a77576c893699113a70fa516b9984ae9f3b6fac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for enterprise-integrated-channels 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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for enterprise_integrated_channels-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA 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.
