Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration steps for the Zoom API no longer possible due to Zoom API deprecation of JWT #116028

Closed
v-johanpo opened this issue Oct 16, 2023 · 6 comments

Comments

@v-johanpo
Copy link

Hello, this solution/documentation requires an update as Zoom API JSON Web Tokens (JWT) has been deprecated since (Sept 08, 2023) making the 'step 1' of the guide no longer possible thus this solution will not work in the current spec.

Zoom API now requires Server-to-Server OAuth or OAuth apps to replace the functionality (Server-to-Server OAuth app type is only for internal applications and processes. All apps created for third-party usage must be OAuth app types.)


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@cwatson-cat
Copy link
Contributor

@prtanej Can you please take a look at this issue with the install guidance for Zoom Reports?

@Naveenommi-MSFT
Copy link
Contributor

@v-johanpo
Thank you for bringing this to our attention.
I've delegated this to content author @prtanej, who will review it and offer their insightful opinions.

@prtanej
Copy link
Contributor

prtanej commented Oct 17, 2023

Being cognizant of the JWT being deprecated, we are in process of changing the authorization process. The documentation update will follow when the update is pushed.

Thanks.

@batamig
Copy link
Contributor

batamig commented Jan 28, 2024

#label:"backlog-item-created"

@batamig
Copy link
Contributor

batamig commented Jul 7, 2024

#label:"automated-data-connectors"

@batamig
Copy link
Contributor

batamig commented Jul 8, 2024

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants