Repository navigation
Conversation
…e the same user pam project extend and pam project import linked the launch credential via TunnelDAG.link_user_to_resource() on a TunnelDAG loaded before the admin was written via configure_resource. On that stale graph link_user() writes a fresh ACL edge with only belongs_to/is_launch_credential, replacing the edge and dropping is_admin when the admin and launch credential are the same pamUser. Use TunnelDAG.set_launch_credentials(), which sends adminUid with connectUsers in one configure_resource call and keeps is_admin in its local follow-up write. Adds unit-tests/pam/test_pam_same_admin_launch_credential.py.
rporter92
marked this pull request as ready for review
October 6, 2026 22:20
idimov-keeper
self-requested a review
October 7, 2026 16:13
idimov-keeper
approved these changes
Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…e the same user
pam project extend and pam project import linked the launch credential via TunnelDAG.link_user_to_resource() on a TunnelDAG loaded before the admin was written via configure_resource. On that stale graph link_user() writes a fresh ACL edge with only belongs_to/is_launch_credential, replacing the edge and dropping is_admin when the admin and launch credential are the same pamUser.
Use TunnelDAG.set_launch_credentials(), which sends adminUid with connectUsers in one configure_resource call and keeps is_admin in its local follow-up write.
Adds unit-tests/pam/test_pam_same_admin_launch_credential.py.