> For the complete documentation index, see [llms.txt](https://authdocs.skill-mine.com/licentio-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://authdocs.skill-mine.com/licentio-documentation/usecases/custom-provider-integration.md).

# Custom Provider Integration

**Table of Contents**

1. **Overview**&#x20;
   * 1.1 Purpose&#x20;
   * 1.2 Scope
2. **Integration Steps**&#x20;
   * 2.1  Project Integration
   * 2.2  Custom Provider in Admin Settings
   * 2.3  Google API Setup
   * 2.4  Licentio Provider Integration
3. **Conclusion**&#x20;

### 1. Overview&#x20;

**1.1 Purpose**&#x20;

* The purpose of this documentation is to guide administrators through the process of integrating custom authentication providers as custom providers using OAuth and OpenID Connect protocols.&#x20;
* This integration expands user login options and enhances security through industry-standard authentication methods.&#x20;

**1.2 Scope**&#x20;

* This documentation covers the steps required for administrators to integrate various authentication providers as custom providers.&#x20;
* These providers offer OAuth and OpenID Connect support, allowing users to log in to your system using their accounts from these providers securely.&#x20;

### 2. Integration Steps&#x20;

Admins can enhance their application's authentication options by integrating custom authentication providers that support OAuth and OpenID Connect.&#x20;

These providers offer a seamless way for users to log in using their existing accounts from those platforms.&#x20;

**2.1 Project Integration**&#x20;

1. In your application's admin panel, navigate to the **settings-> Custom Providers.**&#x20;
2. Refer:[ Custom Providers. ](/licentio-documentation/settings/authentication-methods.md#oauth-and-openid-connect)
3. Create the desired custom provider (Google, Facebook and any other provider supports OAuth and OpenID Connect.).&#x20;

**2.2 Custom Provider in Admin Settings**&#x20;

1. After successfully integrating the custom authentication provider on the admin side, it will appear in the **Custom Providers** section of your application's admin settings. Example: **Google Provider Integration**&#x20;
2. As an example, we'll guide you through integrating Google as a custom provider.&#x20;
3. Admins can follow the steps mentioned in the **Project Integration** section using the provided URLs from the Google Cloud Console and Google Developers Console.&#x20;

**2.3 Google API Setup**&#x20;

1. Admins access the [Google Cloud Console](https://console.cloud.google.com/) and create a new project.&#x20;
2. Enable the Google+ API for the project to allow user profile information access.&#x20;

#### OAuth2&#x20;

Obtain Client ID and Client Secret&#x20;

1. Access the [Google Developers Console](https://console.developers.google.com/) and select the project.&#x20;
2. Configure OAuth consent screen settings (e.g., application name, user support email).&#x20;
3. Create OAuth 2.0 credentials and obtain the client ID and client secret.&#x20;

#### **2.4 Example: Licentio Provider Integration**&#x20;

For this example, we'll integrate **Licentio** as a custom provider. Here's the specific process:&#x20;

1. In your admin panel, navigate to the **Clients -> Client Settings** section.&#x20;

**Refer:**

{% content-ref url="/pages/5HRVZkBJAGfq5eynGzmY" %}
[Client Settings](/licentio-documentation/settings/open-id-connect-setttings/client-settings.md)
{% endcontent-ref %}

2. Create a new client for Licentio, which will generate a client ID and client secret.&#x20;
3. Return to the **Custom Providers** section and follow the remaining steps by creating **Licentio** as the custom provider and entering the obtained client ID and secret.&#x20;
4. Configure OpenID Connect settings with the issuer URL as instructed.&#x20;
5. The issuer URL also serves as a discovery endpoint. By appending the well-known path /.well-known/openid-configuration to the issuer URL, clients (applications) can retrieve metadata about the OpenID provider. This metadata includes information such as supported endpoints (authorization, token, userinfo, etc. )&#x20;
6. Once the **Licentio** Custom Provider is created it will show in the Social Login Providers list.&#x20;

<figure><img src="/files/tUXnCjHyEfLpc2g27Rou" alt=""><figcaption></figcaption></figure>

#### 2.4.1 Integrating Licentio User Login&#x20;

To integrate Licentio user login into your user applications, follow these steps:&#x20;

1. Navigate to the flow settings in Admin panel.&#x20;
2. Choose the authentication flow that corresponds to the Licentio integration.&#x20;
3. Configure the Login settings flow and include **Licentio** as an authentication option.&#x20;

Refer:[ Login Settings](/licentio-documentation/blueprints.md#login-settings)

4. Here we can configure Licentio as a Login Provider.&#x20;

&#x20;

<figure><img src="/files/NmX4ewdVi5e5hHBIj5vC" alt=""><figcaption></figcaption></figure>

4. Users will now be able to log in to your application using their Licentio accounts.

<figure><img src="/files/N4XSmdIhhD8IzkJwUr0Z" alt=""><figcaption></figcaption></figure>

### 3. Conclusion&#x20;

In summary, when we combine custom authentication providers that work with OAuth and OpenID Connect, we make user logins safer and easier.&#x20;

By following the steps to getting the needed credentials, setting up OpenID Connect, and smoothly adding these options, administrators enable users to access their accounts with confidence and security.&#x20;

This combination ensures a smooth user experience and strong security.&#x20;
