# Deauthorization issue in the app review

**URL:** <https://devforum.zoom.us/t/deauthorization-issue-in-the-app-review/3492>\
**Category:** App Marketplace\
**Created:** [March 6, 2019, 8:18am UTC](https://devforum.zoom.us/t/deauthorization-issue-in-the-app-review/3492 "2019-03-06T08:18:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vishnu.raned](https://avatars.discourse-cdn.com/v4/letter/v/34f0e0/32.png) [@vishnu.raned](https://devforum.zoom.us/u/vishnu.raned)\
**Post date:** [March 6, 2019, 8:18am UTC](https://devforum.zoom.us/t/deauthorization-issue-in-the-app-review/3492/1 "2019-03-06T08:18:30Z")

</div>

Hi  
We have been working on the VideoKen for Zoom app, which is currently under review. The second reviewer gave us the following comment:

“The Logout and Deauthorize button on your app must invoke [this](https://marketplace.zoom.us/docs/guides/authorization/oauth-with-zoom#revoking-tokens) request instead of sending a POST request to your own Deauthorization Event Handler.”

However, we cannot send a deauthorization request from the front end to the Zoom deauth link, because it will be a cross origin request. We are already calling the zoom deauth/ revoke token link from our backend.

How do we proceed, in this case?

Also, for webhooks, will the verification token be passed as a POST param?

This has been documented on this link: [https://support.zoom.us/hc/requests/1063497](https://support.zoom.us/hc/requests/1063497)

---

<div class="post-metadata">

**Author:** ![TimZoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/timzoom/32/978_2.png) [@TimZoom](https://devforum.zoom.us/u/TimZoom)\
**Post date:** [March 6, 2019, 8:47pm UTC](https://devforum.zoom.us/t/deauthorization-issue-in-the-app-review/3492/2 "2019-03-06T20:47:04Z")

</div>

I am bringing this feedback internally to our team. I will have one of my team members respond with more information.

---

<div class="post-metadata">

**Author:** ![vishnu.raned](https://avatars.discourse-cdn.com/v4/letter/v/34f0e0/32.png) [@vishnu.raned](https://devforum.zoom.us/u/vishnu.raned)\
**Post date:** [March 14, 2019, 1:53pm UTC](https://devforum.zoom.us/t/deauthorization-issue-in-the-app-review/3492/3 "2019-03-14T13:53:45Z")

</div>

Thanks Tim. Any updates on this?

---

<div class="post-metadata">

**Author:** ![vishnu.raned](https://avatars.discourse-cdn.com/v4/letter/v/34f0e0/32.png) [@vishnu.raned](https://devforum.zoom.us/u/vishnu.raned)\
**Post date:** [March 18, 2019, 8:06am UTC](https://devforum.zoom.us/t/deauthorization-issue-in-the-app-review/3492/4 "2019-03-18T08:06:07Z")

</div>

Hi Tim,

Any update on this? We haven’t heard back from your team yet.

Thanks

Vishnu

---

<div class="post-metadata">

**Author:** ![TimZoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/timzoom/32/978_2.png) [@TimZoom](https://devforum.zoom.us/u/TimZoom)\
**Post date:** [March 18, 2019, 7:41pm UTC](https://devforum.zoom.us/t/deauthorization-issue-in-the-app-review/3492/5 "2019-03-18T19:41:55Z")

</div>

Still looking into it. Thanks for your patience.

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 6:12pm UTC](https://devforum.zoom.us/t/deauthorization-issue-in-the-app-review/3492/6 "2020-08-21T18:12:35Z")

</div>

Closed on August 21, 2020, 6:12pm UTC