Skip to content

v0.36.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 18:56
· 35 commits to main since this release
Immutable release. Only release title and notes can be modified.
c02e10c

What changes in 0.36.0

0.36.0 gives an async host one call for a signed-in person's groups, fresh from the issuer at each call. Nothing a host uses today changes.

Per app

  • hopin: replace hopin.agent.session_groups.SessionGroups with webauth.session_groups.SessionGroups, and delete the copy with its test.
    • Pass the session transaction where the copy took the bare store: lambda: nullcontext(sessions).
    • The class has no session_id_of; call webauth.dependencies.session_id_from_request(connection, config) where the session id itself is needed.
  • skat: of_session(session_id) is the entry for a plain HTTP route. The store needs nothing beyond replace_refresh_token.
  • presentator, songmaker, speech-runtime: nothing to change beyond the pin, and no need to take this release for itself.

New

  • webauth.session_groups.SessionGroups(relying_party, session_transaction, config) (#711, PR #712; docs/host-contract.md, GROUPS-28 to GROUPS-30).
    • await of_session(session_id) and await of_connection(connection) answer the groups as a frozenset[str], or the AccessTokenRefusal that current_groups answers, by one current_groups call on a worker thread.
    • Fresh at each call. Each call is one refresh grant; nothing is cached.
    • No session, no grant. A connection without a session answers SIGN_IN_AGAIN and makes no grant.
    • A cancelled caller gets no answer, but its grant still stores its rotated refresh token. The cancellation reaches the caller after the grant ends, so a timeout around the call fires only then.
    • No lock. Overlapping calls of one session both succeed where the issuer lets a used refresh token be used again, and the last replacement written wins (GROUPS-25 to GROUPS-27). Where an issuer revokes a used refresh token, an overlapping call can answer SIGN_IN_AGAIN; serialising a session's grants is then the host's.
  • webauth.admission.app_role takes any Collection[str] of group paths, so the reader's frozenset passes to it as it is for a subgroup-aware check (GROUPS-12). A tuple or a list works as before.

Breaking

None. No migration.

Not visible to a host

  • A release is dispatched with the version alone and gated before its tag exists, through quality's shared release workflows (#593, PR #713). This release is the first one made that way.
  • The private worker helper moved to webauth/_worker.py.

Full Changelog: v0.35.0...v0.36.0