> For the complete documentation index, see [llms.txt](https://docs.esignet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esignet.io/home/esignet/esignet-authentication/test/try-it-out/integrate-with-e-signet.md).

# Integrate with eSignet

If you are a relying party looking to integrate with **eSignet,** you can connect with us by completing the [form](https://docs.google.com/forms/d/e/1FAIpQLSerko7k1wiy1sjgfRSfRU5Bjkb7cKc0t2z0FmKt6mSLBqJGXQ/viewform) here. This will assist us in facilitating a seamless integration on [collab](https://collab.mosip.net/).

Here are some FAQs on the Google form.

<details>

<summary>What are redirect URIs?</summary>

The redirect URIs are the list of URIs the relying party provides where the authorization code needs to be sent after successful authentication by eSignet.

</details>

<details>

<summary>Why do you need a public key?</summary>

The public key shared by the relying party is used to verify the digital signature when there is an authorization request. It is also used to encrypt the `user_info` and send it to the relying party.

</details>

<details>

<summary>What is JWK format?</summary>

JWK (JSON Web Key) is a JSON data structure that represents a set of public keys utilizing either the Elliptic Curve or RSA families of algorithms (public key cryptography).

Learn more about JWK [here](https://openid.net/specs/draft-jones-json-web-key-03.html).

</details>

<details>

<summary>How can I convert a public key to JWK format?</summary>

Here is the easiest way to convert your public key (a `.PEM` file) to JWK format for testing.

* Go to the link <https://russelldavies.github.io/jwk-creator/>
* Select **Public Key Use** as **Signing**
* Select **Algorithm** as **RS256**
* Select **Key ID** as **alpha-numeric-random-string**
* Paste the public key PEM file content in **PEM encoded key**
* Click on the **convert** button

<img src="https://3349261888-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylzvZHp30DQ3rNCClELV%2Fuploads%2Fgit-blob-8ae1a560ccd10a8d105675799419e72b3b7a6449%2Fimage%20(1).png?alt=media&amp;token=52b15a3b-ed4f-4e12-8463-37d756c7193f" alt="" data-size="original">

</details>

Once you receive the eSignet credentials at the email address provided on the form, please go through our integration guide on [Relying Party Integration](/home/esignet/esignet-authentication/develop/integration/relying-party.md) to complete the integration.


---

# 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.esignet.io/home/esignet/esignet-authentication/test/try-it-out/integrate-with-e-signet.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.