# Integration Options and Discovery Endpoints

eSignet supports integration with both [**Mock ID**](#id-1.-mock-id-integration) and [**MOSIP ID**](#id-2.-mosip-id-integration) systems for authentication and identity verification.

The **integration flow and configuration steps** remain identical for both options, the only difference lies in the **discovery endpoints**, which determine the environment and underlying ID system you connect to.

{% hint style="info" %}
Note: The two options listed here — **Mock ID** and **MOSIP ID** — are provided **only for testing and proof-of-concept (POC)** purposes within the [**MOSIP Collab environment**](https://collab.mosip.net/).
{% endhint %}

{% hint style="info" %}
In real-world deployments, eSignet can be configured to work with **national ID systems or other identity providers** as per the country’s implementation and integration requirements.
{% endhint %}

<details>

<summary><strong>Understanding Discovery Endpoints</strong></summary>

A **discovery endpoint** is a standard part of the **OpenID Connect (OIDC)** specification.\
It provides a **metadata document** (commonly located at `/.well-known/openid-configuration`) that allows relying parties (RPs) to automatically discover key configuration details for integrating with the identity provider (IdP).

**Each discovery document mainly includes:**

1. Authorization, Token, and UserInfo endpoint URLs
2. Supported scopes, claims, and grant types
3. Public keys for token signature validation
4. Supported authentication methods and response types

**For more details refer** [**here**](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata)**.**

</details>

<details>

<summary><strong>Why Discovery Endpoints Matter for Relying Parties</strong></summary>

For developers and integrators, discovery endpoints simplify setup by:

1. **Automating configuration:** No need to hardcode or manually maintain endpoint URLs.
2. **Ensuring consistency:** RPs always use up-to-date endpoint details published by eSignet.
3. **Reducing errors:** Helps avoid misconfigurations in authorization or token flows.

</details>

### **Discovery Endpoints for Mock ID and MOSIP ID Integration** <a href="#discovery-endpoints-for-mock-id-and-mosip-id-integration" id="discovery-endpoints-for-mock-id-and-mosip-id-integration"></a>

#### **1. Mock ID Integration**

Use this option to integrate with a **Mock ID system**, which is designed to **simulate a real ID system** for **testing and development purposes**.

Please refer [here](https://esignet-mock.collab.mosip.net/) for the Mock ID discovery endpoints.<br>

**Purpose:**

1. Enables developers to test authentication flows safely.
2. Returns claims and responses similar to production with mock user data.
3. Ideal for validating OIDC client configuration and redirect flows.

#### **2. MOSIP ID Integration**

Use this option if you want to use a **MOSIP ID** for your **use case demonstrations or integration testing**.

Please refer [here](https://esignet-mosipid.collab.mosip.net/) for the MOSIP ID discovery endpoints.<br>

**Purpose:**

1. Connects to the live MOSIP identity system for real user authentication.
2. Returns genuine user claims and ID tokens after successful login.
3. Suitable for end-to-end verification before deployment.

To get started with integration. and onboard your client to eSignet please refer to this [page](/esignet-authentication/test/try-it-out/integrate-with-e-signet.md)


---

# 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://docs.esignet.io/esignet-authentication/develop/integration/relying-party/integration-options-and-discovery-endpoints.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.