Skip to content

fix: session end event's participants#58856

Merged
tigrato merged 1 commit intomasterfrom
tigrato/session-end-users
Sep 8, 2025
Merged

fix: session end event's participants#58856
tigrato merged 1 commit intomasterfrom
tigrato/session-end-users

Conversation

@tigrato
Copy link
Copy Markdown
Contributor

@tigrato tigrato commented Sep 8, 2025

Similarly to #58853, session's end events also showed inconsistencies in participant fiedls for different protocols.

This created an issue where root users couldn't watch session recordings they participated depending on the protocol, while some local users could.

Since ithe session's participants field is a repeated string, we can't apply the same logic as in #58853, so we need to transform the username prior to emitting the session end events. This will allow leaf users to see their recordings.

Fixes #12324
Fixes gravitational/teleport-private#166

Changelog: Fixed a bug that prevented root users from viewing session recordings when they were participants.

@github-actions github-actions bot added audit-log Issues related to Teleports Audit Log database-access Database access related issues and PRs desktop-access kubernetes-access size/sm labels Sep 8, 2025
@tigrato tigrato requested a review from zmb3 September 8, 2025 10:18
@tigrato tigrato force-pushed the tigrato/session-end-users branch from a1a17c0 to 3831fdb Compare September 8, 2025 11:41
@tigrato tigrato changed the title fix: session end events participants fix: session end event's participants Sep 8, 2025
Base automatically changed from tigrato/session-tracker-suers to master September 8, 2025 16:30
Similarly to #58853, session's end events also showed inconsistencies in
participant fiedls for different protocols.

This created an issue where root users couldn't watch session recordings
they participated depending on the protocol, while some local users
could.

Since ithe session's participants field is a repeated string, we can't apply the
same logic as in #58853, so we need to transform the username prior to
emitting the session end events. This will allow leaf users to see their
recordings.

Fixes #12324
Fixes teleport-private#166

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
@tigrato tigrato force-pushed the tigrato/session-end-users branch from 3831fdb to ad79b39 Compare September 8, 2025 16:53
@tigrato tigrato enabled auto-merge September 8, 2025 16:53
@tigrato tigrato added this pull request to the merge queue Sep 8, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 8, 2025
@tigrato tigrato added this pull request to the merge queue Sep 8, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 8, 2025
@tigrato tigrato added this pull request to the merge queue Sep 8, 2025
Merged via the queue into master with commit 8710815 Sep 8, 2025
41 of 42 checks passed
@tigrato tigrato deleted the tigrato/session-end-users branch September 8, 2025 19:44
@backport-bot-workflows
Copy link
Copy Markdown
Contributor

@tigrato See the table below for backport results.

Branch Result
branch/v18 Create PR

mmcallister pushed a commit that referenced this pull request Sep 22, 2025
Similarly to #58853, session's end events also showed inconsistencies in
participant fiedls for different protocols.

This created an issue where root users couldn't watch session recordings
they participated depending on the protocol, while some local users
could.

Since ithe session's participants field is a repeated string, we can't apply the
same logic as in #58853, so we need to transform the username prior to
emitting the session end events. This will allow leaf users to see their
recordings.

Fixes #12324
Fixes teleport-private#166

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

audit-log Issues related to Teleports Audit Log backport/branch/v18 database-access Database access related issues and PRs desktop-access kubernetes-access size/sm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Role for Restricted Access to Session Recordings not working on Leaf cluster

3 participants