> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/security/identity-providers-sso/oidc-identity-providers/google-idp-oidc-configuration.md).

# Google IDP - OIDC - Configuration

{% hint style="success" %}

#### Required User Credentials

\[**Flosum User**] - **SystemAdministrator** Role
{% endhint %}

{% hint style="success" %}

#### Important Note

The instructions in this article cover a third-party app and may not reflect the latest version. Please use these instructions as a guide to complete the task, but be aware that some screens, field names, and steps may have changed.
{% endhint %}

## ![](https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FSxcnKlaJKPzDqONWoDNv%2FSummary2-Small-Icon.svg?alt=media\&token=5e3253d0-a069-4ba5-9c06-83c70bd0b21d) Overview

This guide explains how to integrate Google IDP using OpenID Connect (OIDC) with Flosum Cloud Apps to enable Single Sign-On (SSO) for seamless login.

{% hint style="info" %}
For more general instructions about adding an Identity Provider, see the following article.

* [Adding an Identity Provider (SSO)](/global-settings/security/identity-providers-sso/adding-an-identity-provider-sso.md)
  {% endhint %}

{% hint style="warning" %}

#### Customer-Hosted

Customers who host Flosum Apps on their own infrastructure will have a custom URL for logging into their apps. When using this documentation, replace any **Flosum Hosted URLs** with your own URLs.
{% endhint %}

### Outline Of Steps Involved

* **Create a Client with Google IDP**
* **Set up the Redirect URL**
* **Obtain the Client ID and Client Secret**
* **Create an Identity Provider with Flosum Global Settings**
* **Test the SSO**

## Configuring Google IDP for Flosum Cloud Apps

This section shows you how to configure a Google IDP to work with Flosum Cloud Apps for SSO.

{% stepper %}
{% step %}

### Create an OAuth Client ID in Google Cloud Console

1. Access the Google Cloud Console.
2. Navigate to the **API & Services** section.
3. Select **Credentials**.
4. Click **Create Credentials**.
5. From the dropdown menu, choose **OAuth Client ID**.

   <div align="left"><figure><img src="https://lh6.googleusercontent.com/_XUmgld4tNU9OtlPN1aJCk5P2nTZA0jm5grpeN1tsxLBaxtGdteS2eaCslT-x6eppnEtuFzoAWm42iYYcmoUlKnDVdfsr9uPiCgH4cCazbelZqenXmPFgI9NW_3MvEoFHoMawB3uObigzJhk" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Specify Application Type and Name

1. Under the **Application type** section, select the appropriate option (e.g., **Web application**).
2. Enter a name for your application in the **Name** field.

   <div align="left"><figure><img src="https://lh4.googleusercontent.com/-GwXBWN1CX-l-LFx2zS7CyDDEoCxR2T1TRrqp4fJU-UNAPd-kIiGdwJ6J7AqBT2X3LMOX81zaZYgUx_C708vsM_rL_U97uUIJaxuikg74VLnRuI0m35rePmFzzgdHJvEJgDfKWQLIDgKXSEC" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

#### Configure Authorized Redirect URIs and Retrieve Credentials

1. In the **Authorized redirect URIs** section, add the URL of your region for each Flosum Cloud App you want to use with SSO. See the table below for the URLs for your region.

{% tabs %}
{% tab title="United States URLs" %}

<table><thead><tr><th width="180">Flosum Cloud App</th><th>Callback URL</th></tr></thead><tbody><tr><td>Global Settings</td><td>https://global-us.flosum.app/api/v1/oauth/callback</td></tr><tr><td>Backup &#x26; Archive</td><td>https://backup-us.flosum.app/api/v1/oauth/callback</td></tr><tr><td>DevOps</td><td>https://devops-us.flosum.app/api/v1/oauth/callback</td></tr></tbody></table>
{% endtab %}

{% tab title="Germany URLs" %}

<table><thead><tr><th width="180">Flosum Cloud App</th><th>Callback URL</th></tr></thead><tbody><tr><td>Global Settings</td><td>https://global-de.flosum.app/api/v1/oauth/callback</td></tr><tr><td>Backup &#x26; Archive</td><td>https://backup-de.flosum.app/api/v1/oauth/callback</td></tr><tr><td>DevOps</td><td>https://devops-de.flosum.app/api/v1/oauth/callback</td></tr></tbody></table>
{% endtab %}

{% tab title="Japan URLs" %}

<table><thead><tr><th width="180">Flosum Cloud App</th><th>Callback URL</th></tr></thead><tbody><tr><td>Global Settings</td><td>https://global-jp.flosum.app/api/v1/oauth/callback</td></tr><tr><td>Backup &#x26; Archive</td><td>https://backup-jp.flosum.app/api/v1/oauth/callback</td></tr><tr><td>DevOps</td><td>https://devops-jp.flosum.app/api/v1/oauth/callback</td></tr></tbody></table>
{% endtab %}

{% tab title="Australia URLs" %}

<table><thead><tr><th width="180">Flosum Cloud App</th><th>Callback URL</th></tr></thead><tbody><tr><td>Global Settings</td><td>https://global-au.flosum.app/api/v1/oauth/callback</td></tr><tr><td>Backup &#x26; Archive</td><td>https://backup-au.flosum.app/api/v1/oauth/callback</td></tr><tr><td>DevOps</td><td>https://devops-au.flosum.app/api/v1/oauth/callback</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

2. Click **Create**. **Note**: After creating, the client's credentials will be displayed in a dialog box. Keep this open for the next step.

   <div align="left"><figure><img src="https://lh6.googleusercontent.com/4yFlMkTY7LLaXvIWuB5dSIPqNvuqxTvQIveJWJqG8v19OgZ3tAdKNXcpUWw38LIauCG90DSh57oIGsE4K_Y-GrMtgLTExvlacuBDm0qgklumFrqCYPeKItLt4LXR94bBBwZyIVMuIODoZHKR" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

#### Retrieve Google IDP Client Details

{% hint style="info" %}
You will need **Your Client ID** and **Your Client Secret** values when creating the Identity Provider in Flosum Global Settings.
{% endhint %}

1. Copy the **Your Client ID** value.
2. Copy the **Your Client Secret** value.

   <div align="left"><figure><img src="https://lh5.googleusercontent.com/S6avWV0kQ7YnIS2z9_jBuKlLo29Sx8IoBZSSrIjK1bQ_lWKIsq7gufkwLHEXF7p295aKc7KigJ9bZASTovr6yP63ussIaBhzWSJJ9bOiWJqswAJp8VAAaFhi4Pcxw9hD1Z2NpQyJhNIRxIBn" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="info" %}
The **Issuer URL** for most configurations is: `https://accounts.google.com` . However, it is recommended to confirm the URL and copy it if it is different.
{% endhint %}
{% endstep %}
{% endstepper %}

## Create Identity Provider In Global Settings

{% stepper %}
{% step %}

### Create Identity Provider

Follow the general instructions in the article below to get started creating an OIDC Identity Provider.

1. [Adding an Identity Provider (SSO)](/global-settings/security/identity-providers-sso/adding-an-identity-provider-sso.md)
2. Complete the **Basic information** section.
   1. Select **OPEN\_ID** for the identity provider **Type**.
3. Complete the **Button information** section.
4. (Optional) Complete the **Group information** section.

**Complete OpenId Information Fields**

Copy the information from your Google IDP application into the OpenId Information section. The table explains which Google IDP fields to enter into which Flosum Fields. The final screenshot shows a completed identity provider for a Google IDP OIDC application.

The sections above show you how to find the values found in the **Google IDP Fields** column.

| Flosum Fields     | Google IDP Fields                                       |
| ----------------- | ------------------------------------------------------- |
| **Client ID**     | **Your Client ID**                                      |
| **Client Secret** | **Your Client Secret**                                  |
| **Issuer**        | `https://accounts.google.com`  (unless otherwise noted) |

<div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2F8qq4982KeRDETD2cZHIP%2FGoogleIdpOidcConfig-CreateIdentityProvider-01.png?alt=media&amp;token=329a283c-f16b-46cf-a382-19e1e9202498" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Save and Test

{% hint style="info" %}
For instructions on logging in with SSO, see the following article.

* [Logging In With SSO](/global-settings/security/identity-providers-sso/logging-in-with-sso.md)
  {% endhint %}

1. Click **Save** to save the identity provider.
2. To test, open an incognito window.
3. Start logging in to Global Settings with your tenant name.
4. If the identity provider was configured successfully, you should see the SSO button you created.&#x20;

<div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FMqMNcUxDk0VfgScGf8rG%2FGoogleIdpOidcConfig-CreateIdentityProvider-02.png?alt=media&amp;token=d1f2cb2e-9675-4ba1-b9a5-e27138edf79e" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flosum.com/global-settings/security/identity-providers-sso/oidc-identity-providers/google-idp-oidc-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.