KeyCloakAuthenticator
Authenticates users via SSO using OIDC.
This authenticator implements a refresh mechanism, ensuring that the tokens stored in the user dict are always up-to-date (if the update is not possible, it forces a re-authentication of the user). It also allows exchanging the user token for tokens that can be used to authenticate against other (external) services.
This Authenticator is built on top of OAuthenticator and should be possible to use some of its configuration values.
Requirements
- Jupyterhub
- oauthenticator
- PyJWT[crypto]
- openssl_devel (see below)
Installation
pip install keycloakauthenticator
If you enable check_signature, you also need the openssl_devel (or equivalent in your distribution) package.
Usage
In your JupyterHub config file, set the authenticator and configure it:
# Enable the authenticator
c.JupyterHub.authenticator_class = "keycloakauthenticator.KeyCloakAuthenticator"
c.KeyCloakAuthenticator.username_claim = "cern_upn"
# URL to redirect to after logout is complete with auth provider.
c.KeyCloakAuthenticator.logout_redirect_url = "https://cern.ch/swan"
c.KeyCloakAuthenticator.oauth_callback_url = "https://swan.cern.ch/hub/oauth_callback"
# Specify the issuer url, to get all the endpoints automatically from .well-known/openid-configuration
c.KeyCloakAuthenticator.oidc_issuer = "https://auth.cern.ch/auth/realms/cern"
# If you need to set a different scope, like adding the offline option for longer lived refresh token
c.KeyCloakAuthenticator.scope = ["profile", "email", "offline_access"]
# Only allow users with this specific roles (none, to allow all)
c.KeyCloakAuthenticator.allowed_roles = []
# Specify the role to set a user as admin
c.KeyCloakAuthenticator.admin_role = "swan-admin"
# If you have the roles in a non default place inside the user token, you can retrieve them
# This must return a set
def claim_roles_key(env, token):
return set(token.get("app_roles", []))
c.KeyCloakAuthenticator.claim_roles_key = claim_roles_key
# Request access tokens for other services by passing their id's (this uses the token exchange mechanism)
c.KeyCloakAuthenticator.exchange_tokens = ["eos-service", "cernbox-service"]
# If your authenticator needs extra configurations, set them in the pre-spawn hook
def pre_spawn_hook(authenticator, spawner, auth_state):
spawner.environment["ACCESS_TOKEN"] = auth_state["exchanged_tokens"]["eos-service"]
spawner.environment["OAUTH_INSPECTION_ENDPOINT"] = authenticator.userdata_url.replace("https://", "")
spawner.user_uid = auth_state["oauth_user"]["cern_uid"]
decoded_token = authenticator._decode_token(auth_state["access_token"])
spawner.user_roles = authenticator.claim_roles_key(authenticator, decoded_token)
c.KeyCloakAuthenticator.pre_spawn_hook = pre_spawn_hook
# Configure token signature verification
c.KeyCloakAuthenticator.check_signature = True
c.KeyCloakAuthenticator.jwt_signing_algorithms = ["HS256", "RS256"]
# Once a token is refreshed, by default jupyterhub does not trigger a refresh again (triggered when receiving any authenticated request) in `Authenticator.auth_refresh_age` seconds (default 5 minutes)
# If you want to refresh the token less often, and align the refresh to your tokens expiration, which will also trigger the update of the oAuth/OIDC token, this value can be changed:
c.KeyCloakAuthenticator.auth_refresh_age = 900 # 15 minutes
It's also necessary to configure the Client ID and secret. One way of doing this is by setting the following environment variables:
OAUTH_CLIENT_ID=my_id
OAUTH_CLIENT_SECRET=my_secret
Metadata
Release files for keycloakauthenticator 4.0.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| keycloakauthenticator-4.0.13.tar.gz | 8.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| keycloakauthenticator-4.0.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.2 kB
Release files / keycloakauthenticator-4.0.13.tar.gz
| Download URL | keycloakauthenticator-4.0.13.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7036ef5b02faae6cac49d83dc8a977073b1b96e2bf5c4415bbf1603bff7c1c40
|
|
BLAKE2b-256 checksum How to use checksums |
3ea3fb9c2935b393ccb7c9a13320cd3f11572bdadd7dbad03fcea0e934e036a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Oct 2, 2026.
Transparency logRelease files / keycloakauthenticator-4.0.13-py3-none-any.whl
| Download URL | keycloakauthenticator-4.0.13-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30a31c42a0cffb65c922ac474af287968c411195ba6bed1905597917bcd71f0e
|
|
BLAKE2b-256 checksum How to use checksums |
96448113003988f2c658acbef6c40372fc7589657b5b0badab5fa764fefc03eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Oct 2, 2026.
Transparency log