-
Notifications
You must be signed in to change notification settings - Fork 178
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
[BUG] Dashboard not giving an option to select a tenant and defaultRoute does not seem to be in sync with default tenant (last selected tenant) #1261
Comments
[Triage] @peternied Would you please look into this issue and classify it accordingly? |
I don't see anything else that needs to happen here, but if there is wackiness due to this being stuck in a transfer queue please feel free to comment on the issue |
[Triage] @deepak-rsystems Thank you for filing this issue.
This is expected behavior by design. Users have still have an option to switch tenants by clicking on your avatar and choose the tenant they want to switch to.
@opensearch-project/security Can someone please look into this behavior? |
Hi @opensearch-project/security-dashboards-plugin team, |
@RyanL1997 I see you are assigned to it, but it was back in December so I doubt it is still accurate that you're working on this one. If you are not, could you please un-assign yourself so it is clear that this is up for grabs still? Thanks! |
Hi @opensearch-project/security-dashboards-plugin team, |
I will pick this up @davidlago, please assign me. |
Update: on 2.11.0 we're unable to disable global tenant, so I couldn't reproduce that error. // Edit |
Tested on 2.10.0 with:
results:
As said previously I'll compare with 2.4.0. |
Tested on 2.4.1 (Dashboard and OpenSearch) with the same results. @deepak-rsystems it's possible that I'm missing details about configuration. Can you please provide as simplest as it's possible configuration (or what was set) to reproduce that bug? |
@kajetan-nobel I think you were able to reproduce the bug, but couldn't acknowledge it. As per your last comments: Let me provide the problem description in simple words:
Expectation is to see the default route as per tenant "e911" which is the default tenant in this case. Another example, now take three tenants, "cadm", "e911" and "bmc" where "e911" is the default tenant (the last selected tenant). So when user logins now, it will see default route for tenant "bmc" but selected tenant is "e911" Let me know if its still not clear. |
@deepak-rsystems thank you for your quick reply! I've got a few questions:
So if I understood correctly those would be reproduction steps:
Second one:
Am I correct @deepak-rsystems? |
@kajetan-nobel Kindly check the definition of defaultRoute in the attached screenshot: So, default route is the landing page when you open OpenSearch Dashboards. |
@deepak-rsystems thank you for your response, I'm glad that we're on the same page, just wanted to be sure :). It looks like the amount of tenants also has an impact on the default route. CasesTested on version: 2.4.1 Side note: Expected behaviors are my proposal as solutions for unexpected behaviors. User contains only one available tenant after login
User contains more than one available tenant after login
The user changed the tenant
Summary: Default route is only used when an available tenant is only one. So it'll never be used when As I was debugging, and looking into that I found additional cases that are related, so decisions here will be needed |
Hey, @davidlago @peternied @cwperks I need feedback for this one if my proposes of expected behaviours are correct ones. |
Hi @opensearch-project/security-dashboards-plugin team, |
Describe the bug
We have multiple problems with dashboard access related to multi tenancy:
To Reproduce
Pre-requisites:
Steps to reproduce the behavior:
Expected behavior
OpenSearch Version
2.4.0
Dashboards Version
2.4.0
Plugins
No custom plugin enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: