Livio Spring 9ec9ad4314 feat(oidc): sid claim for id_tokens issued through login V1 (#8525) ... # Which Problems Are Solved id_tokens issued for auth requests created through the login UI currently do not provide a sid claim. This is due to the fact that (SSO) sessions for the login UI do not have one and are only computed by the userAgent(ID), the user(ID) and the authentication checks of the latter. This prevents client to track sessions and terminate specific session on the end_session_endpoint. # How the Problems Are Solved - An `id` column is added to the `auth.user_sessions` table. - The `id` (prefixed with `V1_`) is set whenever a session is added or updated to active (from terminated) - The id is passed to the `oidc session` (as v2 sessionIDs), to expose it as `sid` claim # Additional Changes - refactored `getUpdateCols` to handle different column value types and add arguments for query # Additional Context - closes #8499 - relates to #8501		2024-09-03 13:19:00 +00:00
..
eventsourcing/model	refactor(fmt): run gci on complete project (#7557)	2024-04-03 10:43:43 +00:00
view	feat(oidc): sid claim for id_tokens issued through login V1 (#8525)	2024-09-03 13:19:00 +00:00