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

[v2.10] After logging in via LDAP auth provider extensions do not load #13500

Open
github-actions bot opened this issue Feb 25, 2025 · 0 comments
Open
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Milestone

Comments

@github-actions
Copy link
Contributor

This is a backport issue for #13499, automatically created via GitHub Actions workflow initiated by @richard-cox

Original issue body:

Setup

  • Rancher version: v2.10.2
  • Rancher UI Extensions: Range of prime based extensions

Describe the bug

  • After logging in using LDAP extensions are not loaded
  • In logged in though, on refresh, they are

To Reproduce

  • Setup an LDAP auth provider
  • Install element or observability extensions
  • Log out
  • Log in again

Result

  • extensions have not loaded, no side nav icon for extension

Expected Result

  • extensions have loaded, side nav icon for extension is showing
@github-actions github-actions bot added kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None labels Feb 25, 2025
@github-actions github-actions bot added this to the v2.10.3 milestone Feb 25, 2025
@richard-cox richard-cox modified the milestones: v2.10.3, v2.10.4 Feb 25, 2025
@richard-cox richard-cox changed the title [backport v2.10.3] After logging in via LDAP auth provider extensions do not load [v2.10] After logging in via LDAP auth provider extensions do not load Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Projects
None yet
Development

No branches or pull requests

2 participants