Hi @elisa.zoom
I’ve been working on other projects and related components, and now I’m winding back to this.
I just retested everything.
· We get no webhook events from our General apps, unless we add individual users to the app.
· Adding users to a Group and then adding that Group to the app has no noticeable effect.
If you succeeded in sending webhook events through a Group membership assignment, then something must be different.
Highest probability scenarios:
· We are doing something different in the process of adding the User to the Group, and then adding the Group to the App.
· Something in our default user configuration is preventing app assignment, through Group membership, from working.
Is there a way to show the Zoom App settings (or any other relevant settings) in the user configuration that worked for you?
Thanks
How I tested:
Consumer: Our webhook consumer (optionally) requests RTMS start for meetings, after receiving a meeting.started event.
Meetings: All meetings were joined as Host.
General OAuth Apps:
1. I created a general app “Meeting Only” that sends two webhook events (meeting.started and meeting.ended) to my dev consumer (via ngrok).
2. I have an existing app “RTMS local dev” that sends meeting.rtms_started, meeting.rtms_stopped, meeting.started, and meeting.ended events to my dev consumer (via ngrok).
3. I added 3 new users (A, B, and C) to our test account, through our client application, using Zoom API.
4. They were all assigned to our default group “All Users”.
5. I created a new group “Dev Test”.
6. I added users A, B, and C to the “Dev Test” group.
7. I removed C from the “All Users” group (just to see if it changed anything).
8. I added the “Dev Test” group to the “Meeting Only” app.
9. I added the “Dev Test” group to the “RTMS local dev” app.
10. I scheduled meetings using users A, B, and C: the webhook consumer receieved nothing (and the apps didn’t log Events).
11. I then added users A, B, and C individucally to the “RTMS local dev” app, scheduled a new meeting for each, and all events were received and logged.
12. I then disabled user A, B, and C in the “RTMS local dev” app, scheduled a new meeting for each, and no events were received (or logged).
13. (odd bit) I then added users A, B, and C individually to the “Meeting Only” app, and scheduled a new meeting for each:
a. Users A and C triggered meeting.started (and meeting.ended) events from the “Meeting Only” app, and the RTMS start request received a (403) Forbidden response.
b. User B triggered meeting.started (and meeting.ended) events from the “Meeting Only” app, and the RTMS start request triggered meeting.rtms_started (and meeting.rtms_stopped) in the “RTMS local dev” app.
I couldn’t find any differences between user A and user B (and user C wasn’t a member of the “All Users” group).
Webhook Only App:
I also created an Account Level Webhook Only app to send meeting.started and meeting.ended.
Activating this app on our test account triggered the meeting.started (and meeting.ended) event, but every attempt to start RTMS received a (403) Forbidden response.
Additional thoughts about users and groups within an app:
Once added, a User can be disabled or removed.
After adding a Group, there are no options…
In theory, one could move all of the Users into a new Group, but it would be nice to have a disable or remove option, after adding a Group.