> For the complete documentation index, see [llms.txt](https://docs.oceanenterprise.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanenterprise.io/operational-guidelines/user-directory-management/user-enrolment-in-authentik/create-an-invitation/user-claims-assignment-for-data-space-participant.md).

# User Claims Assignment for Data Space Participant

The Data Space Participant Authentik blueprint exposes the same four OE business claims:

* `orgId`;
* `walletId`;
* `signerServer`;
* `wellKnownUrl`.

For a Participant user, these values must identify the Participant organization and Participant services, not the Data Space Operator services.

Example user attributes structure:

```yaml
orgId: <participant-organization-id>
walletId: <participant-wallet-id>
signerServer: <participant-signer-server-url>
wellKnownUrl: <participant-well-known-url>
```

Equivalent invitation context, when supported by the deployed Authentik invitation form:

```json
{
  "orgId": "<participant-organization-id>",
  "walletId": "<participant-wallet-id>",
  "signerServer": "<participant-signer-server-url>",
  "wellKnownUrl": "<participant-well-known-url>"
}
```

The Participant provider maps these user attributes into the corresponding OIDC claims. When the Participant is federated with the Data Space Operator, the Operator source-property mapping copies these upstream values into the Operator shadow user's attributes.

### Verification

1. The Participant user contains all attributes from **Directory → Users → `<user>` → Custom Attributes** or **Directory → Users → `<user>` → Edit User → Advanced settings → Attributes**:

<figure><img src="https://1789397093-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH0zpgrXbeZ7u6UuCV9Gz%2Fuploads%2F4NcNjZg5j54bRZfxfbFX%2FScreenshot%202026-09-08%20at%2002.50.04.png?alt=media&amp;token=75ae0cf0-1cdf-4237-b543-d487cfab8e29" alt=""><figcaption></figcaption></figure>

2. The Participant OIDC provider includes the OE scope mappings.

<figure><img src="https://1789397093-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH0zpgrXbeZ7u6UuCV9Gz%2Fuploads%2FmxrrJSpzUK2FBut3IIwv%2FScreenshot%202026-09-08%20at%2002.47.33.png?alt=media&amp;token=ed5ecc2f-0a01-427d-a2e5-8ca65ec7915d" alt=""><figcaption></figcaption></figure>

3. A Participant-issued token contains the correct values when the relevant scopes are requested.
4. After federated login to the Data Space Operator, the Data Space Operator shadow user receives the same values.


---

# 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.oceanenterprise.io/operational-guidelines/user-directory-management/user-enrolment-in-authentik/create-an-invitation/user-claims-assignment-for-data-space-participant.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.
