Accounts in ADB ES
This article lists all accounts used in ADB Enterprise Services (ADB ES).
Linux users
The following accounts are created in an operating system during ADB ES installation. They are used to manage the corresponding services. Password authentication is disabled for these accounts.
| Account | Description |
|---|---|
adcm |
The user that is used by ADCM to deploy clusters |
adcc |
System user for the ADB Control services |
adbm |
System user for the ADBM services |
postgres |
Default PostgreSQL user. Created if the internal Database instance is used |
clickhouse |
Default ClickHouse user. Created if the internal ClickHouse instance is used |
Accounts in the ADB ES databases
The following accounts are created in the ADB ES databases.
| Account | Description | Password |
|---|---|---|
postgres |
A role in the PostgreSQL database, which is used in ADB Control to store information on queries (see Query DB). For external databases, the username can be changed in the Database service configuration parameters: External database parameters → Username |
The password is set in the Database service configuration parameters:
|
adcc |
A role that owns the |
Not set |
default |
The default account name in the ClickHouse database, which is used in ADB Control to store information on metrics (see Metrics DB). The username can be changed in the Clickhouse service configuration parameters. For an internal ClickHouse instance, the username can be changed only before the service installation. For an external ClickHouse instance, the username can be changed anytime |
The password is set in the Clickhouse service configuration parameters:
|
ADB Control UI user
The following user is created during ADB Control installation.
| Account | Description | Default password | How to change a password |
|---|---|---|---|
admin |
The ADB Control owner, which is used to work with ADB Control UI |
The default password is When you first log in to ADB Control, you will be prompted to change a password. For more information, see Connect to ADB Control and ADBM. A password is stored in the
|
You can change a password on the Users → Management tab in the ADB Control UI. For more information, see Edit a user |
ADB Control system users
The following users are service API accounts.
Information about them is stored in the adcc.system_user table of the ADB Control database.
They cannot be used to log in to the ADB Control UI.
| Account | Purpose | Password |
|---|---|---|
adcc |
To perform bundle operations in ADB Control |
ADB Control → UI component parameters → Service password If the password is changed after installation, run the Reconfigure and restart actions of the ADB Control service and of the ADBC agents service |
adbm |
To collect information about storage and cluster modifications that is displayed on the Audit page |
ADBM → Password for adbm system-user. If the password is changed after installation, run the Reconfigure and restart actions of the ADBM service and of the ADBM agents service |
adcm |
To register ADB clusters in ADB Control and ADBM. A user is created for each connected ADB cluster when the ADBC and ADBM agents are installed |
The password is imported from the If the |
ADBM API user
The following user is created during ADBM installation.
| Account | Description | Password |
|---|---|---|
adcc |
The user that is used for authentication in the ADBM CLI API |
Stored as plaintext in the /opt/adbm-server/auth.properties file. The password is updated when you change a password in ADBM → Password for adbm system-user. If the password is changed after installation, run the Reconfigure and restart actions of the ADBM service and of the ADBM agents service |
Monitoring user
The following user is created in Grafana during installation of the Monitoring service.
| Account | Description | Password |
|---|---|---|
admin |
Grafana administrator account used to access the Grafana web interface |
The password is set in the Monitoring service configuration parameters, in Grafana settings → Grafana administrator’s password. If the password is changed after the service installation, run the Reconfigure and restart action of the Monitoring service |
LDAP accounts in ADB Control
Refer to the LDAP authentication article to learn how to enable LDAP for ADB Control. To allow ADB Control to access the LDAP server, specify the LDAP account credentials in the ADB Control configuration parameters in the UI LDAP authentication → Login and Password fields.
If LDAP authentication is configured, you need to map user groups of the selected LDAP server to roles in ADB Control. You can manage it on the Users → LDAP group mapping tab in the ADB Control web interface. For more information, see Configure role mappings with LDAP groups.
|
IMPORTANT
After you assign the |
ADCM user
The following user is created during ADCM installation and is used to access the ADCM web interface.
| Account | Description | Default password | How to change a password |
|---|---|---|---|
admin |
ADCM administrator account |
admin |
After ADCM installation is complete, you can change the password in ADCM |