> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-wallet/inji-web/technical-overview/backend-services/esignet-authentication-layer.md).

# eSignet - Authentication Layer

**eSignet** provides a user-friendly and efficient method for individuals to authenticate themselves and a access online services. Serving as a dependable identity provider for relying party applications, it grants access to services without requiring additional login credentials. eSignet also provides a secure means of verifying an individual's identity against trusted identity providers, such as national identity databases, driver's license systems, passport systems, or other trusted sources. The level of assurance here is determined by the authentication factor employed. To know more about eSignet, click [here](https://docs.esignet.io/).

Let's explore how eSignet integrates with Inji Web and provides authentication solutions for the download workflow as follows:

### Download VC

* The User navigates to the `Home page of the Inji web application` and selects an issuer and credential type
* Next, the authentication page is displayed which is the interface provided by eSignet.
* The user enters the required information, such as Policy Number, Name, and Date of Birth. Subsequently, the system gets redirected back to Mimoto to add a client\_id and generate a key pair, initiating the request to download the credential
* Once Mimoto provides the response with the client\_id and key, the credential endpoint of the issuer is invoked to get the credentials

### Credential endpoint

Once the access token is received from eSignet by Mimoto, Mimoto uses it to request the Verifiable Credential from Certify.

**Note**: The endpoint attribute is present in the issuer's well-known configuration.

<mark style="color:green;">`POST`</mark> `undefined/vci/credential`


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inji.io/inji-wallet/inji-web/technical-overview/backend-services/esignet-authentication-layer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.