SSOGEN / SSO Applications / Zoom SSO: Sign In to Zoom Through SSOGEN
Integration
Zoom SSO: Sign In to Zoom Through SSOGEN
Zoom SSO setup with SSOGEN comes down to two exchanges of values and a launch address. Follow the order below and test with a real person before activating, so the first live sign-in is not the first test.
Zoom SSO with SSOGEN gives every employee one sign-in to meetings, under the sign-in policy you set. Zoom is the service provider (SAML) or the client (OpenID Connect), and SSOGEN is the identity provider. SSOGEN connects any application that speaks SAML 2.0 or OpenID Connect this way, with no catalog entry needed.
The order of the steps matters: collect the application’s values first, register, then give SSOGEN’s values back. The Zoom administration screen uses its own labels, so match fields by meaning with the table below.
Values to copy for Zoom
| SSOGEN field or value | Vendor-neutral name in the application | Direction |
|---|---|---|
| Service provider entity ID | Entity ID, identifier, audience | From Zoom into SSOGEN |
| Assertion consumer service URL | ACS URL, reply URL | From Zoom into SSOGEN |
| Single logout URL (optional) | Logout URL | From Zoom into SSOGEN, if it has one |
| IdP entity ID | Identity provider entity ID, issuer | From SSOGEN into Zoom |
| Single sign-on URL | Sign-in URL, login URL | From SSOGEN into Zoom |
| Signing certificate | Identity provider certificate | From SSOGEN into Zoom |
| Name ID | User matching attribute | Choose in SSOGEN, set the same format in Zoom |
If Zoom publishes a metadata file, upload it in the Connection step, and SSOGEN fills in the first three rows. In the other direction, importing SSOGEN’s metadata address configures the last four rows at once, including the certificate.
Do the steps in this order
Work in this sequence:
- Collect the application’s service provider values from its single sign-on screen, without turning SSO on.
- Register the application in SSOGEN and enter those values.
- Open the Integration tab and put SSOGEN’s values into the application.
- Assign people, run Test, and select Activate application.
Keep an administrator sign-in that does not use SSO until you have proved that SSO works.
Register, assign, test and activate
- In the Admin Console, open Applications, then SAML (or OpenID Connect) and start the registration wizard.
- Fill in General and Connection with the values above, choose a Sign-in policy, and set Identify the person by.
- Enter the Launch URL, the address that starts the application’s own SSO sign-in. Selecting Next saves the application, but it stays unavailable.
- Assign a person or group, run Test for a named person, and review the result.
- Select Activate application. The application then appears in My Apps for the people assigned to it.
The full screens and every message appear in Register a SAML application and Register an OpenID Connect application. The test and activation details appear in Assign people, set the sign-in policy, test and activate.
Questions people ask
Where do I start a Zoom SSO sign-in?
From My Apps or from the application’s own SSO sign-in address. Both send the person to the application, which sends its sign-in request to SSOGEN.
What happens if the entity ID has a typo?
SSOGEN refuses the sign-in and reports that no service provider is registered with that entity ID. Compare both sides character for character.
Is the application live as soon as I save it?
No. It is saved but unavailable until you select Activate application on the last step.
Where to go next
- Return to the hub. The SSO applications hub has the protocol comparison and the other guides.
- Choose the protocol. If you are not sure whether Zoom belongs under SAML or OpenID Connect, read Choose how to connect an application.
- See it working. To watch Zoom SSO set up in this order, request a trial from the SSOGEN team.