# Keyclock and Zoom SSO configuration

**URL:** <https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907>\
**Category:** API and Webhooks\
**Created:** [April 19, 2020, 4:00pm UTC](https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907 "2020-04-19T16:00:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jitensachdeva](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jitensachdeva/32/2854_2.png) [@jitensachdeva](https://devforum.zoom.us/u/jitensachdeva)\
**Post date:** [April 19, 2020, 4:00pm UTC](https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907/1 "2020-04-19T16:00:07Z")

</div>

Do we have anywhere steps to integrate Keycloak SAML client with ZOOM SSO ?

There is very little documentation available around configuring SSO.

---

<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:** [April 21, 2020, 1:41am UTC](https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907/2 "2020-04-21T01:41:20Z")

</div>

Hey @jitensachdeva,

Please see our support docs for SSO info:

> **[Getting Started with SSO](https://support.zoom.us/hc/en-us/articles/201363003-Getting-Started-with-SSO)**
>
> Overview
> Single sign-on allows you to login using your company credentials. Zoom single sign-on (SSO) is based on SAML 2.0.
> Zoom acts as the Service Provider (SP), and offers automatic user provisi...

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![jitensachdeva](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jitensachdeva/32/2854_2.png) [@jitensachdeva](https://devforum.zoom.us/u/jitensachdeva)\
**Post date:** [April 26, 2020, 11:50am UTC](https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907/3 "2020-04-26T11:50:36Z")

</div>

Thanks I have gone through this but this was not helpful as every SAML provider comes with its own set of configuration.

---

<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:** [April 29, 2020, 4:54pm UTC](https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907/4 "2020-04-29T16:54:27Z")

</div>

Hey @jitensachdeva,

Checkout this support doc as well:

> **[Advanced SAML mapping](https://support.zoom.us/hc/en-us/articles/115005081403-Advanced-SAML-Mapping)**
>
> Overview
> Advanced SAML mapping allows you to designate a Zoom license, add-ons, user roles, user groups, or IM groups based on a value being passed using SAML. This can allow you to have certain us...

Let me know if that helps!

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![angelj](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@angelj](https://devforum.zoom.us/u/angelj)\
**Post date:** [June 22, 2020, 3:47pm UTC](https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907/5 "2020-06-22T15:47:55Z")

</div>

Hi @jitensachdeva. I’m in the process of integrating keycloak and zoom at work.

Using the settings I leave below, we were able to successfully create a user and log it into Zoom. Of course there are still many tests and fine tuning to do; this is not the final setup.

### Keycloak’s client

- Client ID: `yourcompany.zoom.us` (note there’s no leading ‘https://’)
- Client Protocol: `saml`
- Enabled: `ON`
- Include AuthnStatement: `ON`
- Sign Documents: `OFF`
- Sign Assertions: `ON`
- Signature Algorithm: `RSA_SHA256`
- SAML Signature Key Name: `KEY_ID`
- Canonicalization Method: `EXCLUSIVE`
- Force POST Binding: `OFF`
- Force Name ID Format: `ON`
- Name ID Format: (pick one according to your needs)
- Valid Redirect URIs: `https://yourcompany.zoom.us/*`
- Master SAML Processing URL: `https://yourcompany.zoom.us/saml/SSO`
- Logout Service POST Binding URL: `https://yourcompany.zoom.us/saml/SingleLogout`
- Logout Service Redirect Binding URL: `https://yourcompany.zoom.us/saml/SingleLogout`

For testing purposes, we used the builtin mappers (`X500 email`, `X500 givenName` y `X500 surname`)

### Zoom settings

- Sign-in Page URL: `yourkeycloakbaseURL/auth/realms/yourrealm/protocol/saml`
- Sign-out Page URL: `yourkeycloakbaseURL/auth/realms/yourrealm/protocol/saml`
- Identity provider certificate: you can copy the content of the tag **dsig:X509Data** from `yourkeycloakbaseURL/auth/realms/yourrealm/protocol/saml/descriptor`
- Service Provider (SP) Entity ID: `yourcompany.zoom.us`
- Issuer (IDP Entity ID): `yourkeycloakbaseURL/auth/realms/yourrealm`
- Binding: `HTTP-Redirect`
- Signature Hash Algorithm: `SHA-256`

**Attributes mapping**

- Email address: `urn:oid:1.2.840.113549.1.9.1 (i.e. value from X500 email)
- First Name: urn:oid:2.5.4.42 (i.e. value from X500 givenName)
- Last Name: urn:oid:2.5.4.4 (i.e. value from X500 surname)
- Employee Unique ID: (in our case, NameID)

Hope this serves you as a starting point,  
Angel

---

<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:** [June 24, 2020, 5:12pm UTC](https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907/6 "2020-06-24T17:12:29Z")

</div>

Hey @angelj,

Thanks for contributing to the Zoom Developer Community! 🙂

-Tommy

---

<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, 10:25pm UTC](https://devforum.zoom.us/t/keyclock-and-zoom-sso-configuration/13907/7 "2020-08-21T22:25:21Z")

</div>

Closed on August 21, 2020, 10:25pm UTC


