> 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/identity-provider/getting-started.md).

# Getting started

The Identity Provider role is fulfilled by a legal entity whose tooling identifies and authenticates entities (humans or machines). An Identity Provider:

* Provides identifiers for humans;
* Issues credentials (i.e. a password or electronic keycard) to humans;
* Identifies humans to Service Providers based on this information.
* Holds information on authorisations of humans representing a Service Consumer; i.e. information indicating which humans are authorised to act on a Service Consumer's behalf.
  * If a human is authorised to represent multiple Service Consumers, the Identity Provider is expected to provide a list from which the human must select the Service Consumer it wants to represent.
* Can check whether a human representing a legal entity is authorised to receive the service;
* Can confirm this authorisation to the Service Provider.

As a result, Service Providers can outsource the identification and authentication of humans, as well as tasks related to managing the authorisations and delegation information of humans, to an Identity Provider instead of implementing their own tooling.

The iSHARE specifications do not include requirements for user logout. Identity Providers may provide a logout mechanism that Service Providers can trigger when a users requests to logout from the Service Provider, for example with OpenID Connect RP-Initiated logout.

To double-check if required endpoints are implemented, please use the following list as a cheat sheet:

Identity Provider

* [ ] [Access Token (M2M)](/version-3.0/all-roles-common-endpoints/access-token-m2m.md)
* [ ] [Capabilities](/version-3.0/all-roles-common-endpoints/capabilities.md)
* [ ] [Authorize](/version-3.0/identity-provider/authorize.md)
* [ ] [Login](/version-3.0/identity-provider/login.md)
* [ ] [Access Token (H2M)](/version-3.0/identity-provider/access-token.md)
* [ ] [User Info](/version-3.0/identity-provider/user-info.md)


---

# 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/identity-provider/getting-started.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.