jupyter-server-user-token
A simple Jupyter Server extension that adds the server's User Token (if it exists) into the process's environment as JUPYTER_SERVER_USER_TOKEN.
Why?
Some frontend extensions and visualisation libraries use iframes to render documents served out on Jupyter Server Proxy.
These iframes might have an href target like: /proxy/index.html?some=query-params and work happily when used in notebooks and lab.
In the context of myst the same visualisations run into issues when connecting to remote Jupyter servers running on different origins, as the cookie-based auth in play in a same-origin lab front ends, will fail on a typlical myst website.
By exposing the user token, end user code can do something about this and supply the user token string to the library / extension code that needs it.
Metadata
Release files for jupyter-server-user-token 0.1.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 | |
|---|---|---|---|---|
| jupyter_server_user_token-0.1.0.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jupyter_server_user_token-0.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 6.7 kB
Release files / jupyter_server_user_token-0.1.0.tar.gz
| Download URL | jupyter_server_user_token-0.1.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d4325fcfa61ccb4d1171321a8076a3ab7a157cc5cbf96a76aad608a0e812fa9
|
|
BLAKE2b-256 checksum How to use checksums |
aa7ab17fa1e8872a610cf2544b6dfd2921d69db216ef5e310c8114372f2ea0a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.15
|
Release files / jupyter_server_user_token-0.1.0-py2.py3-none-any.whl
| Download URL | jupyter_server_user_token-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
0ccfcb8b2a9bca77b806f66c2f15828e1464536ced5109b09fe71577b49c31cc
|
|
BLAKE2b-256 checksum How to use checksums |
3918b78901297239a7962ea2dfee69510b6c579d353b30fb8c726d0151c45b76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.15
|
Security for jupyter-server-user-token 0.1.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.