Documentation

Password protecting meeting join links in this module's tests.

Kicking a member from a meeting conversation must emit a meeting.delete event targeted at the removed member so their clients drop the meeting view. Remaining members must not receive it.

Helper to extract meetingId and domain from a meeting JSON object

On create/update responses, the full conversation object is returned alongside the legacy qualified_conversation field. This asserts that both refer to the same conversation.

Assert a meeting lifecycle notification carries the meeting's qualified id flat at payload.0.qualified_id and has NO "data" wrapper (proves the no-nesting contract).

Helper to create a default new meeting JSON object

Legacy (V15/V16) meeting JSON: carries end_time and no tzid (V17 adds tzid). Used to exercise the legacy endpoints in interop tests.

Create a meeting with default times relative to now (starts in one hour, one hour long, no invitees, title "Team Standup") and return the 201 body.

Read endpoints (GET meetingslist, GET meetings{domain}/{id}) treat a team with the meetings feature disabled as "no meetings" (list -> 200 [], get -> 404 meeting-not-found) instead of 403 invalid-op, while write endpoints (POST /meetings) keep the hard gate and still return 403 invalid-op. See WPB-27329.

WPB-28272: PUT meetings{domain}/{id} accepts an optional tzid and updates the stored time zone; omitting it (as legacy clients do) keeps the stored value; an invalid tzid is rejected at decode time.

WPB-27907: meeting lifecycle events are delivered to all conversation members; only the originating client connection is excluded (no redundant echo), while the initiator's other client connections and all other members receive them. This test covers the non-initiator member path: a member who joined the meeting conversation after creation receives 'meeting.update' and 'meeting.delete'. The originating-client-connection exclusion is covered in testMeetingOriginatingConnectionExcluded; the multi-member recipient set is covered at the unit level in Wire.MeetingsSubsystem.InterpreterSpec.

A meeting created via the V19 shape (end_time + tzid + type) is visible to legacy clients (< V17) with an end_time; V19 reads carry end_time too.

A meeting created via the legacy shape (end_time) is visible to V19 clients with end_time and the injected default tzid (Europe/Berlin).

The V19 meeting object exposes a type field (immediate or scheduled); type is required on create and not updatable.

WPB-29361: the V19 meeting object always exposes a link join link carrying the meeting's join code as key/code query parameters. Creating a meeting in a mode that cannot produce a link (cassandra-only code store, or no join-link URI configured for the domain) fails with 500 link-unavailable. Legacy endpoint shapes (V16/V18) never carry link.

WPB-29361: in multi-ingress mode a meeting created by a user whose domain has no configured join-link URI cannot get a link, so creation fails closed with 500 link-unavailable (the old fallback would have fabricated one). Holds regardless of code-storage mode.

A meeting created via the V18 shape (no type) is readable via V19 and carries the stored default type scheduled.

WPB-28216: refreshing a meeting's join link recreates the join code (rotating the code embedded in the link URL), revokes the meeting conversation's guest link, and enforces creator-only access.

Run the dynamic backend with a licence whose meetings flags are the given triple (invitation_links, emails_sending, calendars_integration): the CLI's example payload is patched with the requested flags, so tests can exercise flag combinations independently (e.g. join links licensed while email sending is off). Also exposes the backend resource (e.g. for execSql, which needs the backend's Postgres dbname).

Licensed backend with all meetings flags enabled.

As withLicensedBackendFlags, but also exposes the backend resource (e.g. for execSql, which needs the backend's Postgres dbname).

Run the body against a dynamic backend whose galley is licensed with the given meetings flags.

Produce a base64url licence payload from the licensing CLI's example, with the three meetings flags overwritten by the given triple.

Extract the (key, code) query parameters from a meeting join link URL (…meeting-join?key=<key>&code=<code>&domain=…). The URL contains exactly one ? and the three known parameters; missing parts yield "".

WPB-28216: POST meeting{domain}{key}{code}/join joins a meeting through its join link for any authenticated local user (re-joining is an idempotent no-op) and enforces the optional password. The code value is the rotating capability: stale values (superseded by a refresh) yield 404.

WPB-28989: GET meeting{domain}{key}{code}/code-check checks a meeting join link unauthenticated (metadata only) and POST meeting{domain}{key}{code}/join joins the meeting's conversation. No creator or conversation membership is required; password-protected links require the matching password on both verbs.

A temporary guest (brig ephemeral account created via the anonymous POST /register flow, what the webapp's "Join as Temporary Guest" uses) can resolve a meeting join link and join the meeting conversation without being a team member. Refreshing the link rotates the code so the stale value stops working, while an already-joined guest keeps their membership.

Access-role updates on meeting conversations are rejected: the roles are owned by the meetings subsystem (the stored GuestAccessRole is what lets temporary guests join, see WPB-27191), and a client rewrite via PUT /conversations/{cnv}/access would strip that role.

POST /meetings accepts an optional password that password-protects the join link/code at creation time; short passwords are rejected at decode time.

WPB-29643: on a deployment whose license does not cover invitation links (the default, unlicensed static backend), both join-by-link verbs return 403 id-feature-error before any link resolution. Meeting creation is NOT gated, and unknown keys do not leak a 404.