Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some members with Github as Auth Provider could not be shown in cluster member list #44907

Closed
gaktive opened this issue Mar 11, 2024 · 4 comments
Assignees
Labels
area/authentication JIRA To be used in correspondence with the internal ticketing system. kind/bug Issues that are defects reported by users or that we know have reached a real release priority/2 team/collie the team that is responsible for auth and rbac within rancher
Milestone

Comments

@gaktive
Copy link
Member

gaktive commented Mar 11, 2024

Internal reference: SURE-7818
Reported in 2.7.9

Some members (Auth Provider=Github) could not be shown in cluster member list.

The user exists on Github Enterprise and the user exists on the list under Add Cluster Member but not when using the filter string upon typing within the Select Member textbox.

@gaktive gaktive added [zube]: To Triage JIRA To be used in correspondence with the internal ticketing system. kind/bug Issues that are defects reported by users or that we know have reached a real release and removed [zube]: To Triage labels Mar 11, 2024
@richard-cox
Copy link
Member

We need to confirm if the expected results are in the response to /v3/principals?action=search. If not the auth team will need to triage

@eva-vashkevich
Copy link
Member

eva-vashkevich commented Mar 22, 2024

Hi, I've checked results from /v3/principals?action=search and they do not contain correct results. The result I am getting contains a user, which is not part of the allowed orgs, but does not contain teams I have added. The search string we are passing is correct. Looks like it is a BE problem, as mentioned by Richard. The original JIRA issue is with the Authentication Provider team, but it hasn't been triaged.

@gaktive
Copy link
Member Author

gaktive commented Mar 22, 2024

Transferring to rancher/rancher cc @Jono-SUSE-Rancher

@gaktive gaktive transferred this issue from rancher/dashboard Mar 22, 2024
@gaktive gaktive added this to the v2.9-Next1 milestone Mar 22, 2024
@eva-vashkevich eva-vashkevich removed their assignment Mar 25, 2024
@samjustus samjustus modified the milestones: v2.9-Next1, Unscheduled Mar 27, 2024
@samjustus samjustus added team/collie the team that is responsible for auth and rbac within rancher area/authentication labels Mar 27, 2024
@samjustus samjustus modified the milestones: Unscheduled, v2.9-Next1 Apr 25, 2024
rohitsakala pushed a commit to rohitsakala/rancher that referenced this issue May 13, 2024
rohitsakala pushed a commit to rohitsakala/rancher that referenced this issue May 14, 2024
@nickwsuse
Copy link
Contributor

nickwsuse commented Jun 5, 2024

Verified on v2.9-head ID: fd73f43

  1. Fresh Install | v2.9-head | Org/Team/User Search
  2. Fresh Install | v2.9-head | Team Access
  3. Fresh Install | v2.9-head | Nested Memberships
  4. Fresh Install | v2.9-head | Enable two (or more) orgs in GH provider
  5. Upgrade | v2.8.4 → v2.9-head | GH Auth Enabled Before Upgrade | Org/Team/User Search
  6. Upgrade | v2.8.4 → v2.9-head | GH Auth Enabled Before Upgrade | Team Access
  7. Upgrade | v2.8.4 → v2.9-head | GH Auth Enabled Before Upgrade | Nested Memberships
  8. Upgrade | v2.8.4 → v2.9-head | Enable two (or more) orgs in GH provider

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/authentication JIRA To be used in correspondence with the internal ticketing system. kind/bug Issues that are defects reported by users or that we know have reached a real release priority/2 team/collie the team that is responsible for auth and rbac within rancher
Projects
None yet
Development

No branches or pull requests

6 participants