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

Allowing securitytenant header #108

Open
avst-dmartino opened this issue Nov 22, 2021 · 2 comments
Open

Allowing securitytenant header #108

avst-dmartino opened this issue Nov 22, 2021 · 2 comments

Comments

@avst-dmartino
Copy link

avst-dmartino commented Nov 22, 2021

The header securitytenant is needed when requests need to set the header that governs what tenant an entity belongs to. In my case I am using metricbeat and I am trying to setup the dashboards on the global tenant in AWS ES.

@abutaha
Copy link
Owner

abutaha commented Mar 7, 2023

Can you please elaborate more on this? Where you face the error that requires this header? I haven't came across it yet.

@cpaton
Copy link

cpaton commented Feb 2, 2024

Just hitting this too. OpenSearch dashboards support multi-tenancy i.e. a single instance can support multiple tenants, and each tenant provides an isolated area of configuration for saved objects e.g. searches and index patterns.

When using the API to manage those saved objects there is a single endpoint for all tenants and you provide the header securitytenant to specify which one you want to target. Without including this header in the request it targets the Global tenant by default.

I've yet to find good documentation on the OpenSearch dashboards API and only came across this securitytenant header referred to on their forums e.g. https://forum.opensearch.org/t/saved-objects-kibana-api-from-tenant/9655

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants