evoid-auth
Bring-your-own-provider authentication — Intent Handler system
Quick Start • Intent Handler • Config • API
Quick Start
uv add evoid-auth
Method 1: Intent Handler (Recommended)
from evoid_auth import register_provider, register_handlers
from evoid.core.extend import before
# Register your auth logic
async def my_auth(token: str) -> dict:
user = await db.find_by_token(token)
if not user:
raise ValueError("Invalid token")
return {"user": user.name, "role": user.role}
register_provider("my_auth", my_auth)
# Register auth as Intent handlers
register_handlers()
# Wire to pipeline
before("GET:/users", "authenticate")
before("POST:/admin", "authenticate")
Method 2: Direct API
from evoid_auth import authenticate, authorize, register_provider
register_provider("jwt", jwt_auth_fn)
# authenticate and authorize are pipeline processors
Intent Handler
evoid-auth registers these Intent handlers:
| Intent | Handler | Description |
|---|---|---|
auth.authenticate |
authenticate |
Extract token, call provider, set user in ctx |
auth.authorize |
authorize |
Check role against requirement |
How it works
register_handlers()registers auth Intents as pipeline processorsauthenticateextracts token from request headers/metadata- Calls your registered provider function
- Writes
user,role,auth_methodtoctx.state authorizechecksctx.state["role"]against required roles
Token Sources
The authenticate processor checks these in order:
metadata["token"]— direct fieldAuthorization: Bearer <token>headerAuthorization: Token <token>headerX-API-Keyheader- Query parameter fallback
Role Hierarchy
admin (4) > editor (3) > viewer (2) > guest (1)
A higher role satisfies any lower requirement.
from evoid.core.extend import before
# Wire authenticate to routes — role check happens in your provider
before("DELETE:/users", "authenticate")
before("GET:/reports", "authenticate")
# Your provider decides what role is needed per route:
async def my_auth(token: str) -> dict:
user = await db.find_by_token(token)
return {"user": user.name, "role": user.role}
Configuration
TOML
[engines]
auth = "auth"
Python
from evoid_auth import register_provider
from evoid.core.extend import before
# Register multiple providers
register_provider("jwt", jwt_auth_fn)
register_provider("api_key", api_key_auth_fn)
# Wire to pipeline — authenticate uses the default provider
before("GET:/users", "authenticate")
API
register_handlers()
Register auth as Intent handlers. No parameters needed.
Provider Registration
| Function | Signature | Description |
|---|---|---|
register_provider |
register_provider(name, fn) |
Register an auth provider |
resolve_provider |
resolve_provider(name) |
Get provider by name |
list_providers |
list_providers() |
List all registered names |
Processors
| Processor | Description |
|---|---|
authenticate |
Extracts token, calls provider, sets ctx.state |
authorize |
Checks role against requirement |
Provider Signature
async def my_provider(token: str) -> dict:
"""Must return dict with at least 'role' key."""
return {"user": "alice", "role": "admin"}
Dependencies
evoid>=0.4.0
Optional Dependencies
pyjwt>=2.8.0— for JWT decoding in your provider
Links
License
MIT
Metadata
Release files for evoid-auth 0.2.0
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 |
|---|---|---|---|---|
| evoid_auth-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for evoid_auth-0.2.0-py3-none-any.whl |
Release files / evoid_auth-0.2.0-py3-none-any.whl
| Download URL | evoid_auth-0.2.0-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
32321fe1867f4a32709a454055fd7abc6e5549e718a4aecfceebf958e4b7ab0c
|
|
BLAKE2b-256 checksum How to use checksums |
453aea951617e65540e8b9e3f515b74bdbdcb089a50118374fbbdb4bb6127e54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.3 {"installer":{"name":"uv","version":"0.12.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for evoid-auth 0.2.0
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.