It's often difficult to find the correct configuration for JupyterHub Authenticators, especially LDAP.
This command line utility loads your jupyterhub_config.py file, and attempts to login using a configured username and password with debug logging enabled.
This should allow you to quickly see whether your Authenticator configuration is correct.
| # Example of using JupyterHub with an Apache proxy under a prefix | |
| version: "3" | |
| services: | |
| jhub: | |
| image: quay.io/jupyterhub/jupyterhub-demo:5.1.0 | |
| networks: | |
| - jhub | |
| volumes: |
| name: nbgitpuller | |
| channels: | |
| - conda-forge | |
| dependencies: | |
| - python=3.12 | |
| - nbgitpuller |
| channels: | |
| - conda-forge | |
| dependencies: | |
| - jupyter-offlinenotebook | |
| - tldraw |
| #!/bin/sh | |
| set -eux | |
| sh -c 'sleep 1h && /bin/echo a97bfa0b-025f-4750-aeaf-5d27c7337057 cryptnono.banned.string1' | |
| exit 1 |
| #!/bin/bash | |
| loopdevice=/dev/loop0 | |
| loopfile=crypt.loop | |
| #megabytes | |
| loopsize=256 | |
| #/dev/mapper/xxxxx when open | |
| cryptmapper=myCrypt |
| # Access a Kubernetes node root filesystem under /mnt/root | |
| # Replace nodename.k8s.example.org with the Kubernetes node you want to access | |
| # | |
| # kubectl apply -f root-host-volume-shell.yaml | |
| # kubectl exec -it root-host-volume-shell -- bash | |
| --- | |
| apiVersion: v1 | |
| kind: Pod | |
| metadata: | |
| name: root-host-volume-shell |
| repos: | |
| - repo: https://github.com/pycqa/isort | |
| rev: 5.12.0 | |
| hooks: | |
| - id: isort | |
| - repo: https://github.com/psf/black | |
| rev: 23.3.0 | |
| hooks: | |
| - id: black |
| #!/bin/sh | |
| # Based on Windows EC2Launch Module/Scripts/Send-AdminCredentials.ps1 script | |
| # | |
| # Include this at the end of your EC2 userdata | |
| # Once the console output is available you should be able to run | |
| # aws ec2 get-password-data --instance-id=INSTANCE_ID --priv-launch-key SSH_PRIVATE_PEM_FILE | |
| # to get the randomly generated password | |
| # | |
| # Note that SSH password authentication is disabled on the SSH server by default |
| # make sure crypt module in use | |
| sudo modprobe dm-crypt | |
| # Find out which drive it was with the following command: | |
| sudo fdisk -l | |
| # You must mount /dev/sda3 myvolume | |
| # use cryptsetup, device is accessible under /dev/mapper/myvolume | |
| sudo cryptsetup luksOpen /dev/sde3 myvolume |