OpenZiti Console is a management plane for identities and policy
The Ziti Admin Console, also called ZAC, is the graphical interface for an OpenZiti network. The Controller configuration documentation separates the edge-management API from other controller functions. That API allows remote administration of identities, policies, authentication, and edge components. The identity documentation says tokens can be downloaded through the Ziti Admin Console and treats an identity configuration file as a durable credential.
For an asset inventory, the console is not just another login page. It is a place from which an authorized administrator can create or remove identities, change access policy, and obtain identity material. A reachable console can be a useful discovery target even when the network uses a strong overlay model. The controller and the console's own authentication path determine whether that visibility matters.
OpenZiti supports external identity providers for ZAC. The external-auth guides require the identity provider to allow the console's callback URL and specify an audience for the controller API. A misconfiguration can make login fail, or it can grant a session whose audience and role mapping do not match the intended administrator group. Review configuration, not only a successful login page.
Query plan
Use app="OpenZiti" as a broad product candidate and title="Ziti Admin Console" as the narrower title candidate. Both use sub_type=all, page 1, and page size 1. The application query can include overlay components that are not the console. The title query can be missed when an organization customizes the page. The live counts are not available because the authorized ZoomEye execution was rejected in this run.
Do not treat a match as a controller or an enrollment endpoint without verification. A ZAC page, a controller API, and an edge router are different services with different authority. Query results should be labeled with the surface that was actually observed.
Review identity and controller authority
List administrator identities and their authentication methods. Check certificate, password, external JWT, and OIDC paths separately. Confirm that the administrator role is mapped to the intended IdP group and that a newly authenticated but unauthorized user cannot create identities or policies.
Review the controller's edge-management listener. It should be reachable only from the console path and the administrative networks that need it. If the management API is exposed directly, test that the endpoint enforces the same identity and authorization model as the console. Do not use an unauthenticated request to infer the result.
Audit identity enrollment tokens and downloaded identity files. A token can bootstrap a durable identity, so its issuance, delivery, expiration, and revocation need a record. Store enrollment material in a secret manager or a controlled one-time channel. Remove unused identities and rotate certificates according to the network's policy.
Reduce the console blast radius
Use a separate administrative identity for the console, with multi-factor authentication at the identity provider. Put ZAC behind a management network or identity-aware proxy and restrict its callback URLs to the intended hostnames. Review external OIDC role mapping when the IdP changes group names or token claims.
Monitor console logins, identity creation, policy changes, and enrollment-token use. Keep controller logs and IdP logs together during an investigation. A console access event without a corresponding admin identity claim may indicate a misconfigured provider or a stolen session.
Respond to an unexpected console
Confirm ownership through DNS, controller configuration, and cloud records. Do not download an identity token from an unknown console. If the host is yours, review the controller's admin identities and recent policy changes before disabling access. If it is not yours, preserve the evidence and avoid interacting with the management interface.
OpenZiti's value is that the management plane can be kept off the public network. The console must be treated as an authority plane, not a harmless status page. The query finds candidates; the identity and enrollment model decides the response.
Top comments (0)