We are currently running the WebSDK version 1.7.5 in our production environment with no errors. We attempted an upgrade over the past couple of days to 1.7.7, and are now receiving an error message indicating that the participantId we’re passing in is > 12 characters (which is true). Historically (1.7.5 and prior), passing this participantId parameter allowed us to launch the Zoom session via the WebSDK with a user’s details including the participantId, which then translated into the Participant_ID field in the downstream web-hooks. These participantIds look something like CkltXNm4R322elaVEjRFGQ - and correspond to the user_id field we’re pulling from our Users extracts.
Per some other articles, we tried omiting the participantId from the init’s json completely, instead relying only on the userEmail property. This did NOT work though. Though we successfully recorded the user_name of the joining person in subsequent webhook events, the participant_ID returned was a completely random identifier not tied at all to the account we had joined the meeting under.
1.7.6 and beyond is throwing an Invalid Parameters error indicating that the participantId exceeds 12 characters. This doesn’t make sense because all of the user_id fields exceed 12 characters. It seems like something has fouled up in 1.7.6 and above that confuses the expected lengths of participantId and participant_user_id, which we can’t really supply at init because we think that’s auto-generated.
1.7.5 worked/allowed us to pass participantId with lenghts > 12 characters. 1.7.7’s release failed to allow us to do the same thing.
For the WebSDK, we really need to provide the user context to the ZoomMtg.Init so that subsequent webhooks correctly identify which user is logged in. We use that information for LOTS of downstream processes, and we can’t rely on the user_name field because it’s not distinct and the formatting differs from the user object. This was definitely working in 1.7.5.