Unified Portal ZHera
Unified Portal ZHera
ZHera is the unified entry component of the ZCF platform. It provides single sign-on, unified navigation, and cross-product resource views for enterprise users across multiple product lines. With ZHera, operators can manage ZStack Cloud, ZSphere, ZStone, ZBS, ZSN, and other products from one interface without switching between consoles.
Single Sign-On (SSO)
ZHera integrates single sign-on based on OAuth 2.0 / OIDC and supports existing enterprise LDAP, Active Directory, and mainstream identity providers. After signing in once, users can access all authorized product modules without repeated authentication.
- LDAP / AD account integration
- SAML 2.0 / OIDC support
- Optional multi-factor authentication (MFA)
- Configurable session timeout and forced logout policies
Permissions and Multi-Tenant Management
ZHera provides a fine-grained RBAC model and supports permission policies across global, project, and resource scopes.
| Role | Scope | Scenario |
|---|---|---|
| Platform admin | All platform resources | IT operations team |
| Project admin | All resources in a specified project | Business owner |
| Standard user | Authorized resource objects | Development/test users |
| Read-only user | View only, no operations | Audit/monitoring users |
In multi-tenant mode, resources, networks, and quotas are fully isolated between tenants.
Dashboard and Alert Center
ZHera provides customizable operation dashboards with drag-and-drop layouts and multiple chart types such as line charts, pie charts, and heat maps. The alert center aggregates alerts from sub-products and displays, processes, and archives them in ZHera.
The dashboard refresh interval is configurable, defaults to 30 seconds, and supports large-screen mode for NOC monitoring rooms.
OpenAPI and Integration
ZHera exposes complete REST APIs covering user management, permission configuration, resource queries, and other operations for integration with internal CMDB, ITSM, and automation platforms.
APIs are described with OpenAPI 3.0 and can be debugged online through the built-in API Explorer. All API calls support token-based authentication, including API Key and OAuth 2.0 Client Credentials modes.