django-openstax-accounts
django-openstax-accounts is a Django app to read data from the logged-in user’s OpenStax account using the SSO cookie.
Quick start
Add the following settings to your settings file:
# OpenStax Accounts settings SSO_COOKIE_NAME = "<oxa_env>" SSO_SIGNATURE_PUBLIC_KEY = "<public_key_for_accounts>" SSO_ENCRYPTION_PRIVATE_KEY = "<private_key_for_accounts>"
Usage
If you need to access the current user’s OpenStax account UUID, you can use the get_logged_in_user_uuid function from openstax_accounts.functions. This function will a UUID.:
from django.shortcuts import render
from openstax_accounts.functions import get_logged_in_user_uuid
def my_view(request):
user_uuid = get_logged_in_user_uuid(request)
# function to do something with the uuid, like save it to your database or use for an API call
return render(request, "my_template.html", {"user_uuid": user_uuid})
Metadata
Release files for django-openstax-accounts 1.2.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 |
|---|---|---|---|---|
| django_openstax_accounts-1.2.0.tar.gz | 18.0 kB | With provenance | Details for django_openstax_accounts-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_openstax_accounts-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for django_openstax_accounts-1.2.0-py3-none-any.whl |
Total release size: 36.5 kB
Release files / django_openstax_accounts-1.2.0.tar.gz
| Download URL | django_openstax_accounts-1.2.0.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2e8951b6bdd38b9695f0181b65fb922d167889ad669d44eaedcfc0a307c0229
|
|
BLAKE2b-256 checksum How to use checksums |
1e9daf991e89f68c82a7451331d96a0fbd5835ea03ddb4b6905feff97b7b5b90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 10, 2026.
Transparency logRelease files / django_openstax_accounts-1.2.0-py3-none-any.whl
| Download URL | django_openstax_accounts-1.2.0-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2f4bb1ea010ba91997baa8acd625a5aa56c84341d15197e0d5a7b534ee1f8f9
|
|
BLAKE2b-256 checksum How to use checksums |
28d4ea60fd13cf014f4bad582bbfc1db5280ab113dc8d09fec21c09cf453f886
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 10, 2026.
Transparency logSecurity for django-openstax-accounts 1.2.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 django_openstax_accounts-1.2.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 Mar 10, 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.