> 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.2/developer-zone/repositories/openg2p-auth.md).

# openg2p-auth

## Contents

This repository contains <>

## eSignet integration

openg2p-auth is an extension to server-auth to setup further parameters and facilitate further functionalities required for OpenG2P. The settings for openG2P-auth in included in the same page as server-auth. Below are the parameters available for openg2p-auth

* **Allowed in Self Service Portal : Wether or not the login option will be visible for self service portal login page**
* **Use G2P Reg ID Type :** What would be the Registry ID Type used to store the token received
* **Partner Creation Call Validate Url :**
* **Partner Creation Validate Response Mapping :** Mapping the fields for registry record creation
* **Default Group User Creation :** Default user group to be created when the user log in to self service portal through eSignet for the first time.
* **Login Attribute Mapping On User Creation : What would be the login attribute connected with the user after the user is created for first time**


---

# 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.2/developer-zone/repositories/openg2p-auth.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.