> 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-operator.md).

# User Claims Assignment for Data Space Operator

The Data Space Operator OIDC provider exposes OE claims through scope mappings. For local Operator users, the authoritative values are stored under the user's Authentik `attributes` object.

The repository defines the following OE attributes:

| User attribute | OAuth scope mapping             | Purpose                                             |
| -------------- | ------------------------------- | --------------------------------------------------- |
| `orgId`        | `oe-organizationId`             | Organization identifier                             |
| `walletId`     | `oe-walletId`                   | Wallet identifier                                   |
| `signerServer` | `oe-signerServer`               | Signer Server URL                                   |
| `wellKnownUrl` | `oe-wellKnownUrl`               | OE well-known URL                                   |
| `upstream_idp` | `oe-central-federated_identity` | Upstream source identifier for federated identities |

For a **Data Space Operator user**, assign the first four values according to the Operator's deployed organization and service endpoints. `upstream_idp` is primarily populated for federated shadow users and should not be invented for a normal **Data Space Operator** account.

Example user attributes structure:

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

If the invitation form supports fixed context, the equivalent invitation data can be represented as:

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

The  `oe-save-user-attributes` policy used for `oe-enrollment-invitation` saves these values to the pending user when the corresponding values are available in the enrollment flow context.

### Verification

1. Open the newly created user in the Authentik administration interface.
2. To see property mappings responsible for generating JWT claims, accesses Customization from Authentik User Interface connected as Authentik Admin:

<figure><img src="https://1789397093-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH0zpgrXbeZ7u6UuCV9Gz%2Fuploads%2F7esi8lasJet9yTyIJDG7%2FScreenshot%202026-09-07%20at%2022.39.45.png?alt=media&amp;token=11417ce1-1675-4935-a7e9-4435131facda" alt=""><figcaption></figcaption></figure>

3. Verify that all required Operator values are present and are not blank. Users stored within Data Space Operator Authentik - User Directory will have assigned these 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%2FjOMB5XOpbFR9lgpHRuuD%2FScreenshot%202026-09-07%20at%2022.41.09.png?alt=media&amp;token=5dbfab6f-0287-49f2-bb7c-b24c85200f97" alt=""><figcaption></figcaption></figure>

4. Authenticate to an OE application that requests the corresponding scopes.
5. Inspect the resulting token and verify that the expected claims are emitted.


---

# 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-operator.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.