Configure Google as an Identity Provider in ZITADEL
This guides shows you how to connect Google as an identity provider in ZITADEL.
In ZITADEL you can connect an Identity Provider (IdP) like Google to your instance and provide it as default to all organizations. Also, you can register the IdP to a specific organization only. If you allow so, your organizations members can do the same in self-service.
Google Configuration​
Register a new client​
- Go to the Google Cloud Platform and choose your project: https://console.cloud.google.com/apis/credentials
- Click on "+ CREATE CREDENTIALS" and choose "OAuth client ID"
- Choose "Web application" as application type and give a name
- Add the redirect uri
- {your-domain}/ui/login/login/externalidp/callback
- Example redirect url for the domain
https://acme-gzoe4x.zitadel.cloud
would look like this:https://acme-gzoe4x.zitadel.cloud/ui/login/login/externalidp/callback
- Save the Client ID and Client secret
ZITADEL Configuration​
Add custom login policy​
The login policy can be configured on two levels. Once in the default settings and this can be overwritten for each organization. The only difference is where you configure it. Go either to the settings page of a specific organization or to the default settings page. Default Settings: $YOUR-DOMAIN/ui/console/instance?id=general Organization: Choose the organization in the menu and go to $YOUR-DOMAIN/ui/console/org-settings?id=login
- Go to the Settings
- Modify your login policy in the menu "Login Behavior and Security"
- Enable the attribute "External Login allowed"
You can also change the settings through the API directly either in the default settings or on a specific organization:
Go to the IdP Providers Overview​
Go to the settings page of your instance or organization and choose "Identity Providers".
In the table you can see all the providers you have configured. Also, you see all provider templates that are available.
Select the Google Provider template.
Create a new Google Provider​
The Google provider template has everything you need preconfigured. Add the client ID and secret created before on your Google App.
You can configure the following settings if you like, a useful default will be filled if you don't change anything:
Scopes: The scopes define which scopes will be sent to the provider, openid
, profile
, and email
are prefilled. This information will be taken to create/update the user within ZITADEL. ZITADEL ensures that at least the openid
-scope is always sent.
Automatic creation: If this setting is enabled the user will be created automatically within ZITADEL, if it doesn't exist.
Automatic update: If this setting is enabled, the user will be updated within ZITADEL, if some user data is changed withing the provider. E.g if the lastname changes on the Google account, the information will be changed on the ZITADEL account on the next login.
Account creation allowed: This setting determines if account creation within ZITADEL is allowed or not.
Account linking allowed: This setting determines if account linking is allowed. When logging in with a Google account, a linkable ZITADEL account has to exist already.
Either account creation or account linking have to be enabled. Otherwise, the provider can't be used.
Activate IdP​
Once you created the provider, it is listed in the providers overview. Activate it by selecting the tick with the tooltip set as available.
If you deactivate a provider, your users with links to it will not be able to authenticate anymore. You can reactivate it and the logins will work again.
The provider can also be activated via API. As the identity providers are sub-resources of the login settings, this is done by linking the provider to the settings:
Test the setup​
To test the setup, use incognito mode and browse to your login page. You see a new button which redirects you to your Google login screen.
By default, ZITADEL shows what you define in the default settings. If you overwrite the default settings for an organization, you need to send the organization scope in your auth request.
The organization scope looks like this: urn:zitadel:iam:org:id:{id}
.
You can read more about the reserved scopes
or use the ZITADEL OIDC Playground to see what happens with the login when you send different scopes.