Signup, login and profile with the Python SDK (authorizer-py 0.3.0rc4) sync client, plus the admin client listing users.

git clone https://github.com/authorizerdev/authorizer.git
cd authorizer
make dev   # http://localhost:8080, admin secret: admin

python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
python main.py

Defaults match make dev; override with AUTHORIZER_URL, CLIENT_ID, ADMIN_SECRET env vars.

• The pip package is authorizer-py; the import is authorizer.
• The client supports three wire protocols: graphql (default), rest, and grpc (AuthorizerClient(..., protocol="grpc"); gRPC needs pip install 'authorizer-py[grpc]').
• Async variants exist for both clients: AsyncAuthorizerClient, AsyncAuthorizerAdminClient.
• Admin operations authenticate with the x-authorizer-admin-secret header, normally via AuthorizerAdminClient.

Since server 2.4.0 MFA is on by default, so signup/login withhold the access token and return Proceed to mfa setup; declining the offer with skip_mfa_setup is what releases it. That call is identified by the MFA session cookie, which the server marks Secure (--app-cookie-secure defaults to true) — httpx keeps it in its jar but will not replay it over plain http, so main.py reads it out of the jar and passes it by hand. A deployment on https needs none of that.