Managing users in Hybrid Manager
Hybrid Manager (HM) uses Dex for user authentication in the HM console, acting as a proxy between HM and any native users or external user management systems (identity providers or IdPs) like LDAP and SAML.
During the initial bootstrapping of HM, an administrator sets up a native superuser for HM console access. Use this native superuser to sign in to the console for the first time.
For testing or demo environments, you can simplify operations by adding more native users as needed.
- See Creating native users for more information.
For assigning system roles to different users, HM uses a role-based access control (RBAC) model.
- See User roles and authorization for more information.
For production deployments, we strongly recommend configuring an external IdP like LDAP, SAML, or another supported connector. This ensures robust and secure user management. After configuring your chosen IdP and adding new administrators for the organization, disable the native user login.
- See Configuring an IdP for more information.
Managing native users
Create and manage additional native users for testing purposes or remove native users after configuring an IdP.
Configuring IdPs
Configure identity providers to manage your organization's users in production environments.
Applying modifications
Apply modifications to the Dex configuration to reconcile any changes to user-related parameters.
User roles and authorization
Discover what user roles are predefined for Hybrid Manager, what they allow access to, and how to assign them to users.
Could this page be better? Report a problem or suggest an addition!