Fixes a sign-in loop after OAuth sign-in
WAVE fixes two bugs that caused some users to loop back to the sign-in screen after completing OAuth sign-in. Sign-in now completes on the first try.
What's new across WAVE, at the platform, workstream, and product level. Shipping in the open.
Filtered by tag auth · clear
WAVE fixes two bugs that caused some users to loop back to the sign-in screen after completing OAuth sign-in. Sign-in now completes on the first try.
When a request fails authentication, WAVE's response now points to the document describing how to authenticate. Agents no longer need prior knowledge of our auth flow.
WAVE's authorization-server metadata document now serves our actual configuration instead of redirecting, so agents can discover our auth setup in one call.
A key minted through the console can now authenticate on every route. Previously every request with a freshly minted key returned an authorization error.
A request to a Zoom route without credentials now returns 401 with the typed error body instead of a payment challenge. Organization resolution on those routes no longer fails on edge cases.
Run wave login to authenticate through a browser device flow, then use wave whoami and wave logout to check or end your session.
The live MoQ relay requires authenticated join tokens and isolates each organization's namespace, so only authorized participants can join a stream.
Dated, versioned changes to the API and SDKs live at changelog.wave.online.