# In-Client Auth flow in Zoom Linux desktop client

**URL:** <https://devforum.zoom.us/t/in-client-auth-flow-in-zoom-linux-desktop-client/101520>\
**Category:** API and Webhooks\
**Created:** [January 9, 2024, 9:18pm UTC](https://devforum.zoom.us/t/in-client-auth-flow-in-zoom-linux-desktop-client/101520 "2024-01-09T21:18:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mstf](https://avatars.discourse-cdn.com/v4/letter/m/7993a0/32.png) [@mstf](https://devforum.zoom.us/u/mstf)\
**Post date:** [January 9, 2024, 9:18pm UTC](https://devforum.zoom.us/t/in-client-auth-flow-in-zoom-linux-desktop-client/101520/1 "2024-01-09T21:18:52Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**

> **[ZoomSdk | @zoom/appssdk - v0.16.16](https://appssdk.zoom.us/classes/ZoomSdk.ZoomSdk.html#onAuthorized)**
>
> Documentation for @zoom/appssdk - v0.16.16

**Description**  
The in-client authorization flow works without problems on Windows within the Zoom desktop client. Nevertheless, the same code does not fire the `onAuthorized` event on Linux. Is there a plan to support this on Linux? Here is my code:

```auto
zoomSdk.addEventListener("onAuthorized", (event) => {
    console.log(event);
});
zoomSdk.authorize({ codeChallenge: codeChallenge, state: state })
    .then(e => console.log(e))
    .catch(e => console.log(e));

```

**Error?**  
No error message. The zoomSdk.authorize() method even returns `{"message": "Success"}` However, the event is not fired, hence the code cannot be retrieved in order to request an access token.

---

<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:** [January 12, 2025, 12:55pm UTC](https://devforum.zoom.us/t/in-client-auth-flow-in-zoom-linux-desktop-client/101520/2 "2025-01-12T12:55:34Z")

</div>

Closed on January 12, 2025, 12:55pm UTC

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