DEV Community

johnettagaweraks
johnettagaweraks

Posted on

OpenStack Horizon's exact-name zero hides the dashboard path

OpenStack Horizon's exact-name zero hides the dashboard path

OpenStack Horizon is the canonical dashboard for OpenStack. It gives tenants a web interface for provisioning and managing resources and gives administrators a management view. The browser may identify the service as "OpenStack Dashboard," a tenant name, a branded portal, or a generic login page. An exact search for "OpenStack Horizon" can therefore be less useful than the deployment path and identity flow.

The 2026-11-16 count-only observation used sub_type=all, page 1, and pagesize 1. app="OpenStack Horizon" returned 0, title="OpenStack Horizon" returned 0, and http.body="OpenStack Horizon" returned 96. Those counts do not measure the number of OpenStack clouds.

Query role Exact dork Observed total
Application fingerprint app="OpenStack Horizon" 0
Page title title="OpenStack Horizon" 0
HTTP body http.body="OpenStack Horizon" 96

The dashboard is an identity and authorization surface

OpenStack's security guide describes the dashboard as a self-service portal backed by the Identity service. Horizon itself is a Django application, and its deployment inherits Django security practices such as allowed hosts, secure cookies, CSRF protection, and authentication configuration.

The important inventory fields are the dashboard URL, Keystone endpoint, federation or local authentication method, allowed hosts, session backend, and administrator paths. A login page does not show which OpenStack services the tenant can reach or whether an administrator view is disabled.

Product branding varies

Horizon can be customized with site branding and deployed under a path such as /horizon/. A dashboard behind a proxy may return a generic login title. A documentation site may contain the full name without running Horizon.

The 96 body results are a lead set for checking URLs, headers, login forms, and paths. The zero exact-name observations show the weakness of those two labels, not the absence of Horizon deployments. Search planning should include configuration terms, static asset paths, and the expected authentication redirects, but every query must still be validated.

Separate tenant and administrator decisions

Tenant actions such as creating instances or changing security groups are sensitive. Administrator actions can alter quotas, users, networks, or service configuration. A dashboard should not assume that the login page protects both planes equally. Role checks belong in the backend services as well as Horizon.

Review whether federation metadata is current, whether session cookies are marked secure and HTTP-only, whether the application trusts proxy headers, and whether error pages reveal service endpoints. Test with designated accounts and a defined scope.

Use the selected body observation as a route clue

The body query is the only nonzero selected observation and supplies the link below. It should be treated as a candidate-discovery step. An organization can correlate those candidates with its own Keystone endpoints and dashboard hostnames, then validate the actual response.

The operational lesson is that an OpenStack dashboard is identified by its role in a cloud control plane, not by a two-word title match. A zero on the exact name can coexist with a well-used dashboard. Asset records should follow the identity provider, the dashboard URL, and the services it can reach.

References

Top comments (0)