Presentation Configuration

This guide covers how to create, manage, and configure presentation requests in EUDIPLO. Presentation configurations define what credentials and claims should be requested from users.

---

Configuration Structure

Example Presentation Configuration (PID):

{
  "id": "pid",
  "description": "Presentation ID",
  "dcql_query": {
    "credentials": [
      {
        "id": "pid",
        "format": "dc+sd-jwt",
        "meta": {
          "vct_values": [
            "<PUBLIC_URL>/credentials-metadata/vct/pid"
          ]
        },
        "claims": [
          {
            "path": [
              "address",
              "locality"
            ]
          }
        ]
      }
    ]
  },
  "registrationCert": {
    "body": {
      "privacy_policy": "https://example.com/privacy-policy",
      "purpose": [
        {
          "locale": "en-US",
          "name": "To register a new user"
        }
      ],
      "contact": {
        "website": "https://example.com/contact",
        "e-mail": "privacy@example.com",
        "phone": "+1234567890"
      },
      "credentials": [
        {
          "format": "dc+sd-jwt",
          "meta": {
            "vct_values": [
              "<PUBLIC_URL>/credentials-metadata/vct/pid"
            ]
          },
          "claims": [
            {
              "path": [
                "address",
                "locality"
              ]
            }
          ]
        }
      ]
    }
  },
  "webhook": {
    "url": "http://localhost:8787/consume",
    "auth": {
      "type": "apiKey",
      "config": {
        "headerName": "x-api-key",
        "value": "foo-bar"
      }
    }
  }
}

---

Configuration Fields

• id: REQUIRED - Unique identifier for the presentation configuration.
• description: REQUIRED - Human-readable description of the presentation. Will not be displayed to the end user.
• dcql_query: REQUIRED - DCQL query defining the requested credentials and claims following the DCQL specification
• registrationCert: OPTIONAL - Registration certificate containing legal and privacy information about the verifier. See Registration Certificate for details.
• webhook: OPTIONAL - Webhook configuration for receiving verified presentations asynchronously. See Webhook Integration for details.
• redirectUri: OPTIONAL - URI to redirect the user to after completing the presentation. This is useful for web applications that need to return the user to a specific page after verification.

Info

If no webhook is configured, the presentation result can be fetched by querying the /session endpoint with the sessionId.