# SSO support in OAuth

**URL:** <https://devforum.zoom.us/t/sso-support-in-oauth/1372>\
**Category:** API and Webhooks\
**Created:** [June 19, 2018, 9:05pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372 "2018-06-19T21:05:04Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joris\_De\_Smedt1](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Joris\_De\_Smedt1](https://devforum.zoom.us/u/Joris_De_Smedt1)\
**Post date:** [June 19, 2018, 9:05pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/1 "2018-06-19T21:05:04Z")

</div>

Hello,

&nbsp;

So I set up an OAuth application in zoom to integrate with our application.

Everything works fine if the user authenticates with his email and password. But when he selects the option to login with&nbsp;SSO he always gets an error.

The problem is somewhere with redirecting I am guessing. So when I select to login with SSO, I have to give my domain. Afterwards he logs in perfectly, but then when he redirects I get an error saying there is an invalid client id (see screenshot).

Since everything goes fine without using SSO I am guessing there is something wrong at Zoom’s side. Also I did not had the option to login with SSO when wanted to authenticate with OAuth so I am guessing this is a new feature.

Could it be that this is a bug? If not, could somebody help me to see what is going wrong?

&nbsp;

Kind Regards,

Joris.

&nbsp;

 ![](https://support.zoom.us/hc/user_images/Ix4vou3Kw8S7fPbHEZrOtQ.png)

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [June 19, 2018, 9:59pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/2 "2018-06-19T21:59:19Z")

</div>

Hi Joris,&nbsp;

Yes, signing in with SSO is a new feature that we released over last weekend. Does the client ID match the one set for your OAuth application? Here’s is a documentation on how to use SSO with OAuth -&nbsp;[https://developer.zoom.us/docs/oauth/.&nbsp;](https://developer.zoom.us/docs/oauth/.%C2%A0)

Let us know if that works for you.&nbsp;

Thanks

&nbsp;

---

<div class="post-metadata">

**Author:** ![Joris\_De\_Smedt1](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Joris\_De\_Smedt1](https://devforum.zoom.us/u/Joris_De_Smedt1)\
**Post date:** [June 19, 2018, 10:05pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/3 "2018-06-19T22:05:35Z")

</div>

Hi,

Yes the client id does match. Like I said before, the OAuth authentication works for users who authenticate using a email and password. It only fails (with the error described above) when the user tries to authenticate with SSO.

Kind regards,  
Joris

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [June 19, 2018, 10:31pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/4 "2018-06-19T22:31:18Z")

</div>

Hi Joris,&nbsp;

Do you have Single Sign on Enabled? You’ll will need to have a paid plan with more than 10 host.&nbsp;

Thanks

---

<div class="post-metadata">

**Author:** ![Joris\_De\_Smedt1](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Joris\_De\_Smedt1](https://devforum.zoom.us/u/Joris_De_Smedt1)\
**Post date:** [June 20, 2018, 9:14am UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/5 "2018-06-20T09:14:08Z")

</div>

Hi Michael,

&nbsp;

Yes we do, the organisation is Showpad and we have a pro plan.

&nbsp;

Kind Regards,

Joris.

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [June 20, 2018, 4:09pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/6 "2018-06-20T16:09:29Z")

</div>

Hi Joris,&nbsp;

We have reached back with our Engineering team and there is a bug with SSO login. I will follow up with you as soon as we fix the issue.&nbsp;&nbsp;

Thanks

---

<div class="post-metadata">

**Author:** ![Joris\_De\_Smedt1](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Joris\_De\_Smedt1](https://devforum.zoom.us/u/Joris_De_Smedt1)\
**Post date:** [June 25, 2018, 12:05pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/7 "2018-06-25T12:05:16Z")

</div>

Hey Michael,

Could you provide an update on this?

&nbsp;

Kind regards,

Joris.

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [June 25, 2018, 5:13pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/8 "2018-06-25T17:13:20Z")

</div>

Hi Joris,&nbsp;

Yes, our Engineering team is still deploying a fix for the SSO bug and should be available tomorrow morning.&nbsp;

Thanks

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [June 26, 2018, 7:59pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/9 "2018-06-26T19:59:05Z")

</div>

Hi Joris,&nbsp;

I wanted to update you that we are still fixing the issue and we will be deploying the fix for the SSO bug this weekend.&nbsp;

Thanks

---

<div class="post-metadata">

**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\
**Post date:** [July 26, 2018, 5:57pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/10 "2018-07-26T17:57:05Z")

</div>

Hi Joris,&nbsp;

I wanted to follow up with you. Our SSO fix was implemented a couple weeks ago. Are you still experiencing this issue?

Thanks

---

<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, 5:49pm UTC](https://devforum.zoom.us/t/sso-support-in-oauth/1372/11 "2020-08-21T17:49:39Z")

</div>

Closed on August 21, 2020, 5:49pm UTC


