Sessions Management

EUDIPLO manages sessions for credential issuance and verification, bound to each tenant. When using the Interactive Authorization Endpoint (IAE), the session tracks the multi-step authorization flow, including completed steps and collected data. Sessions are stored in the database and can be managed via the /api/sessions endpoint. You can retrieve a specific session via /api/sessions/{id}.

Session Cleanup

To tidy up old sessions, an interval is set to clean up older sessions. The cleanup behavior can be configured both globally (via environment variables) and per-tenant (via the Session Config API or the client UI).

Other elements like persisted status mapping (the binding between a session ID and a status list reference) are not deleted with this process.

OID4VP Security Fields

For OID4VP presentation sessions, EUDIPLO stores additional fields that implement the security model defined in OID4VP §13.3:

Field	Type	Description
walletNonce	string \| null	Wallet-facing identifier used as state in the authorization request. Separates the wallet's view of the session from the internal session.id, preventing cross-reference attacks.
responseCode	string \| null	One-time code generated when the wallet submits its response. Appended to the redirect_uri for same-device flows to prevent session fixation on redirect.

These fields are populated automatically when a presentation request is created and are not exposed through the session management API. They exist solely for the OID4VP protocol flow.

For details on how these fields are used in practice, see Credential Presentation — Direct Post Security Model.

Cleanup Modes

EUDIPLO supports two cleanup modes:

• Full (default): Deletes the entire session record from the database.
• Anonymize: Keeps session metadata (ID, original status, timestamps) but removes personal data including credentials, credential payloads, auth queries, offers, and request objects.

Anonymize mode is useful for audit and compliance scenarios where you need to retain evidence that a session occurred without storing personal data. The original session status is preserved, so historical statistics remain accurate. For real-time monitoring, see the Monitoring Guide.

Per-Tenant Configuration

Each tenant can override the global session settings via the /session-config endpoint or through the client UI under Session Management > Session Config.

For the full API specification, see the Session Config API.

Configuration Options

Field	Type	Description
ttlSeconds	number	Time-to-live in seconds (minimum 60). Omit to use global default.
cleanupMode	string	Either full or anonymize. Omit to use global default.

Session Logs

Session flow events (e.g. flow start, credential issuance, token exchange, errors) can optionally be persisted to the database per session. This is controlled by the LOG_SESSION_STORE environment variable — see Logging Configuration for details.

When enabled, logs are available via GET /api/session/{id}/logs and are visible in the Web Client under the Logs tab on the session detail page. The tab only appears when log entries exist for the session.

Global Configuration

The global defaults are configured via environment variables:

Key	Type	Notes
SESSION_TIDY_UP_INTERVAL	number	Interval in seconds to run session tidy up (default: 3600)
SESSION_TTL	number	Default time to live for sessions in seconds. Can be overridden per tenant. (default: 86400)
SESSION_CLEANUP_MODE	string	Default cleanup mode when sessions expire. 'full' deletes the entire session, 'anonymize' keeps metadata but removes personal data. Can be overridden per tenant. (default: full)