> For the complete documentation index, see [llms.txt](https://engineering-ing-inf-rd.gitbook.io/true-connector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering-ing-inf-rd.gitbook.io/true-connector/advanced-configuration/identityproviders.md).

# Supported Identity Providers

Since Identity provider is disabled by default, in order to enable it, set following application.property to true:

```
application.isEnabledDapsInteraction=true

```

The TRUE Connector is able to interact with the following Identity Providers: For each of 3 supported identity providers, you need to obtain certificate, in order to be able to get JWToken from DAPS server. Certificate needs to be copied into *ecc\_cert* folder and modify *DAPS\_KEYSTORE\_NAME*, *DAPS\_KEYSTORE\_PASSWORD* and *DAPS\_KEYSTORE\_ALIAS* in *.env* file, for both Provider and Consumer section..

* **AISECv2** (default configuration)additional step: edit *application-docker.properties* and modify *application.dapsVersion=v2* and *application.dapsUrl* should point to DAPS v2 server
* **ORBITER** put the certificates (private and public key) in the *ecc\_cert* folder, edit related settings (i.e., *application.daps.orbiter.privateKey*, *application.daps.orbiter.password*) and set the *application.dapsVersion* (in the *application-docker.properties*) to *orbiter* *application.dapsUrl* should point to Orbiter IDP server

DAPS related configuration can be achieved by modifying following (.env file). Following snippet is just an example:

```
PROVIDER_DAPS_KEYSTORE_NAME=daps-keystore-provider.p12
PROVIDER_DAPS_KEYSTORE_PASSWORD=password
PROVIDER_DAPS_KEYSTORE_ALIAS=1
```

and/or

```
CONSUMER_DAPS_KEYSTORE_NAME=daps-keystore-consumer.p12
CONSUMER_DAPS_KEYSTORE_PASSWORD=password
CONSUMER_DAPS_KEYSTORE_ALIAS=1
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://engineering-ing-inf-rd.gitbook.io/true-connector/advanced-configuration/identityproviders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.