GHSA-gj7p-595x-qwf5 Data Sharing Framework is Missing Session Timeout for OIDC Sessions

• Maven dev.dsf:dsf-common-jetty: < 2.1.0 (no fix yet) • Maven dev.dsf:dsf-fhir-server: < 2.1.0 (no fix yet) • Maven dev.dsf:dsf-bpe-server: < 2.1.0 (no fix yet)

Affected Components DSF FHIR Server with enabled OIDC authentication. DSF BPE Server with enabled OIDC authentication. Summary OIDC-authenticated sessions had no configured maximum inactivity timeout. Sessions persisted indefinitely after login, even after the OIDC access token expired. Impact If a user logs in via OIDC and leaves their browser without explicitly logging out, the session remains valid indefinitely. Another person using the same browser can access the DSF UI with the previous user's permissions. This is a realistic threat in hospital environments with shared workstations. Only affects OIDC browser sessions, not relevant for mTLS machine-to-machine communication. Fix (commits f4ecb00, 7d25fea) • Added configurable session timeout via `dev.dsf.server.auth.oidc.session.timeout` (default: `PT30M`). • Enabled `logoutWhenIdTokenIsExpired(true)` in OpenID configuration to tie session lifetime to token lifetime. • Websocket sessions are now closed with `VIOLATED_POLICY` when credentials expire, prevents stale websocket connections from continuing to receive events after session timeout.