-
Notifications
You must be signed in to change notification settings - Fork 159
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] multitenancy disabled still makes calls for tenancy #1764
Comments
@derek-ho was this addressed with your recent changes? |
I don't think so, but let me try to reproduce |
@kavilla I was not able to reproduce the bug. I believe we are already hiding that call behind the config's value for multi tenancy enabled here: https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/plugin.ts#L178. Can you share more detailed reproduction steps? Were you switching this value from true to false? I believe @cwperks said that a reboot of OSD is needed when this value changes. Are you able to reproduce this on |
I'm getting the same issue with multi tenancy enabled, step to reproduce:
|
What is the bug?
On start up, https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/plugin.ts#L191 calls out to get tenant info. But if I do not have tenancy enabled on my cluster and disable multitenancy in my config with
opensearch_security.multitenancy.enabled: false
, I get a403
on start up and OSD crashes for example:What is the expected behavior?
OSD does need to make a call out to get tenant info if multitenancy is disabled. To further expand there is a configuration:
migrations.skip
that skips the migration process on the.kibana
index. I believe that migrations call should also respect this configuration.The text was updated successfully, but these errors were encountered: