OpenSearch Dashboards tenancy is not backend authorization
OpenSearch Dashboards tenants look like separate workspaces. Users see saved objects in the global tenant, a private tenant, or custom tenants assigned to their roles. That separation is useful, but it does not move the data. Every saved object and query is still handled by the OpenSearch cluster through the Dashboards server identity.
The security documentation describes the global tenant as shared by every Dashboards user, the private tenant as exclusive to one user, and custom tenants as role-controlled spaces. It also describes the securitytenant header as part of multi-tenancy. Dashboards must be configured to allow that header to reach OpenSearch together with the standard Authorization header. The header informs tenant context. It is not a replacement for a role mapping that allows the user to read the underlying index.
The common mistake is to treat the Dashboards UI as the whole security boundary. An analyst who cannot see an index pattern in one tenant may still be able to call the OpenSearch REST API, use a client certificate, or reach another proxy path with the same backend credentials. Tenant names also appear in URLs, which makes it tempting to test another tenant by changing a parameter. The backend role model has to reject that request even when the caller knows the name.
A second mistake is making the Dashboards server user too powerful. The server account needs enough access to write saved objects and perform routine discovery. If it is also allowed to read every index and change security configuration, a flaw in the front end or a proxy trust mistake can become cluster-wide access. Keep the server identity narrow. Keep human identities separate. Test the direct API with the same credentials users receive.
Multi-tenancy should be treated as a presentation and collaboration boundary. Data authorization remains in the cluster. Start from the reporting user's effective roles, then verify index permissions, document-level security, field-level security, and tenant access independently. A user with access to a custom tenant should not automatically gain access to every index referenced by a dashboard saved there.
Useful checks include calling the security account information endpoint with a test user, reading an assigned tenant, attempting a tenant not assigned to the user, and querying each protected index directly. Repeat the checks through every public ingress path. If a dashboard is embedded in another portal, test the identity forwarded by that portal rather than assuming the outer login is sufficient.
Operators should also review the default tenant. If global is the default and it is broadly available, teams may publish dashboards and index patterns there without understanding the audience. Set the default deliberately, disable tenants that have no owner, and make custom tenants part of the access review.
The tenant selector organizes saved work. OpenSearch roles decide which data can be read. They are related controls, and neither one substitutes for the other.
Top comments (0)