csrd-auth
Pluggable JWT authentication for FastAPI — authenticators, key providers, and dependency factories.
Tier 2 (bridge) — depends on csrd-models and csrd-context only.
Installation
pip install "csrd-auth @ git+https://github.com/csrd-api/fastapi-common.git#subdirectory=packages/auth"
Usage
from csrd.auth import (
JWTAuthenticator,
StaticKeyProvider,
create_bearer_dependency,
create_jwt_bearer,
)
Quick start — JWT bearer dependency
# Standalone (provide your own token_finder)
from csrd.auth import create_jwt_bearer
auth_dep = create_jwt_bearer(
key="your-secret",
token_finder=lambda: extract_token_from_request(),
)
When used with csrd.versioning, wire in find_token explicitly:
from csrd.auth import create_jwt_bearer
from csrd.versioning import find_token
auth_dep = create_jwt_bearer(key="your-secret", token_finder=find_token)
Authenticators
| Class | Strategy |
|---|---|
JWTAuthenticator |
Decode & verify JWT locally via PyJWT |
StaticAuthenticator |
Accept a fixed token (dev/testing) |
RemoteAuthenticator |
Validate via upstream HTTP endpoint |
CallbackAuthenticator |
Delegate to any sync/async callable |
ChainedAuthenticator |
Try multiple authenticators in order |
Key Providers
| Class | Strategy |
|---|---|
StaticKeyProvider |
Fixed string, bytes, or SecretStr |
EnvKeyProvider |
Read from app.state or settings loader |
JWKSKeyProvider |
Fetch from JWKS endpoint (cached with TTL) |
MultiKeyProvider |
Route by kid header or try all |
CallbackKeyProvider |
Delegate to any callable |
Protocols
Authenticator—(Request, str) -> UserClaimsKeyProvider—(token_headers, app) -> key
Both are @runtime_checkable protocols.
Dependency Tier
Tier 1 csrd.models csrd.lifespan csrd.context
Tier 2 csrd.auth csrd.logging csrd.delegate csrd.repository csrd.service
Tier 3 csrd.versioning
csrd.auth depends only on csrd.models (for UserClaims) and csrd.context (for user_info_context). It has no dependency on csrd.versioning.
1 maintainer
Metadata
1 maintainer
Release files for csrd-auth 0.5.29
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| csrd_auth-0.5.29.tar.gz | 19.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| csrd_auth-0.5.29-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.3 kB
Release files / csrd_auth-0.5.29.tar.gz
| Download URL | csrd_auth-0.5.29.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f067bc81c29f3642cd204e66fc5b50d75cf38fdfbe08b1fb2e700ab68196c2d
|
|
BLAKE2b-256 checksum How to use checksums |
e3ed048a7fc2b3ee5c90892da6eba35c4ef3db88fac7cad5e934e0e0dc116fd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 26, 2026.
Transparency logRelease files / csrd_auth-0.5.29-py3-none-any.whl
| Download URL | csrd_auth-0.5.29-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c456bbf59c3948842a4ea434edc41aade22c14ad122f999d78fcc593f237ba19
|
|
BLAKE2b-256 checksum How to use checksums |
a7cfffec34ee70edd0237af15d02cd9ec7a91e252e19fa9b21c9b642adbc5602
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 26, 2026.
Transparency log
