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?
Zoom Meeting API – Zoom Developers
- Also for the Restrict Participant access thread, the links have been broken with the new updates to the Zoom site.
- It’s not showing up in our list of installed apps.
- You can require both, either or neither.
- I took a look and can’t find the reference to the error in the template you shared.
- @elisa.zoom should we update the api documentation I linked in OP as the curl command provided there does not work due to redirects?
- The user would not be able to join the meeting.
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.
Remove "Read AI" from account
- I created a support ticket on your behalf to remove Read AI from your account.
- Is the purpose of join-token option in sdk is to allow a bot to a meeting with mandatory login option enabled.?
- Can a ticket be created for me as well?
- I want the bot to join independently, not behalf of a user.
- Hi @elisa.zoom , our organization has the same issue – can you please assist in completely removing read.ai and blocking it to all users of account?
- This error suggests that despite passing the download_access_token, there’s still a permissions issue tied to the host role.
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.
Meeting join token not working in zoom meeting linux sdk
Any guidance would be greatly appreciated! Is there something additional I need to configure, perhaps on the account level or within the API request logic? Has anyone faced a similar issue or have insights on how to work around this limitation? “Only the host can download this recording. If step 1 is completed but step 2 has not yet finished connecting to the media server, and the host ends the session during this time, it results in a JOIN_MEETING_FAILED error. If guest init too long after host ended the meeting.
How to create Zoom meeting survey at end of meeting
But I cannot see the meeting survey at ending of the meeting. @amanda-recallai If you take a look at the meeting_service_interface.h file in linux meeting sdk . Alternatively, you could use a third-party integration like Recall.ai which streamlines the entire integration process into one simple-to-use api I did find it in the other meeting headless linux sample template repo though which may be what you’re referring to based on the screenshot you shared? I took a look and can’t find the reference to the error in the template you shared. The config.toml is updated at run time so there is no chance of the token getting expired.
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 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.
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?
I’m not super familiar with curl but I’m pretty sure there’s an option you can specify to authorize the token to be forwarded when following the HTTP 307 redirect. The behavior I just described might be desirable from a security stand point, but it conflicts with the way Zoom wants us to download files because they redirect our requests to a different domain. Only the host can download this recording.
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.
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 reveryplay casino Read’s team about this issue. Hi @elisa.zoom , Our institution just had the same issue occur.
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.
It can be accessed via admin and user-auth app. 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! Hello, we are having the same issue. It is not added, and has never been approved in our App Marketplace dashboard. Please submit a ticket for me to assist with removing it. It’s not showing up in our list of installed apps.