Issue with downloading meeting recording transcript Meetings

I want the bot to join independently, not behalf of a user. One thing to mention is that join tokens are not authorization tokens and to join a meeting that requires login, you’d need to supply a ZAK token. They closed the security gap in their http client sometime in 2018 and all releases since then no longer forward passwords and reveryplay casino tokens. In the case of Microsoft, I can tell you that their HTTP client used to forward passwords and tokens until 2018. I also have the same issue, not in apps and its still infiltrating all my zoom calls I have Read AI removed from my Zoom account but it continues joining my meetings.
If someone makes an account with Email A for the yoga company and Email B for their Zoom account, then this meeting authentication would fail right? We’re aiming to avoid user-context tokens where possible for backend automation. I just wanted to update this thread since I had a helpful and insightful conversation with @alison from Read’s team about this issue. Hi @elisa.zoom , Our institution just had the same issue occur.

• Any guidance would be greatly appreciated!
• So, blocking Read.AI worked if we are the ones that run the meeting.
• Hi @achen @brian11 @brooksntI created a support ticket on your behalf, you should hear back from our team soon.Please make sure to follow up with them
• Hopefully there is a better fix than creating an individual support ticket for each case as this is clearly an issue for many users.
• Feel free to post your issue there, you will be able to get some help there!
• Please submit a ticket for me to assist with removing it.
• If you have any other questions, do not hesitate to reach out to contact Read support since they will be better equipped to assist you!

Zoom Meeting API – Zoom Developers

I never signed up with Read.ai so I can’t go to that account to disable it. And it still says it was invited by one of our internal users. So, blocking Read.AI worked if we are the ones that run the meeting. Has anyone else faced this issue? Checked for Zoom app updates—it’s up to date.

Recording wasn’t created & cannot be found

You’re correct that the ZAK token is required to join a meeting on behalf of a user, but it’s actually not needed if you just want the bot to join on its own. When call client.join(meetingId, token, userName, passcode) will create new meeting session instead. The app was never installed in our org’s Zoom account but it is showing up in countless meetings.

Join meeting error after host ends the session

The way you connected security considerations with the behavior of modern HTTP clients (like curl and Microsoft’s .NET client) was particularly insightful and gave me a better understanding of what’s happening under the hood. Your reply was not only informative but also incredibly helpful in clarifying why this issue occurs when trying to download Zoom files. They do this on purpose to avoid leaking passwords and tokens. Please sign in to your Zoom account to download if you are the host. Please sign in to your Zoom account to download if you are the host.” I’m using a server-to-server OAuth app owned by the account owner and have ensured that all necessary scopes are enabled, as outlined in Zoom’s API documentation.
I’ve read through this disturbing thread and realize that we can’t figure out how to get rid of it, either. Can you please open a ticket for me? It is concerning that this could happen so easily to many people, come on Zoom! I also don’t have the app in my Zoom settings.
How to resolve this error and what I’m doing wrong here.? Thanks again for taking the time to share your expertise with the community here, your efforts are truly appreciated! After reading your response, I took another look at the curl man page and discovered that while the -L flag allows curl to follow redirects, I actually needed to use the –location-trusted option instead.

• Is there something additional I need to configure, perhaps on the account level or within the API request logic?
• After reading your response, I took another look at the curl man page and discovered that while the -L flag allows curl to follow redirects, I actually needed to use the –location-trusted option instead.
• The Join Token allows you to join meetings without authentication requirements, but it will fail when “require authentication to join” is enabled (as you’ve seen with error code 23)
• Hi,Please help me remove Read.ai from my account.
• It can be accessed via admin and user-auth app.
• This is a huge issue for us as we have intentionally disabled transcripts for the related meetings and have major security concerns with an unapproved ai monitoring the meetings.
• In the case of Microsoft, I can tell you that their HTTP client used to forward passwords and tokens until 2018.

How to get rid of read.ai?

This is a huge issue for us as we have intentionally disabled transcripts for the related meetings and have major security concerns with an unapproved ai monitoring the meetings. Can you please create a support ticket for me as well? Did this problem get resolved, as I am continually fed up with read.ai hijacking my meetings and overriding my zoom recordings How do I get rid of it?

Would appreciate any insight into whether this functionality is available now or potentially on the roadmap. I’ve noticed that ai_call_summary_id appears in the call log details, but I can’t find any documented endpoint to retrieve the summary content itself.

Why My Zoom Not Working On Mobile data?

Made sure my mobile data is turned on and working (other apps like YouTube and Instagram work fine). I’ve been having this frustrating issue with Zoom lately, and I’m hoping someone can help me out. Can someone help me with the issue? Hi @thendral.d can you please share how you creating the meeting via API?
In contrast, The ZAK token is necessary to join as an authenticated user, especially when mandatory login is enforced With only Client ID, Client Secret, and the meeting URL I am getting error My suggestion here would just be to omit any kind of join token in your config.toml, and instead just provide your Client ID, Client Secret, and the meeting URL that you want to join. This will allow you to start a meeting and join authorization-required meetings too @elisa.zoom should we update the api documentation I linked in OP as the curl command provided there does not work due to redirects? This flag ensures the Authorization header is passed along when following the redirect, which resolves the issue with downloading files from Zoom.