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:

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:

{
  "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:

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

1. A Participant-issued token contains the correct values when the relevant scopes are requested.

2. After federated login to the Data Space Operator, the Data Space Operator shadow user receives the same values.