> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.3/social-registry/features/id-integration/id-authentication.md).

# ID Authentication

work in progress

The Social Registry (SR) is updated via various mechanisms. The mechanisms such as API, Login-based direct data entry, Registration portal, ODK, and CSV. It is necessary to confirm that the information provided about the beneficiaries' identities are accurate and that they are currently receiving benefits from the applicable programs. With the ID Authentication feature, SR can check if each beneficiary has validated themselves using biometrics within a specified time frame, allowing it to periodically verify each beneficiary's current status.

Only Registrars, Administrators, and Enumerators are authorised to use National IDs and biometrics or OTPs to authenticate applicants/registrants both in person and virtually.

Note:

The ID Authentication feature avoids the need for self-authentication via self-service portals.

## Source code

[G2P Auth: OIDC - Reg ID](/1.3/pbms/developer-zone/odoo-modules/authentication-oidc-reg-id.md)

## Related user guides

:notebook\_with\_decorative\_cover:[Configure eSignet Auth Provider for ID Authentication](/1.3/social-registry/features/id-integration/id-authentication/user-guides/configure-esignet-auth-provider-for-id-authentication.md)

:notebook\_with\_decorative\_cover:[ID Authentication Process](/1.3/social-registry/features/id-integration/id-authentication/user-guides/id-authentication-process.md)

:notebook\_with\_decorative\_cover:eSignet Client Creation


---

# 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.openg2p.org/1.3/social-registry/features/id-integration/id-authentication.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.