Adrian

The plugin uses "server oauth" (and that is indeed merged), NOT per-user oauth. So there are no redirect URLs etc involved....

[Server-to-server oauth](https://developers.zoom.us/docs/internal-apps/s2s-oauth/) does not use a redirect URL since there is no end user oauth flow. The plugin does NOT support user oauth, only server-to-server oauth.

This doesn't really fit well together in the schema of settings that are managed via the UI: They are all stored in the database and have UI where the user...

`DEFAULT_TIMEZONE` cannot be fully overridden in the UI; you can only set a different time zone for specific categories or events..

So I was thinking about this, and introducing individual env vars seems like a bit of a mess (especially considering data types - settings are stored as JSON after all!)....

Just to avoid any misunderstanding and both sides waiting for the other to add it: Are you willing to contribute this? It should be pretty straightforward and while the two...

Sure! Sounds like something for 3.2.1 or 3.2.2 then ;)

While implementing it would be possible, you'd need to keep this state around somewhere. And assuming that you use flask-multipass in Indico the problem is that everything there expects to...

Easier said than done - currently the ID token is not stored anywhere... :/

Sure, we can keep it open. Regarding the other point, when you do a SSO logout you usually want to log out everywhere. For *just* logging our from Indico you...