OAuth clients are managed from the Console
Registering, updating and revoking OAuth clients now happens in the Console, per environment. A client registered in staging still does not exist in production.
- Console
- OAuth server
Everything that changed on the surfaces you integrate against. Entries that require you to change something are marked; the rest you can read and move on.
Registering, updating and revoking OAuth clients now happens in the Console, per environment. A client registered in staging still does not exist in production.
Templates are listed by source, so you can find the message a given flow sends without reading the whole list.
The authentication endpoints moved from /auth/… to the root of the auth API. The paths are otherwise unchanged.
Action required
If you call the auth API directly rather than through an SDK, drop the /auth prefix from your request paths.
The Console shows what differs between two environments of a project: sign-in methods, multi-factor options, password rules, sudo actions, OAuth providers, delivery providers and bot protection. Promoting a change becomes a review rather than a guess.
Each environment keeps its own deployment history, with the steps a deployment went through and the logs it produced.
A function now opens on a summary of its invocations, errors and latency, rather than dropping you straight into configuration.
A deployment runs as ordered steps with their own state, so a failure names the step it failed at instead of returning a single opaque error.
Logs carry an id and can be filtered by field, and the Console lists the requests made by an individual user.
The permissions endpoints, fields and tables were renamed to grants throughout, and role fields were adjusted alongside them.
Action required
Update any call to the permissions endpoints, and any code reading permission fields from a response.
Apple, Discord, Facebook, LinkedIn and Twitch join the providers you can enable per environment.
You can add claims to the tokens issued for a project and see the resulting token before saving, rather than discovering the shape after the fact.
Privilege elevation now runs through a nonce flow, challenges count attempts, and signing out clears sudo state instead of leaving it to expire.
Administrative actions across an organization are recorded and readable in the Console.