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.
- Your reply was not only informative but also incredibly helpful in clarifying why this issue occurs when trying to download Zoom files.
- @amanda-recallai If you take a look at the meeting_service_interface.h file in linux meeting sdk .
- There are many threads and support articles on this.
- If guest init too long after host ended the meeting.
- Would this user be flagged to them in any way?
- Hi @thendral.d can you please share how you creating the meeting via API?
- How to resolve this error and what I’m doing wrong here.?
Remove "Read AI" from account
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.
- “Only the host can download this recording.
- The app was never installed in our org’s Zoom account but it is showing up in countless meetings.
- Alternatively, you could use a third-party integration like Recall.ai which streamlines the entire integration process into one simple-to-use api
- I want a ticket opened for me as well to get rid of this in my account.
- I am looking for more information on how we can make the meeting more secure as today many students will share the links with their friends.
- 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.
- I also don’t have the app in my Zoom settings.
How to get rid of read.ai?
Is there any solution for overwriting this as the host of the meeting? These fitness businesses will have their students register and then we give join meeting links. I am looking for more information on how we can make the meeting more secure as today many students will share the links with their friends. Will I be able to get the AI call Summaries if i do an Oauth 2.0 S2S request before and get the token? Yes you can use it with S2S OAuth apps after adding the admin scope. And would like to request a simple way to access the AI call summary from the callId alone, rather than relying on userId.
Issue with downloading meeting recording transcript
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.
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.
You can require both, either or neither. Essentially, you have several options to define an authenticated user. Would this user be flagged to them in any way?
Join meeting error after host ends the session
Read.ai joins private meetings that are not recorded due to security and privacy reasons. I contacted Read.ai support team, and they refused to delete my account. This morning, I discovered that no recording file was created or saved. In your instance, I would enable both to best ensure only certain people have access to the meeting.
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.
Recording wasn’t created & cannot be found
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.
Read.ai is not listed in our downloaded apps but is making its way into nearly every meeting and causing concerns about privacy and legality. Can a ticket be created for me as well? We have the same problem, never installed the app but it try to join our meetings.
I want a ticket opened for me as well to get rid of this in my account. I am having the same issue and cannot get Read.ai off my account. API Reference for /docs/api/rest/reference/zoom-api/methods Please create it for a scheduled meeting via the web portal. @gianni.zoom Please help me resolve the issue
Meeting join token not working in zoom meeting linux sdk
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 reveryplay casino a different domain. Only the host can download this recording.
Leave a Reply