> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/installation-setup/system-settings/openid-connect-settings.md).

# OpenId Connect Settings

The OpenId Connect connector allows you to connect ngSurvey to any OpenId Connect compatible identity provider compatible with OId Connect protocol like for example Identity Server, AWS Cognito or Keycloak. Once you have setup the connector all your existing users from your OId identity provider will be able to login seamlessly with their existing credentials.

## 🔅 OpenId Connect properties

* **`Issuer`** URI of your identity provider. eg: <https://yourissueruri.com>
* **`Client ID`** Client ID that identify your identity provider application.
* **`Login button text`** Text label of the login button that is used to trigger the OpenId  authentication manually.    &#x20;
* **`Single signon`** Tries to login automatically using existing OpenId credentials.&#x20;
* **`Security items default`** If Settings will be used by default for all [Open Id security items](/form-management/security/security-items/openid-connect.md) if no settings have been set on the security item.

{% hint style="danger" %}
If you turn single sign-on on make sure to first log with an OpenId account and assign this account admin privileges or [roles](/multi-user-management/roles.md) in ngSurvey from the [user](/multi-user-management/users.md) access control. &#x20;
{% endhint %}

{% hint style="info" %}
Using the auto-link property on [roles](/multi-user-management/roles.md) and [groups](/multi-user-management/groups.md) you can automatically map a role or a group to each new OpenId user that is connecting to ngSurvey.
{% endhint %}


---

# 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.ngsurvey.com/installation-setup/system-settings/openid-connect-settings.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.