Auth Playground
A demonstration OAuth2 / OpenID Connect (OIDC) client application built with Authlib. This project illustrates how to integrate with an identity provider for user authentication, registration, and consent management. It can be used to play with the different interactions between clients and server, or debug a server implementation.
Installation
Using pip
pip install auth-playground
Using uv
uv add auth-playground
Using Docker
Run the pre-built image from GitHub Container Registry:
docker run -p 4000:4000 -e SECRET_KEY="your-secret-key" ghcr.io/authlib/auth-playground:latest
Or build locally:
docker build -t auth-playground .
docker run -p 4000:4000 -e SECRET_KEY="your-secret-key" auth-playground
Configuration
The application is configured using environment variables. Copy the example configuration file:
cp example.env .env
Edit .env and set the required values:
# Required
export SECRET_KEY="your-secret-key"
# Optional
export OAUTH_CLIENT_ID="your-client-id"
export OAUTH_CLIENT_SECRET="your-client-secret"
export OAUTH_AUTH_SERVER="https://your-identity-provider.example.com"
Registering with your Identity Provider
When registering this application with your identity provider, configure the following redirect URIs:
http://localhost:4000/authorize_callback
http://localhost:4000/logout_callback
Usage
auth-playground
The application will be available at http://localhost:4000
Development
Running Tests
uv run pytest
Code Style
uv run prek run --all-files
Release files for auth-playground 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| auth_playground-0.1.7.tar.gz | 59.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auth_playground-0.1.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 132.5 kB
Release files / auth_playground-0.1.7.tar.gz
| Download URL | auth_playground-0.1.7.tar.gz |
|---|---|
| Size | 59.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fa8c15e5cd4a877dbf7254f1218f6b0dd0a8c634e7c948049c22fb669d3d65b
|
|
BLAKE2b-256 checksum How to use checksums |
fb220076dc021e7b4c1db769c9d1486ffcdef2f032abe71bb07ccd1951aaada9
|
| 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 Jan 16, 2026.
Transparency logRelease files / auth_playground-0.1.7-py3-none-any.whl
| Download URL | auth_playground-0.1.7-py3-none-any.whl |
|---|---|
| Size | 73.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6bc43ed50ddd79abae47069b26ebe64c18121fdb9ca3a02153fe91eb41419f4
|
|
BLAKE2b-256 checksum How to use checksums |
a262b3df4856ffc69f540397e68671bf246680278c82206e0a0413e425b250ca
|
| 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 Jan 16, 2026.
Transparency log