Apache Custos Jupyterhub Authenticator
The Apache Custos Jupyterhub Authenticator provides CILogon based federated authentication for Jupyterhub. In addtion it provides access to Custos IAM solutions such as
-
Fine-Grained Authorization
-
Secret Management
-
Service Accounts ..etc.
Additional Information : https://airavata.apache.org/custos/
Folder Structure
-
custosauthenticator
Includes oidc plugin to connect with custos oauth services
Configuration
Add following configuration to Jupyter Hub in helm chart configuration (values.yaml). You need to request an tenant from Custos Portal to start
- dev: https://dev.portal.usecustos.org/
- production: https://portal.usecustos.org/
Hub configuration
hub:
config:
CustosOAuthenticator:
client_id: CHANGE_ME
client_secret: CHANGE_ME
oauth_callback_url: https://<jupyter_host>/hub/oauth_callback
custos_host: custos.scigap.org
JupyterHub:
authenticator_class: custosauthenticator.custos.CustosOAuthenticator
Metadata
Release files for custos-jupyterhub-authenticator 1.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| custos_jupyterhub_authenticator-1.0.5-py3-none-any.whl | Python 3 | none | any | Details for custos_jupyterhub_authenticator-1.0.5-py3-none-any.whl |
Release files / custos_jupyterhub_authenticator-1.0.5-py3-none-any.whl
| Download URL | custos_jupyterhub_authenticator-1.0.5-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
12982ffc940ad68092f186f3bd49b1bc3feabd83504ae7e5c7b956acc1930a56
|
|
BLAKE2b-256 checksum How to use checksums |
ac16991d8600d9b452e824e207ee53caa957b822bf1a1e08339b6905b7d570b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for custos-jupyterhub-authenticator 1.0.5
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.