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

# Google

This guide shows how to configure Google as your identity provider.

## Prerequisites 

* You are an administrator of your Google Cloud Console
* You have [enabled the Admin SDK API](https://developers.google.com/workspace/guides/enable-apis) (required for synchronizing Groups)

## Create the OAuth application

1. Log into the [Google Cloud Console](https://console.cloud.google.com/).
2. Select an existing Project or create a new one.
3. Navigate to the [Google Auth Platform](https://console.cloud.google.com/auth/overview) via the Menu ![](https://storage.googleapis.com/support-kms-prod/JxKYG9DqcsormHflJJ8Z8bHuyVI5YheC0lAp) bar on the left.
4. If Google Auth Platform is not yet configured, click **Get Started**![](/files/r9GtHR4ih0lpSqmYNBmx)
5. Enter a name for this application (e.g. **Neurox Web App**) and select a user support email. Click **Next**.\
   .![](/files/8uN6bs2lAdtf6bUwoKCp)
6.  Select your intended **Audience**. We recommend **Internal** unless you want users to log in with email domains outside of your Google Workspace.\
   Click **Next**.\
   ![](/files/ri9wcf9doIp9d3p2vGAa)
7. Enter an email address for Google to contact you. Click **Next**.\
   ![](/files/jvzgHwsTWSJFruwv8duh)
8. Check the box to agree to Google's API Services policies. Click **Continue**.\
   ![](/files/jurqDZs8Lq5piVLtkVuL)
9. Click the **Create** button to create your application.\
   ![](/files/tDboaU9f6d5LbH9QE28r)

### Create the OAuth client

1. Click the **Create OAuth Client** button.\
   ![](/files/CuXUrUadfBX79B1Jn8lR)
2. Under **Application type** select **Web application**\
   ![](/files/uRQHCW3N2wV1MYLRcMv9)•
3. Enter a **Name** for your OAuth Client (e.g. **Neurox Web App**)\
   ![](/files/y1uT0ALEJfnZdMF63hsZ)
4. Under **Authorized JavaScript origins** click **Add URI**\
   ![](/files/eGSv2kDMw3DALmBarAJO)
5. In **URIs 1** enter your **Control Portal** URL (e.g. `random-words.goneurox.com`)\
   ![](/files/LiFad2xFJzASw0U9mkyk)
6. Under **Authorized redirect URIs** click **Add URI**\
   ![](/files/rU1qKiAjB29UTrwYHIvd)
7. Enter the following URIs (click **Add URI** to add more):
   1. `https://random-words.goneurox.com/api/connect/google/callback`
   2. `https://random-words.goneurox.com/idp/callback`
   3. `https://random-words.goneurox.com/sso/auth`\
      \
      Be sure to replace `random-words.goneurox.com` with your actual subdomain.\
      ![](/files/OtbWCy9vloFASbmHKfA1)
8. Click the **Create** button\
   ![](/files/pNAvTJBVWyDUw33Inj0k)

### Copy & Apply your OAuth credentials

1. Click the **Download** icon under **Actions**\
   ![](/files/b15KldbUTpgKU81pGYBH)
2. In the pop up modal, copy both the **Client ID** and **Client Secret** values
3. Run the following commands:

{% code overflow="wrap" %}

```shell
kubectl create secret generic -n neurox neurox-control-idp-google --from-literal=clientId=<Client ID> --from-literal=clientSecret=<Client Secret>
```

{% endcode %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.neurox.com/installation/identity-providers/google.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.