# Token based login

**URL:** <https://devforum.zoom.us/t/token-based-login/159>\
**Category:** Web\
**Created:** [February 12, 2017, 9:50am UTC](https://devforum.zoom.us/t/token-based-login/159 "2017-02-12T09:50:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bipin\_Thakur](https://avatars.discourse-cdn.com/v4/letter/b/3d9bf3/32.png) [@Bipin\_Thakur](https://devforum.zoom.us/u/Bipin_Thakur)\
**Post date:** [February 12, 2017, 9:50am UTC](https://devforum.zoom.us/t/token-based-login/159/1 "2017-02-12T09:50:53Z")

</div>

Dear Team,

&nbsp;

Please clarify following points:

&nbsp;

1. Can we restrict a user to inter the meeting room only once. In other words, a user logged in from a device should not be allowed to login from any other device.
2. How can we hide the URL from end user so that they can not temper the query string?
3. How can we open the [zoom.us](http://zoom.us) URL in a iframe?
4. Can we create a taken based login. The token should be disabled/expired as soon as it is used for first successful login.

&nbsp;

Thanks,  
Bipin

---

<div class="post-metadata">

**Author:** ![Ammar\_Naqvi](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@Ammar\_Naqvi](https://devforum.zoom.us/u/Ammar_Naqvi)\
**Post date:** [February 14, 2017, 6:47pm UTC](https://devforum.zoom.us/t/token-based-login/159/2 "2017-02-14T18:47:56Z")

</div>

Hey Bipin,&nbsp;

Thank you for the questions. To answer them:

1. This is currently not possible and we will take this into consideration for possible use cases.

2. The URL displayed to end users can not tamper any settings related to your end. The creators private API key and secret are &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;required to&nbsp;make changes to the meetings or webinars.

3. If you have a meeting URL then: \<iframe src=“meeting URL”\>\</iframe\>

4. This is possible through some coding; When the user logs in the first time, fetch User ID using API endpoint …/user/getbyemail and &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;then …/user/revoketoken from user by passing their user id and email.&nbsp;

&nbsp;

Cheers,  
Ammar

---

<div class="post-metadata">

**Author:** ![Alp\_Altunel](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@Alp\_Altunel](https://devforum.zoom.us/u/Alp_Altunel)\
**Post date:** [October 14, 2017, 7:13am UTC](https://devforum.zoom.us/t/token-based-login/159/3 "2017-10-14T07:13:22Z")

</div>

user/revoketoken does not return token value.&nbsp;

if you look at this link:&nbsp;[https://zoom.github.io/api/#revoke-sso-token](https://zoom.github.io/api/#revoke-sso-token)

you may see the result:

Example Response

```
{
  "id": "unique_id",
  "email": "user@company.com",
  "updated_at": "2013-09-02T12:00:00Z"
}

```

also when I request by /user/getbyemail

token is empty.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 12, 2021, 8:04pm UTC](https://devforum.zoom.us/t/token-based-login/159/4 "2021-05-12T20:04:09Z")

</div>

Here is how to limit participants joining on multiple devices:

> [@Webinar - Limiting Each Participant to a Single Unique Session and/or Device ID?](https://devforum.zoom.us/t/webinar-limiting-each-participant-to-a-single-unique-session-and-or-device-id/26163/2):
>
> Hey @ariesto.kosasih, When using [Webinar Registration](https://support.zoom.us/hc/en-us/articles/204619915-Scheduling-a-Webinar-with-Registration), you can turn off the “Allow attendees to join from multiple device” setting. Let me know if that answers your question. slight_smile Thanks, Tommy

-Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 12, 2021, 8:04pm UTC](https://devforum.zoom.us/t/token-based-login/159/5 "2021-05-12T20:04:12Z")

</div>

Closed on May 12, 2021, 8:04pm UTC


