Zoom meeting

I made a short video to show how to set up Server-to-Server OAuth on Zoom market place.

Hi Venky S,
It looks like you have not granted the "report:read:admin" scope to your Server-to-Server OAuth app. Try adding the scope, clearing the Zoom cache and running the report again.
Hi Sergio Luciano,
1. It is not possible to register a separate Zoom account in the plugin. It may be too late, but you may want to use separate Moodles if the audiences are separate.
2. To modify the plugin, you may be able to find and replace most instances of "zoom" with "zoom2". The only exceptions would be the zoom.us URLs (specifically for the API and OAuth endpoints).

I want to have a second account registered with the plugin, because I have two companies working at Moodle, and they have different accounts. Two questions:
1. Is it possible to register a second zoom account in the plugin?
2. If not, is it possible to make small changes in the plugin to have a second one, with different name, to allow the teaches choose which one to use?

HI Jonathan,
Firstly a big thanks for the app which has made our lives so much easier.
In continuation to your reply to Francesco De Stefano above, I am also facing the problem of not getting the session reports. I have a single zoom pro account. When I try to run the get session report, I get this error:
Get meeting report from Zoom
Finding meetings between 2023-08-24 to 2023-08-27
Querying $hostuuids; need to use Report API
Using Reports API
Hostuuids passed
Processing 1 active host uuids
Getting meetings for host uuid 0aIdgQP1S9WLzo-8bXfZkA
!!! Zoom received a bad request: Invalid access token, does not contain scopes: [report:read:admin]. !!!
!!
Error code: errorwebservice_badrequest !!
!! Stack trace: * line 299 of /mod/zoom/classes/webservice.php: zoom_bad_request_exception thrown
* line 374 of /mod/zoom/classes/webservice.php: call to mod_zoom_webservice->make_call()
* line 850 of /mod/zoom/classes/webservice.php: call to mod_zoom_webservice->make_paginated_call()
* line 332 of /mod/zoom/classes/task/get_meeting_reports.php: call to mod_zoom_webservice->get_user_report()
* line 139 of /mod/zoom/classes/task/get_meeting_reports.php: call to mod_zoom\task\get_meeting_reports->get_meetings_via_reports()
* line 81 of /mod/zoom/cli/get_meeting_report.php: call to mod_zoom\task\get_meeting_reports->execute()
!!
Can you kindly let us know where the issue lies ?

Jonathan, you're a gem. Thanks a boat load!
Turns out our Zoom admin didn't give the developers sufficient access to Zoom. Just enough to create the S2S OAuth app, but not enough for it to... work. We made him remake the app, and everything works like a charm now.

Hi Francesco De Stefano,
Is this a single Zoom Pro/Licensed account or do you have an Education/Business/Enterprise account that includes access to the Dashboard? If you have Dashboard access, the dashboard_meetings:read:admin permission is much more efficient than the report:read:admin permission, which is used to get the session report data. Also, we don't ask for or use the recording:write:admin permission, so I would recommend removing it as a principle of least privilege.
Hi Peter Carpenter,
I would guess that the S2S OAuth app creator did not create it as a Zoom admin within your enterprise. To check, ask a Zoom administrator (to be safe, someone other than the app creator) to go to your Zoom Marketplace's list of account-created apps: https://marketplace.zoom.us/user/dashboard/created-apps Then, find the app the user created. It should say "Account Level" and "Server-to-Server OAuth". If it's not in the list or doesn't have those two tags/labels on the app, then that could be the problem. If everyone looks correct, you may want to try having a different Zoom administrator recreate the S2S app, in case that the existing one is not in a correctable state. Please let us know how it goes!

Hey Jonathan / team!
Because you were very succinctly helpful last time, mind if I bother you folks for one more small thing? We're at a loss on where to look.
We've set up the (S2S) OAuth app properly, and got the credentials passed into the plugin, which then reports that the connection was successful... but only for the person who created the S2S OAuth app. Other Moodle Admins will report that it changes to a No Permission error when they view the same page. Likewise, users cannot create Zoom meetings, only the app creator can. On the user side, it spits out an error saying that the user needs to log in first, which doesn't work. Is there a permission setting somewhere that we're not aware of? Very likely this is out of scope for the plugin, and if that's the case then absolutely disregard all of this, but we're grasping at straws, and are not sure where we misconfigured things.

I updated the plugin to the last versione 5.0.
In this version it isn't possible to view the session report.
I set the Server-to-Server OAuth in App Marketplace of my zoom account.
I put theese SCOPES:
Meeting
meeting:read:admin, meeting:write:admin
Recording
recording:write:admin, recording:read:admin
User
user:write:admin, user:read:admin
Report
report:read:admin
It isn't possible to see the session report in the zoom meeting that I create inside zoom application.
In the old version it was possible to see.
How can I do?

Hi Jonathan,
We have not yet been able to make it work, the same situation as in the previous post that we have published.

Aww, Peter, it's totally fine. We're all in this together. I'm glad you were able to get it working.

Hey Jonathan!
Thank you. you are correct, and I am a sausage. OAuth and Server to Server OAuth are different things.

Hi Peter Carpenter,
If the Zoom app form is asking for Redirect URL, it's not the Server-to-Server OAuth app. Please make sure your Zoom account has access to the Server-to-Server OAuth app type so that you can create the correct app.

Gosh, the instructions for S2S OAuth app are bare bones, aren't they?
I can't for the life of me figure out what to put in the Redirect URL. I've tried the standard https://moodle.mydomain.ca/admin/oauth2callback.php, but that only generates an error that a GET parameter of "state" is missing. The instructions don't even mention that this field exists. Very frustrating.

We have been using this plugin and it really works great, thanks for a great job!
But after upgrading to the latest version we couldn't connect it anymore. We thought it was because we used JWT.
So, we create the Oauth S2S app
After completing the credentials using Oauth S2S we get the following error
Connection status: Connection failed: HTTP Status 403
Changing Zoom API Identifier from email address to username we have this status
Connection status: Connection working
But in this case we get this message when trying to create rooms
Unable to find your account on Zoom. If you are using Zoom for the first time, you must activate your Zoom account by logging into https zoom us. Once you've activated your Zoom account, reload this page and continue setting up your meeting. Else make sure your email on Zoom matches your email on this system.
Any idea where we might be going wrong?
Moodle version 4.1+ (Build: 20221222) (2022112800.05) PHP Version 8.0.29
Regards

Thanks for responding so quickly Jonathan - really appreciated. Your guess was correct - it was a version issue as we are on 4.9 - and the problem has apparently resolved itself so it must have been the caching issue.
PS: Plugin is great !