How do I set up SAML SSO with Google?

In this article, you will find a step-by-step guide to setting up SAML SSO with Google as the identity provider.

In this article, you will receive a step-by-step guide to setting up SAML SSO, provided you use Google as your identity provider. If you are looking for instructions on setting up the SSO login at sipgate, you can find them here.

1

Open admin menu

In the first step, log in to your Google account as an admin and select in the right Menu Apps --> Web and mobile apps .

sipgate help center SSO Google1.png

2

Create SAML app

In the selected area, open the dropdown menu Add App and select Add custom SAML App .

sipgate help center SSO Google2.png

3

Name app

In the next step, you have the option of giving the created app any name you like, adding a description and an icon. Then continue by clicking Continue.

sipgate help center SSO Google3.png

4

Import IdP data

You will receive the identity provider data (SSO URL, Entity ID and Certificate), which you must enter in the interface configuration at sipgate. Then click Continue.

sipgate help center SSO Google5.png

5

Enter SP data

In the next step, enter the service provider data generated by sipgate.

sipgate help center SSO Google6.png

Set the point Name ID Format on EMAIL and Name ID Format on Basic Information > Primary email, and then click Continue.

sipgate help center SSO Google7.png

6

Complete setup

To complete the setup, click in the next step on Finish.

sipgate help center SSO Google8.png

The SAML app for sipgate is set up and must be activated in the next step.

sipgate help center SSO Google9.png

7

Activate app

To activate the app, simply navigate to the User Access- area or use the dropdown menu, and set the status to ON for everyone.

sipgate help center SSO Google10.png

8

Enable SSO at sipgate

In the final step, enable the SSO login method at sipgate by switching the toggle.

sipgate help center SSO7.3.png

Errors and solutions

Error message: "An error has occurred. Please try again. Back to login."

Cause: The web user with Google SSO was deleted and created as a new web user. In the Google SSO database, the old web user is still linked. Workaround: ask sipgate Support to delete the Google SSO entry so that the next Google SSO login works. Solution: We are working on a solution so that when a web user is deleted, the Google SSO deletion is also performed.