> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/manage/on-premise-installation/google-sso-login.md).

# Google SSO Login for On-Prem

Learn how to set up Google SSO for on-premise installation. Find guidelines on creating OAuth authorization credentials in the Google developer console.

To setup Google SSO for on-premise installation, you will need to create OAuth authorization credentials in the Google developer console to identify the application to Google's OAuth 2.0 server.

1. Go to the [<mark style="color:blue;">Developer Credentials page</mark>](https://console.developers.google.com/apis/credentials).
2. Click **Create credentials > OAuth client ID**.
3. Select the **Web application** application type.
4. Name your OAuth 2.0 client and add the Javascript origins and redirect urls replacing the following with your domain.

<figure><img src="https://273246003-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOAPqUQVbLbsfI5YESl32%2Fuploads%2FfE41dVN3PCwHMlzLPHkI%2FScreen%20Shot%202022-05-10%20at%2011.28.34%20AM.png?alt=media&amp;token=0eaef24c-90d0-4879-99fb-64b3e9fc8c7f" alt=""><figcaption></figcaption></figure>

5. Add the Google Client ID and Client Secret that is on this page to your docker `.env` file.

```shell
GOOGLE_CLIENT_ID={YOUR_GOOGLE_CLIENT_ID}
GOOGLE_CLIENT_SECRET={YOUR_GOOGLE_CLIENT_SECRET}
```

Restart the server, and Google SSO should work.


---

# 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.aviator.co/manage/on-premise-installation/google-sso-login.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.