# Joining meeting with encrypted password - embed\_password\_in\_join\_link

**URL:** <https://devforum.zoom.us/t/joining-meeting-with-encrypted-password-embed-password-in-join-link/33258>\
**Category:** API and Webhooks\
**Created:** [October 14, 2020, 6:50pm UTC](https://devforum.zoom.us/t/joining-meeting-with-encrypted-password-embed-password-in-join-link/33258 "2020-10-14T18:50:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![neecholai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/neecholai/32/4241_2.png) [@neecholai](https://devforum.zoom.us/u/neecholai)\
**Post date:** [October 14, 2020, 6:50pm UTC](https://devforum.zoom.us/t/joining-meeting-with-encrypted-password-embed-password-in-join-link/33258/1 "2020-10-14T18:50:40Z")

</div>

**Description**  
We have an app that allows hosts to create zoom meetings, and users to join these zoom meetings all directly from our app using the Zoom API.

We want to ensure our users can join a meeting as easily as possible (preferably without needing to manually enter a password). I understand the host’s settings need to have `embed_password_in_join_link` enabled in order for attendees to join without manually entering a password. However, in the case that the host has this `embed_password_in_join_link` field disabled, we need to catch for this.

We have the following solutions but want to get your opinion on the best method, or if there is a better approach for this:

1. Get user settings before creating each meeting. If `embed_password_in_join_link` is disabled, update user settings to enable it. Create meeting. Update user settings back to it’s original state. The drawback to this is it requires another the user:write scope we don’t currently have. Every existing user will likely have to re-oauth with zoom to provide this extra scope, right? Does this render all of our access/refresh tokens invalid if we add this scope?

2. Add column to our db that indicates if password is required for the meeting. Get user settings before creating each meeting. If they have `embed_password_in_join_link` disabled, mark that password is required for the meeting in our db. In this case, we would need to provide password in our app for this condition. Drawback to this is it will introduce a lot more logic, code and UI considerations for our app.

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
Oauth

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 15, 2020, 8:08pm UTC](https://devforum.zoom.us/t/joining-meeting-with-encrypted-password-embed-password-in-join-link/33258/2 "2020-10-15T20:08:18Z")

</div>

Hey @neecholai,

Great question. In your scenario 1, I should clarify that if you need to add a new scope to your app (user:write), you’re correct in that all existing users will need to re-authenticate:

> **[Upgrading an App - App Submission - Publishing an App - Documentation](https://marketplace.zoom.us/docs/guides/publishing/app-submission/upgrading#reauthorization)**
>
> Upgrading an App
> 
> Upgrading (or updating) an app which has already been published will require functional and security reviews similar to the original S...

If you’re going for the least user-impact, I think option 2 would be less obtrusive, understanding that this creates more work for you.

Let me know if you have additional questions I can help with.

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [November 15, 2020, 6:08am UTC](https://devforum.zoom.us/t/joining-meeting-with-encrypted-password-embed-password-in-join-link/33258/3 "2020-11-15T06:08:37Z")

</div>

Closed on November 15, 2020, 6:08am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
