hawkapi-sso
Social SSO for HawkAPI. One plugin, six providers:
- Google (OAuth2 + OIDC, PKCE)
- GitHub (OAuth2)
- Microsoft / Entra (OAuth2 + OIDC, PKCE)
- Discord (OAuth2)
- Facebook (OAuth2 + Graph API)
- LinkedIn (OAuth2 + OIDC, PKCE)
Pure-Python, async, httpx-based. CSRF-protected via HMAC-signed state cookie. PKCE applied automatically where the provider supports it.
Install
pip install hawkapi-sso
Quickstart
from hawkapi import HawkAPI
from hawkapi_sso import GoogleProvider, GitHubProvider, init_sso
app = HawkAPI()
init_sso(
app,
providers={
"google": GoogleProvider(client_id="...", client_secret="..."),
"github": GitHubProvider(client_id="...", client_secret="..."),
},
state_secret="...", # ≥16 chars; stable across restarts
)
# These routes are mounted automatically:
# GET /auth/sso/login/{provider} → redirects to the provider's authorize URL
# GET /auth/sso/callback/{provider} → handles the OAuth callback, sets `request.scope["sso_user"]`,
# then redirects to `?next=` (or success_redirect).
Reading the authenticated user
The callback handler stashes a normalized OAuthUser on the request scope. Pick it up in your downstream middleware / handlers:
@app.middleware("http")
async def persist_session(request, call_next):
response = await call_next(request)
user = request.scope.get("sso_user")
if user is not None:
# persist user, set session cookie, etc.
...
return response
You can also wire a callback hook:
async def on_login(request, user, token):
# persist, mint JWT, etc.
...
cfg = init_sso(app, providers={...}, state_secret="...")
cfg.on_success = on_login
OAuthUser
@dataclass
class OAuthUser:
provider: str # "google" / "github" / ...
sub: str # provider-issued user id (always string)
email: str # "" if not granted
email_verified: bool # only True when the provider explicitly signals it
name: str
picture: str
raw: dict # the parsed userinfo response, for advanced use
Security
- State cookie —
HttpOnly,Secure(configurable),SameSite=Lax,Max-Age=600by default. Signed with HMAC-SHA256 over the state secret. - CSRF — the callback rejects requests whose
statequery parameter does not match the state cookie byte-for-byte. - PKCE — automatically generated and verified for Google, Microsoft, LinkedIn.
- Open-redirect guard —
?next=parameter must be a path (/...); anything else falls back tosuccess_redirect. client_secret— never logged, never returned in any URL or response.- Email verification —
email_verified=Trueis set only when the provider explicitly signals it (GitHub uses the/user/emailsendpoint). Facebook does not, so it defaults toFalse.
Configuration
init_sso(
app,
providers={...},
state_secret="...",
cookie_name="hawkapi_sso_state",
cookie_secure=True,
cookie_samesite="lax",
cookie_max_age=600,
login_path_prefix="/auth/sso",
success_redirect="/",
failure_redirect="/login?error=sso",
)
Development
git clone https://github.com/Hawk-API/hawkapi-sso.git
cd hawkapi-sso
uv sync --extra dev
uv run pytest -q
uv run ruff check . && uv run ruff format --check .
uv run pyright src/
License
MIT.
Metadata
Release files for hawkapi-sso 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hawkapi_sso-0.2.0.tar.gz | 42.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hawkapi_sso-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.9 kB
Release files / hawkapi_sso-0.2.0.tar.gz
| Download URL | hawkapi_sso-0.2.0.tar.gz |
|---|---|
| Size | 42.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b20cffc730f0a01b6019d827a96777cdc57bebbf7d1ad0e50a1e6e6ca9b09bf
|
|
BLAKE2b-256 checksum How to use checksums |
c345a376b8c9f5cd2b6231d633b9e606663865ceb796a120d40d7f063291f158
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 10, 2026.
Transparency logRelease files / hawkapi_sso-0.2.0-py3-none-any.whl
| Download URL | hawkapi_sso-0.2.0-py3-none-any.whl |
|---|---|
| Size | 22.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3888af72ab02f532f6cb7acbbcec7aabf42d1b94820f1316d020591204d147d5
|
|
BLAKE2b-256 checksum How to use checksums |
42bf0b5889883556b710556f6e8dde0fb140e3b5bf081080b9c0e4c5353b1598
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 10, 2026.
Transparency log