token-utils
Purpose
App for the creation, signing, and decoding of various access tokens
TODO: The README.rst file should start with a brief description of the repository and its purpose. It should be described in the context of other repositories under the openedx organization. It should make clear where this fits in to the overall Open edX codebase and should be oriented towards people who are new to the Open edX project.
Getting Started
Developing
One Time Setup
# Clone the repository
git clone git@github.com:openedx/token-utils.git
cd token-utils
# Set up a virtualenv using virtualenvwrapper with the same name as the repo and activate it
mkvirtualenv -p python3.8 token-utilsEvery time you develop something in this repo
# Activate the virtualenv
workon token-utils
# Grab the latest code
git checkout main
git pull
# Install/update the dev requirements
make requirements
# Run the tests and quality checks (to verify the status before you make any changes)
make validate
# Make a new branch for your changes
git checkout -b <your_github_username>/<short_description>
# Using your favorite editor, edit the code to make your change.
vim ...
# Run your new tests
pytest ./path/to/new/tests
# Run all the tests and quality checks
make validate
# Commit all your changes
git commit ...
git push
# Open a PR and ask for review.Deploying
TODO: How can a new user go about deploying this component? Is it just a few commands? Is there a larger how-to that should be linked here?
PLACEHOLDER: For details on how to deploy this component, see the deployment how-to
Getting Help
Documentation
PLACEHOLDER: Start by going through the documentation. If you need more help see below.
(TODO: Set up documentation)
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/token-utils/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 have a discussion about your new feature idea with the maintainers prior to 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@tcril.org.
Change Log
Unreleased
[0.4.0] - 2026-09-28
Added
Added support for Python 3.12
Removed
Dropped support for Python 3.8; python_requires is now >=3.11
Changed
Upgraded requirements, including pyjwt 2.15. A malformed token signature may now raise jwt.DecodeError (the parent of InvalidSignatureError) instead of InvalidSignatureError
[0.3.0] - 2025-06-11
Changed
Replaced pyjwkest package with pyjwt for JWT token handling
[0.2.1] - 2022-12-16
Added
Fixed changelog formatting error
[0.2.0] - 2022-12-15
Added
Added API function to sign access token
Added API function to unpack access token
[0.1.0] - 2022-08-23
Added
First release on PyPI.
Release files for edx-token-utils 0.4.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 | |
|---|---|---|---|---|
| edx_token_utils-0.4.0.tar.gz | 23.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| edx_token_utils-0.4.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 45.5 kB
Release files / edx_token_utils-0.4.0.tar.gz
| Download URL | edx_token_utils-0.4.0.tar.gz |
|---|---|
| Size | 23.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
492f5ae6e90a5fab614972f5966873a482aeb4b7956310f80dba119eee52994f
|
|
BLAKE2b-256 checksum How to use checksums |
346abd89528741a12b2b6a2e075899c2b1fabf65282279b8e83835225c13746f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / edx_token_utils-0.4.0-py2.py3-none-any.whl
| Download URL | edx_token_utils-0.4.0-py2.py3-none-any.whl |
|---|---|
| Size | 22.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
9baf874882e3b012a0b5898e7678e1e8c7150c4e632f44b5c8cc60b440836244
|
|
BLAKE2b-256 checksum How to use checksums |
5501340c3d98256334785e8c3379485fd54297b2d7aec8b5715af8a76dec13a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for edx-token-utils 0.4.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.
