> 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/roadmap-and-releases/versions/v1.1.0.md).

# v1.1.0

**Release Name**: eSignet

**Release Date**: 22nd September, 2023

## Overview

The 1.1.0 version of eSignet focuses on the **Consent Registry** feature.

The consent registry is designed to store user consent on claims and scopes requested during login to a relying party application using eSignet or the Wallet application ([Inji](https://docs.mosip.io/inji/)).

Key highlights of this feature are:

* Storage of user consent against the requested claims and scopes in the database
* If consent is already provided, the consent screen is bypassed when the user logs in using eSignet.
* Recapture consent in the event of changes in requested claims or scopes.

{% hint style="info" %}
Consent management is not applicable in this release as it solely focuses on the storage of user consent. The functionalities of editing, revoking, updating, or viewing the consent after it has been given by the user are considered beyond the scope of this release.
{% endhint %}

### Features Included

Below are the features available in the release:

* Login with OTP
* Login with biometrics
* Wallet based authentication
* Multi-language support
* Captcha validation
* Consent storage

### Repositories Released

* eSignet: [v1.1.0](https://github.com/mosip/esignet/tree/v1.1.0)
* artifactory-ref-impl: [v1.2.0.1-B5](https://github.com/mosip/artifactory-ref-impl/tree/v1.2.0.1-B5)
* mosip-config: [v1.1.0-ES](https://github.com/mosip/mosip-config/releases/tag/v1.1.0-ES)

For details for deployment go through the helm charts in the [eSignet repository](https://github.com/mosip/esignet/tree/v1.1.0/helm).

### Documentation

* [Feature Documentation](/home/esignet/esignet-authentication/features.md)
* [Integration Guides](/home/esignet/esignet-authentication/develop/integration/relying-party/development-and-integration-with-esignet.md)
* [End User Guide](/home/esignet/esignet-authentication/test/end-user-guide.md)
* [API Documentation](https://github.com/mosip/esignet/blob/v1.1.0/docs/idp-oidc-service-openapi.yaml)
* [QA Report](/home/esignet/roadmap-and-releases/versions/v1.1.0/test-report.md)


---

# 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/roadmap-and-releases/versions/v1.1.0.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.