leap-oauth-sdk
Business-side SDK for services that accept access tokens issued by Leap Auth, an OAuth 2.1 authorization server. It verifies tokens locally against the server's JWKS and reports every failure as one of four error categories, so each service handles retries, re-login and permission errors the same way.
Status: alpha. This release contains access token verification, the server side of browser
sign-in (code exchange, refresh, online session check, logout), encrypted cookie sessions,
leap-sso.js (the matching browser module), principal lookup for admin pickers and admin
member rules.
Install
uv add leap-oauth-sdk
Python 3.12 or newer.
Verify an access token
Create one verifier per process and reuse it, so the JWKS cache is shared by all requests.
from leap_oauth_sdk import AccessTokenVerifier, LeapAuthConfig, OAuthSDKError
verifier = AccessTokenVerifier(
LeapAuthConfig(
issuer="https://auth.example.com", # must equal the token's iss claim exactly
audience="example-service", # this service's own audience
)
)
async def current_subject(bearer_token: str) -> str:
try:
context = await verifier.verify_async(bearer_token)
except OAuthSDKError as exc:
# exc.status is the suggested local HTTP status; exc.code is stable for logs.
raise HTTPException(status_code=exc.status, detail={"error": exc.code})
return context.subject_id
verify() is the blocking variant. Both share the same cache.
The SDK does not read environment variables and has no default hosts. Load settings in your
own configuration layer and pass them to LeapAuthConfig.
Browser sign-in
One browser client is registered per service and environment. The browser runs authorization code + PKCE with a top-level redirect; your backend exchanges the code. Tokens never appear in URLs. Two ways to hold credentials:
- bearer: the page keeps the access and refresh token in
sessionStorageand sendsAuthorization: Bearer. Your API verifies withcheck_session(). - cookie: the backend keeps both tokens in an encrypted HttpOnly cookie and the page never
sees them. Use
CookieSessionManager.
from leap_oauth_sdk import BrowserClientConfig, BrowserSSO, LeapAuthConfig, OAuthSDKError
sso = BrowserSSO(
LeapAuthConfig(issuer="https://auth.example.com", audience="example-service"),
BrowserClientConfig(
client_id="web-example",
redirect_uri="https://app.example.com/auth/callback", # exact registered callback
resource="https://app.example.com/",
),
)
Serve these routes under one base path (bearer mode shown). On OAuthSDKError every route
responds with exc.status, exc.headers and the body exc.to_dict():
| Route | Handler |
|---|---|
GET {base}/config |
sso.browser_config() |
POST {base}/exchange {code, code_verifier} |
sso.exchange_code(...).to_browser_payload() |
POST {base}/refresh {refresh_token} |
sso.refresh(...).to_browser_payload() |
POST {base}/logout {scope} + Bearer |
sso.logout(token, scope) |
Protected API routes call sso.check_session(bearer_token) on every request and must not
cache the result, so that signing out in one service takes effect everywhere on the next
request; pass verified= when the same token was already verified locally. An already-ended
sign-in counts as a successful logout.
Browser module
leap-sso.js ships inside the package; leap_oauth_sdk.static_dir() returns its directory.
<script src="/static/leap-sso.js"></script>
<script>
const sso = LeapSSO.create({
endpointBase: "/api/auth/browser",
credentialMode: "bearer", // or "cookie"
storagePrefix: "example.admin", // sessionStorage keys; storageKeys can keep old names
defaultNext: "/admin",
hooks: {
onLoading: () => showSpinner(),
onLogin: (message, retryable) => showSignIn(message, retryable),
onForbidden: () => showNoAccess(),
},
});
const state = await sso.boot(); // "ready" | "redirecting" | "login" | "forbidden" | "disabled"
if (state === "ready") render(await (await sso.fetch("/api/me")).json());
signInButton.onclick = () => sso.login();
signOutButton.onclick = () => sso.logout().catch(showRetry);
</script>
boot()finishes a callback, restores the deep link, or starts one automatic sign-in that only reuses an existing sign-in. Every page load makes at most one automatic attempt; a failed callback shows sign-in instead of looping.fetch()adds the bearer token and refreshes 60 seconds before expiry, one refresh at a time. A 401 drops local credentials and makes the one automatic attempt; 403 and other statuses are returned to you untouched.- A duplicated tab copies
sessionStorageand with it a refresh token the other tab may already have spent. The server then answersrefresh_rotation_in_progress; the module drops the copy and signs in again through SSO instead of replaying it. In cookie mode the same answer comes from two replicas refreshing at once, so the request is retried briefly. logout()sendsscope=browser, which ends the sign-in for every service in this browser. Credentials are cleared only when the backend confirms; the next page load shows sign-in once.- Messages default to Chinese; pass
messagesto override.
Cookie sessions
from leap_oauth_sdk import CookieCipher, CookieSessionManager
cookies = CookieSessionManager(sso, CookieCipher(secret)) # secret: 32+ characters
# callback: value = cookies.issue(sso.exchange_code(code, verifier), extra={"csrf": csrf})
# per request:
result = cookies.resolve(request.cookies.get("example_session"))
if result.cookie is not None: # refreshed or migrated: write it back
response.set_cookie(
"example_session", result.cookie, max_age=cookies.max_age(result.session),
httponly=True, secure=True, samesite="lax",
)
# logout: cookies.logout(value), then delete the cookie
resolve() refreshes shortly before expiry and checks the sign-in online. Requests carrying
the same old cookie share one refresh within the process, and the result is reused for ten
seconds so a late request never replays the spent refresh token. CookieCipher accepts
previous_secrets for rotation and a context string; legacy_loader lets a service read its
old cookie format once and rewrite it.
Principal lookup
Admin pages pick people through the authorization server instead of typing subject ids.
PrincipalDirectory uses a service lookup credential, never the admin's own token.
from leap_oauth_sdk import PrincipalCandidate, PrincipalDirectory
directory = PrincipalDirectory(config, lookup_token=lookup_token)
result = directory.search("ann") # principals plus directory users; < 2 chars → empty
rows = [c.to_dict() for c in result.candidates] # send to the page; the page posts one back
picked = PrincipalCandidate.from_dict(posted) # untrusted: only ids are kept
accepted = directory.canonicalize([picked, "usr_existing"])
canonicalize()binds directory users to principals, follows aliases to the canonical subject and requires active principals ofallowed_principal_types(defaulthuman). It is all or nothing: any rejected pick raisesPrincipalSelectionError(422) whoserejectedmaps each pick to a reason, and nothing is accepted.validate()returns status and profile per subject in batches of 100, for listing.- A rejected lookup credential is reported as
InvalidResponse, notReauthRequired: it is a configuration problem, and the admin must not be sent to sign in again. api_base_urlpoints lookups at an internal address of the authorization server.
Admin members
MemberService applies the same rules in every service; storage stays in the service.
from leap_oauth_sdk import JsonFileMemberStore, MemberPolicy, MemberService
members = MemberService(
MemberPolicy(owners=frozenset({owner_subject})), # owners come only from configuration
JsonFileMemberStore("/data/admins.json"), # or your own MemberStore
directory, # None: list and remove only
)
members.role_for(subject) # "owner" | "member" | None, read on every call
snapshot = members.list() # profiles from validate(); degrades when it fails
version = members.add(actor, [picked], expected_version=snapshot.version)
members.remove(actor, subject, expected_version=version)
- Only owners add or remove members, owners cannot be removed, and owners in a selection are
ignored. Every write carries the version the admin saw; a concurrent change raises
MemberErrormember_version_conflict(409) instead of overwriting. MemberStorehas two methods,load()andapply(change, expected_version=);applymust persist the change and itsMemberChangeaudit record atomically.JsonFileMemberStoreis a reference implementation for a single replica on a persistent volume.MemberErrorhas the sameto_dict()shape as the SDK errors. Messages are English; mapcodeto your own wording.
Verification rules
- Signature algorithm must be in
allowed_algorithms(defaultEdDSAonly); the token must carry akidthat exists in the JWKS. - Registered claims
exp,iat,nbf,iss,sub,aud,jtiare required;audmust be a single string equal toaudience;issmust equalissuer. vermust equaltoken_version;statusmust beactive;source.channelmust be present;purposemust be inallowed_purposes(a token withoutpurposecounts asaccess).- The JWKS is cached for
jwks_cache_seconds(300). An unknownkidforces at most one refetch perjwks_refresh_cooldown_seconds(10). A failed or malformed fetch is never cached, never falls back to expired keys and is not retried within the same cooldown. Redirects are not followed.
Business authorization (roles, resources, fields, actions) stays in your service. A verified token only proves who the caller is.
Error categories
| Exception | Status | Meaning | What to do |
|---|---|---|---|
Retryable |
503 | Authorization server or JWKS unavailable, timeout, 5xx or 429, temporarily_unavailable (including refresh_rotation_in_progress) |
Keep credentials, retry later |
ReauthRequired |
401 | Token invalid, expired, revoked or unknown key; upstream 401 or invalid_grant; sign-in no longer active |
Clear credentials, sign in again |
Forbidden |
403 | Principal inactive, token purpose not accepted, upstream 403 | Show a permission error, do not re-login |
InvalidResponse |
502 | Malformed upstream response, redirect, invalid_client, token not bound to a browser sign-in |
Alert; do not loop sign-in |
All four inherit from OAuthSDKError and expose code, message, status and retryable;
to_dict() and headers (Retry-After when retryable) build your error response. Messages
never include tokens or upstream response bodies.
Development
uv sync --extra dev
bash scripts/check.sh # also runs the browser module tests (Node 20+)
License
MIT
Metadata
Release files for leap-oauth-sdk 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 | Provenance | |
|---|---|---|---|---|
| leap_oauth_sdk-0.2.0.tar.gz | 31.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| leap_oauth_sdk-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 69.2 kB
Release files / leap_oauth_sdk-0.2.0.tar.gz
| Download URL | leap_oauth_sdk-0.2.0.tar.gz |
|---|---|
| Size | 31.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
86903f83b83bfa6798649543fd8c7dd31a4567b2d7d9f459fc59653c270e238b
|
|
BLAKE2b-256 checksum How to use checksums |
1100f318c10e8607d1b5fe15c9864eb85b63757837ce301d4886dc5a22f31241
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 16, 2026.
Transparency logRelease files / leap_oauth_sdk-0.2.0-py3-none-any.whl
| Download URL | leap_oauth_sdk-0.2.0-py3-none-any.whl |
|---|---|
| Size | 37.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd3d674b65098c75595b7e635f76a7865e696e8fd239133b92de81dcc081aae0
|
|
BLAKE2b-256 checksum How to use checksums |
c83518ecbc97c0d349ad833b00d4423d001a342579f9ff77ca77af01c6fd1542
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Oct 16, 2026.
Transparency logSecurity for leap-oauth-sdk 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for leap_oauth_sdk-0.2.0.tar.gz
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 Oct 16, 2026.
Transparency logA 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.