If not, we can use the API to remove the password, download the video, and then re-add the password. Only problem with this is that we need to also request the scope “recordings:write”. You’re shit out of luck if you’ve already got users and they don’t have this scope.
So gross haha. Note that there may be other restrictions on your user’s meeting recordings, so you might have to patch more than just the password (e.g., expiry), but I’ve kept the example short for demonstration purposes.
That’s a big turnaround! Thanks for listening - glad Zoom upped the priority of this bug.
I’m interested to see that you still need the “recording.write” scope in order to download a password protected recording. That’s a bit odd, isn’t it, to need to “write” to the recording just to download? Funnily enough, it’s actually the same scope needed for my workaround above - is the new zoom update doing a similar thing under the hood?
I finally submitted our Zoom Marketplace Oauth app for my startup Videohop just yesterday, and had to include the “recording.write” scope for the workaround. Interesting to see that I will still need it even after the bug is fixed.
I am able to download the recording using the base URL in a browser session where the user has already authenticated using the web login on another page. But I’d like to be able to initiate the download from bash.
Ah I didn’t see Tommy’s update. @cruiz666 , thanks for bumping. I had moved on to other fires. I’ll get an email together when I can get that environment back up. @tommy , hopefully we’re just making a simple omission or something. Are you using the download url generated by the API call ( GET /meetings/{meetingId})?
You’re welcome, and no, I’m using the urls that arrive in the recording.completed webhooks. Technically they are the same (I think). I have tried to download it by query string, and by bearer but I get answers similar to the ones you already mentioned:
For the other actions I use an oauth token, but this does not work for the download, I tried to implement the jwt with the same credentials, but I have not been able to make it work …
Hi Tom,
I have been reporting since March. I have been sending you all the details including download url, download token, code segment, etc. I have sent the details to developersupport@zoom.us
I’m having the same issue as @cruiz666. Is this solved?
I use the recording.completed webhook content to get the download url. I’ve tried attaching the JWT token via query string. The response I get is:
This issue is very random and happens only for about 1 in 10 meetings (on average). Any help is appreciated.