Need clarity regarding Expiry for webinars and meetings.
Getting message - “Webinar has expired.” for webinarId - ***********
Details
As it is mentioned here - For security reasons, the recommended way to retrieve the updated value for the start_url field pro-grammatically (after expiry) is by calling the Retrieve a Meeting/Webinar APIand referring to the value of the start_url field in the response.
I have few questions -
Could you confirm if the time duration for expiry of a webinar is 2 hour and the start_url can be generated after the expiry? Is it the same for meetings, if not what is the expiry time of Meetings?
Can we control expiry time for the Webinar/Meeting, in terms of duration?
What is the security reasons mentioned here?
I am also not clear about the language here - updated value for the start_url field pro-grammatically (after expiry).
I am not getting the updated value for start_url for webinar id - ***********. It is showing that Webinar has expired. I should be able to regenerate the start_url after expiry?
Could you let me know what I am missing here?
If expiry duration is 2 hours, and webinar continues for more than 2 hours. Will it stop the webinar automatically?
Will users have to do some settings in this scenario by themselves or can I put some programmatic setting so that webinar doesn’t end abruptly for users?
*This post has been edited to remove any meeting / webinar IDs
I am calling the retrieve api after the expiry, it should give me the start_url and join_url, but it is throwing me error that access token is not valid. But using the same token I am able to call the other APIs, even I am able to create webinar/meetings.
Could you help me with this? You can look into the same webinar (id - ***********) for debugging.
Note - If I am calling the retrieve API using the same token before expiry it is giving me correct start_url and join_url.
*This post has been edited to remove any meeting / webinar IDs
Thanks for the reply, I have a question - For which I need answers to on urgent basis -
I have implemented - Update User Settings API . We are using this API for setting "embed_password_in_join_link, so that users will always have an embedded password in their join link. In our development app this is working properly but in production it is throwing error -
"Invalid access token, does not contain scopes: [user:write:admin, user:write, zms:user:write]."
I deauthorized app from Installed Apps section and reinstalled the App again. Note I am using the - User Level app, with /me in URL.
Why is this happening, am I missing something here?