> For the complete documentation index, see [llms.txt](https://dev.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ishare.eu/version-3.0/reference/authentication/get-trusted-ca-list.md).

# Get trusted CA List

Every iSHARE request must be signed with a certificate issued by a Certificate Authority (CA) on the iSHARE trusted list. Participants can retrieve this list via the **`/trusted_list`** endpoint. The trusted list consists of CAs of qualified Trust Service Providers (currently eIDAS issuers). The receiver of a signed request is responsible for verifying that the signer’s certificate chains to a CA from this list.

### Steps to Follow

**1.1 Create client assertion**\
The Service Provider creates a signed JWT client assertion to authenticate with the Participant Registry’s token endpoint.

**1.2 Request access token (`GET/POST /connect/token`)**\
The Service Provider sends the client assertion to the Participant Registry’s OAuth token endpoint to obtain an access token.

**1.3 Receive access token (`200 OK`)**\
The Participant Registry returns an access token (JWT).

**1.4 Request trusted list (`GET /trusted_list`)**\
The Service Provider calls the Participant Registry’s `/trusted_list` endpoint with the bearer token.

**1.5 Receive trusted CAs (`200 OK`)**\
The Participant Registry returns the trusted CA list (typically in an iSHARE-signed JWT).

<figure><img src="https://1961974616-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhIVZwp4ZxhYhb39SlKH3%2Fuploads%2Fgit-blob-54e1c98ad0519b98ee79fc636d817fb6efe60264%2Fget-trusted-CA-list.png?alt=media&amp;token=e974446d-6bf3-4e81-b958-f58f66bf5257" alt=""><figcaption><p>Get a list of trusted CA's from the /trusted_list capabilities endpoint</p></figcaption></figure>


---

# 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://dev.ishare.eu/version-3.0/reference/authentication/get-trusted-ca-list.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.