Spike: Zoom API JWT vs OAuth

What

As suggested by @sengelhard this spike is intended to help us deciding whether to use Zoom's JWT (token per project) or OAuth (token per user) for our Zoom API integration.

Scope

This spike will implement (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31000) a tiny integration with Zoom API's using JWT keeping an eye on the possible use cases.

Conclusion: Use JWT

It's feasible to use Zoom's JWT authentication method and create meetings as different users who are tied to this very Zoom account.

The ongoing Zoom support request regarding enforcing users to be logged in should NOT amend this conclusion.

Use cases

Feel free to discuss the following use cases in individual discussion threads.

• THREAD Create an App and use its JWT credentials to create a Zoom meeting
• THREAD Schedule a (private) meeting for another user. See schedule_for parameter
• THREAD Make sure we can create meetings for users with multiple zoom accounts (with different Zoom domains)