# Configuring OAuth Connection Settings

This technique allows the user’s account information to be used by third-party applications / service without revealing the user’s password.It acts as an intermediary on behalf of the end user, providing the service with an access token that authorizes specific account information to be shared.\
\
The **SSO OAuth** section allows you to configure and manage OAuth connection.

1. Navigate to **Adv. Configuration** > **SSO - OAuth**.
2. Click the **Create New Connection** button.
3. Enter / Select the required values in the fields. Refer to the table below for field names and descriptions.
4. Review all the values and click the **Save Connection** button.
5. The OAuth connection will be configured successfully.
6. To edit details of a connection, click the connection in the **Existing Connections** section, and then click the **Edit Connection** button.
7. Edit the values of the required fields and click **Save Connection**.
8. To delete a connection, click the connection in the **Existing Connections** section, and then click the **Delete Connection** button.<br>

{% hint style="info" %}
**Note**: Authorization URL, Access Token URL and User Detail URL should be specified for Enterprise applications and can be left blank for Standard applications. If left blank, the default values will be used i.e.\
\
Authorization URL: <https://login.microsoftonline.com/common/oauth2/v2.0/authorize>

Access Token URL: <https://login.microsoftonline.com/common/oauth2/v2.0/token>\
User Detail URL: <https://graph.microsoft.com/v1.0/me>
{% endhint %}

| Field                 | Description                                                                                                                                                       |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Provider Type**     | Provider type for which you want to create the new connection. The available options are **Microsoft Office 365**, **Microsoft ADFS**, and **OpenId Connect**.    |
| **Redirect URLs**     | URI(s) to which the authorization server will send the user to after the app has been successfully authorized, and granted an authorization code or access token. |
| **Connection Name**   | Name that will be used to identify the connection.                                                                                                                |
| **Client Id**         | Unique ID assigned to the application registered with the OAuth provider.                                                                                         |
| **Client secret**     | Secret code assigned to the application registered with the OAuth provider.                                                                                       |
| **Authorization URL** | URL to which the frontend will redirect the user for authorization.                                                                                               |
| **Access Token URL**  | URL which should be called for obtaining the access token.                                                                                                        |
| **User Detail URL**   | URL which should be called for obtaining the user details.                                                                                                        |


---

# 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.solar-archive.com/docs/advanced-configuration/configuring-oauth-connection-settings.md?ask=<question>
```

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.