> 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.4.0.md).

# v1.4.0

**Release Number**: v.1.4.0

**Release Date**: 23rd April, 2024

### Overview

Version 1.4.0 of eSignet introduces a new authentication mode and addresses known issues.

1. **Knowledge Based Identification (KBI)**

   We are excited to share that eSignet has expanded its authentication options to include Knowledge Based Identification (KBI) as one of its factors. With eSignet's integration capabilities, existing ID repositories storing user specific details can now be easily integrated with eSignet. This integration enables OpenID based login, allowing users to access relying party services seamlessly.

To learn more about Knowledge Based Identification, click [here](/home/esignet/esignet-authentication/features.md).

1. **Fixes for known issues from v1.3.0**

{% hint style="info" %}
**Note:**

1. The authentication factor can be referred to as either Knowledge Based Authentication (KBA) or Knowledge Based Identification (KBI). However, from the eSignet’s perspective, we will specifically refer to the authentication method as Knowledge Based Identification (KBI).
2. Given the relatively low level of assurance provided by Knowledge Based Identification (KBI), we recommend that Knowledge Based Authentication (KBA) / Knowledge Based Identification (KBI) should be used for the issuance of Verifiable Credentials (VC) or certificates rather than serving as a primary method of authentication.
   {% endhint %}

## Repositories Released

| Repository Released        | Tags                                                          |
| -------------------------- | ------------------------------------------------------------- |
| esignet                    | [v1.4.0](https://github.com/mosip/esignet)                    |
| mosip-config               | [v1.4.0-ES](https://github.com/mosip/mosip-config)            |
| artifactory-ref-impl       | [v1.4.0-ES](https://github.com/mosip/artifactory-ref-impl)    |
| digital-credential-plugins | [v0.1.0](https://github.com/mosip/digital-credential-plugins) |

For details on deployment, refer to the [helm charts](https://github.com/mosip/esignet/tree/v1.4.0/helm) in the eSignet repository.

## 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.4.0/docs/esignet-openapi.yaml)
* [QA Report](/home/esignet/roadmap-and-releases/versions/v1.4.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.4.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.