`gj26dZddlmZddlmZmZddlmZddlm Z edGdd Z edGd d Z edGd d Z Gdde ZGdde ZGdde ZGdde ZGddeZddZy)zFAbstract base + dataclasses + exceptions for dashboard auth providers.) annotations)ABCabstractmethod) dataclass)OptionalT)frozencbeZdZUdZded<ded<ded<ded<ded<ded <ded <ded <y ) Sessionu A verified identity. Returned by ``complete_login`` and ``verify_session``. All fields are mandatory. Providers that don't have a concept of orgs should set ``org_id`` to an empty string. ``access_token`` and ``refresh_token`` are opaque to Hermes — provider-specific. struser_idemail display_nameorg_idproviderint expires_at access_token refresh_tokenN__name__ __module__ __qualname____doc____annotations__Q/root/.hermes/venv/lib/python3.12/site-packages/hermes_cli/dashboard_auth/base.pyr r s4L J KMOrr c4eZdZUdZded<ded<dZded<y) TokenPrincipalu4A verified non-interactive (service-to-service) caller. The token analog of :class:`Session`. Where a ``Session`` represents an interactive human identity behind a session cookie, a ``TokenPrincipal`` represents a machine/service caller that authenticated by presenting a bearer token in the ``Authorization`` request header on a single request — no login, no cookie, no refresh. Returned by :meth:`DashboardAuthProvider.verify_token` and attached to ``request.state.token_principal`` by the token-auth middleware seam so a route handler can see *who* called it. Fields: * ``principal`` — stable identifier for the caller (e.g. the provider name, a service account id, or an agent id). Opaque to the seam. * ``provider`` — the ``name`` of the provider that verified the token. * ``scopes`` — capability strings this principal is authorised for. Empty tuple means "unscoped" (the provider vouches for the caller but attaches no capability list); a route MAY enforce a required scope. r principalrrztuple[str, ...]scopesN)rrrrrr!rrrrrs*NM FO rrc&eZdZUdZded<ded<y) LoginStartuFirst leg of the OAuth round trip. ``redirect_url`` is the URL the browser must navigate to (e.g. the Portal's ``/oauth/authorize``). ``cookie_payload`` is a dict of cookie name → serialised value that the auth route will ``Set-Cookie`` on the response. Used for PKCE state, CSRF nonces, etc. Cookies set here MUST be HttpOnly + Secure (when over HTTPS) + SameSite=Lax with a TTL ≤ 10 minutes (the login lifetime). r redirect_urlzdict[str, str]cookie_payloadNrrrrr#r#8s""rr#ceZdZdZy) ProviderErrorzmIDP unreachable, network error, or other transient failure. Middleware translates this to HTTP 503. Nrrrrrrrr'r'Hrr'ceZdZdZy)InvalidCodeErrorzlThe OAuth callback ``code`` / ``state`` failed validation. Middleware translates this to HTTP 400. Nr(rrrr+r+Or)rr+ceZdZdZy)InvalidCredentialsErrorafA username/password pair was rejected by a password provider. Raised by :meth:`DashboardAuthProvider.complete_password_login`. The ``/auth/password-login`` route translates this to HTTP 401 with a deliberately generic detail (never distinguishing "unknown user" from "wrong password") so the endpoint can't be used as a username oracle. Nr(rrrr-r-Vsrr-ceZdZdZy)RefreshExpiredErroraThis provider rejects the refresh token as dead or invalid. In a multi-provider deployment this does not prove token ownership, so middleware may try remaining providers. It clears cookies and forces re-login only after every reachable provider rejects the token. Nr(rrrr/r/`srr/ceZdZUdZdZded<dZded<dZded<dZded <d Z ded <e dd Z e dd Z e ddZ e ddZe ddZ ddZddZy)DashboardAuthProvideruc Protocol every dashboard-auth provider plugin implements. Lifecycle: 1. ``start_login`` — user clicks "Log in with X" on the login page. Provider returns a redirect URL and any PKCE/CSRF state to stash in short-lived cookies. 2. Browser bounces through the OAuth IDP and lands at /auth/callback. 3. ``complete_login`` — exchange the code + verifier for a Session. 4. ``verify_session`` — called on every request to validate the access token in the cookie. Returns ``None`` if the token is expired or invalid (middleware then triggers refresh or logout). 5. ``refresh_session`` — called when the access token is near expiry. Returns a new Session with rotated tokens. 6. ``revoke_session`` — called on /auth/logout. Best-effort. Failure semantics: * ``start_login`` may raise ``ProviderError`` if the IDP is unreachable. * ``complete_login`` raises ``InvalidCodeError`` on bad code/state; ``ProviderError`` if the IDP is unreachable. * ``verify_session`` returns ``None`` on expiry / unknown token; raises ``ProviderError`` if the IDP is unreachable. Middleware treats expiry and unreachable differently (expiry → refresh; unreachable → 503). * ``refresh_session`` raises ``RefreshExpiredError`` when the refresh token is invalid for that provider. Middleware tries the remaining providers because an opaque foreign token can be indistinguishable from an expired one; it forces re-login only after every reachable provider rejects the token. Raises ``ProviderError`` on network failure; middleware still tries remaining providers, but returns 503 without clearing cookies if none succeeds and any was unavailable. * ``revoke_session`` is best-effort and must not raise. Subclasses MUST set ``name`` (lowercase identifier, stable forever) and ``display_name`` (user-facing label on the login page). Password (non-redirect) providers: A provider that authenticates with a username + password instead of an OAuth redirect sets ``supports_password = True`` and implements ``complete_password_login``. The login page then renders a credential form (POSTing to ``/auth/password-login``) instead of a "Log in with X" redirect button. Everything downstream of login — ``verify_session`` / ``refresh_session`` / ``revoke_session``, the session cookies, the WS-ticket mint — is identical to the OAuth path, because a password session is just a :class:`Session` with provider-minted opaque tokens. The OAuth methods (``start_login`` / ``complete_login``) remain abstract; a pure-password provider that will never be reached via the redirect flow may implement them as stubs that raise ``NotImplementedError``. r namerFboolsupports_passwordsupports_tokenTsupports_sessioncyNr)self redirect_uris r start_loginz!DashboardAuthProvider.start_logins?Brcyr9r)r:codestate code_verifierr;s rcomplete_loginz$DashboardAuthProvider.complete_loginsrcyr9r)r:rs rverify_sessionz$DashboardAuthProvider.verify_sessionsILrcyr9rr:rs rrefresh_sessionz%DashboardAuthProvider.refresh_sessionsADrcyr9rrEs rrevoke_sessionz$DashboardAuthProvider.revoke_sessions=@rcDtt|jd)u$Verify a username/password pair and mint a :class:`Session`. Only called when ``supports_password`` is True (the ``/auth/password-login`` route guards on the flag). The default raises ``NotImplementedError`` so an OAuth-only provider that forgets to set the flag fails loudly rather than silently accepting credentials. The returned ``Session`` carries provider-minted opaque ``access_token`` / ``refresh_token`` exactly like the OAuth path, so all downstream session handling (cookies, verify, refresh, ws-tickets, logout) is identical. Failure semantics: * ``InvalidCredentialsError`` — username/password rejected. The route surfaces a generic 401 (no user-vs-password distinction). Implementations SHOULD spend constant time on unknown users (dummy hash verify) to avoid a timing oracle. * ``ProviderError`` — the backing credential store is unreachable (LDAP/DB down); the route surfaces 503. zd does not support password login (set supports_password = True and override complete_password_login)NotImplementedErrortyper)r:usernamepasswords rcomplete_password_loginz-DashboardAuthProvider.complete_password_logins+0"Dz""#$' '  rcDtt|jd)uVerify a non-interactive bearer token; return its principal. The token analog of ``verify_session``. Only consulted when ``supports_token`` is True. Called by the ``token_auth`` middleware seam for every request to a token-authable route, in registration order, until one provider returns a non-None principal. Contract (mirrors ``verify_session`` stacking semantics): * Return a :class:`TokenPrincipal` if this provider recognises and accepts the token. * Return ``None`` for a token this provider does NOT recognise — never raise, so the seam can fall through to the next provider. A malformed/expired/wrong token is "not recognised" → ``None``. * Raise ``ProviderError`` ONLY for a genuine backing-store outage (the provider can neither confirm nor deny). The seam treats this like ``verify_session``: remember it, keep trying other providers, and surface 503 only if NO provider accepts the token AND at least one was unreachable. Implementations MUST use a constant-time comparison (``hmac.compare_digest``) when matching a shared secret so the endpoint isn't a timing oracle. The default raises ``NotImplementedError`` so a provider that sets ``supports_token`` but forgets to implement this fails loudly rather than silently accepting every caller. zR does not support token auth (set supports_token = True and override verify_token)rJ)r:tokens r verify_tokenz"DashboardAuthProvider.verify_tokens-8"Dz""#$D D  rN)r;r returnr#) r>r r?r r@r r;r rSr )rr rSzOptional[Session])rr rSr )rr rSNone)rMr rNr rSz 'Session')rQr rSz'Optional[TokenPrincipal]')rrrrr3rrr5r6r7rr<rArCrFrHrOrRrrrr1r1is1fD#NL#$t#!ND "d!BB      LLDD@@  *-  < rr1cNd}d}|D]+}t||d}|rt|jd||D]2}tt||drt|jd|t|ddr-t|jdt |j y) a+Raise ``TypeError`` if ``cls`` doesn't fully implement the provider protocol. Call this in every provider plugin's unit tests:: def test_protocol_compliance(): assert_protocol_compliance(MyProvider) Returns ``None`` on success so callers can assert it explicitly. )r<rArCrFrH)r3rr2z missing or empty attribute: Nz missing method: __abstractmethods__z% has unimplemented abstract methods: )getattr TypeErrorrcallablesortedrV)clsrequired_methodsrequired_attrsattrvalmethods rassert_protocol_complianceras.Nc4$<<. =dXF  #HVT23s||n,=fXFG GHs)40||nAc--./ 1  1rN)r[rLrSrT)r __future__rabcrr dataclassesrtypingrr rr# Exceptionr'r+r-r/r1rarrrrgsL"#! $$ $!!!6 $ # # #Iyi)e Ce P! r