# Setting up OAuth IMAP Google {% hint style="warning" %} Google only accepts public AND secure (https) URLs. If your GLPI URL is not accessible from the internet, this procedure will not apply. {% endhint %} ## Install the OAuth IMAP application * From **`Setup`** > **`Plugins`**, install **`Oauth imap`**.

*** ## Creating a project * From your [Google console](https://console.cloud.google.com/) (administrator access is required), go to your organisation then new project ![New project creation](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-d0225dba7cfd3eedab250dc831ce0767596da7c0%2Foauth-imap-google-1.png?alt=media) * Enter the name of your project * Click on **`Create`**

* Return to your organisation, * Select your project ![Select the new project](https://2961961068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsGALtnzA2IROeldmXKt5%2Fuploads%2Fgit-blob-8176b8b40938b8f1bc00d417d44eef3f864bda69%2Foauth-imap-google-3.png?alt=media) *** ## Setting up Oauth access * From the menu, click on **`APIs & Services`**. * Then **`OAuth consent screen`**

### Application Information * From the preview, click **`Get started`** * Enter the application name and the user support email (users will be able to contact you with questions regarding their consent)

### Audience * Indicate what type of audience will be able to use this application (here internal because the user who will be using the imap services is a user of the organization)

### Contact information * Enter the contact name (this contact is notified of changes made to the application)

*** ## Google API Services User Data Policy * Accept the Google API Services User Data Policy and click **`Continue`** and **`Create`**

*** ## Creating a Client ### Application Type \ You now need to create an application client that will connect Google to your GLPI instance using an application ID and a client secret. * In the **Clients** tab, click **`Create a client`**. * Select **Web Application** as the application type. * Enter a name for your application.

### Authorised redirect URIs \ The return URL must be specified in this section. This URL is found in GLPI under **`Setup`** > **`OAuth IMAP`** > **`+ Add`**

* Enter this URL in the **Authorised redirect URIs** section of your application.

* Click **`Create`** to validate your application *** ## Application information {% hint style="warning" %} In the next step, the **client secret** will be displayed. Once you leave this screen, it will no longer be available. Remember to save it in a safe place. {% endhint %} The application is now created. The screen displays the application ID and the client secret, which you will need to enter in GLPI.

*** ## Finalizing GLPI configuration Once your application information is listed in GLPI, and your application is active, you can click on **`+ Add`**

### OAuth Authorization OAuth authorization is required for GLPI to use the IMAP services for the mailbox in question. * From the **OAuth Authorization** tab, click **`+ Create authorization`**. * Specify the account authorized to use the IMAP services.

*** ## Receiver configuration * From **`Configuration`** > **`Receivers`** > **`+ Add`** * Specify the server **`imap.google.com`** * In **Connection options**, select the previously created **IMAP OAuth** application * In Username, select the user with OAuth permissions

*** ## More information For more information on receivers configuration, please refer to the following article: Receivers configuration --- # Agent Instructions: 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: ``` GET https://help.glpi-project.org/tutorials/receivers/oauth_imap_google.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.