Accounts in ADB
This article lists all accounts that are used in Arenadata DB.
Linux users
The following accounts are created in an operating system during ADB installation (/etc/passwd).
| Account | Description | Default password |
|---|---|---|
adcm |
The user that is used by ADCM to deploy clusters |
Not set |
gpadmin |
The Linux user for ADB that is needed to start/stop a cluster and run all console utilities.
The user has access to all cluster databases as a superuser (with the |
Not set |
abrt |
The user for autocoredump. Assigned |
Not set |
pxf |
The user for PXF. Assigned |
Not set |
etcd |
The user for etcd. No login abilities |
Not set |
|
NOTE
During the Install, Upgrade, Reinstall, Expand, and Move Host Segment cluster actions, the bundle overwrites the ~/.ssh/authorized_keys file of the |
Arenadata DB roles
The following accounts are created in the Arenadata DB database during ADB installation (via the CREATE ROLE command).
| Account | Description | Default password | How to change a password |
|---|---|---|---|
gpadmin |
The ADB cluster administrator. This role has access to all cluster databases as superuser |
For local and remote connections, the password is not required by the default rules in pg_hba.conf |
Via the
There is no ability to set/change a password via ADCM |
gpmon |
The |
It is stored in the /home/gpadmin/.pgpass file |
|
adcc |
The role is used by ADB Control for connecting to ADB if ADB ES is used. Such access is required to obtain information about the cluster topology and to cancel requests initiated by users. The username can be changed in the ADB Control configuration parameters during the initial ADB Control installation. Cannot be changed later |
Not set |
Cannot be set |
Monitoring user
The following user is created in Grafana during monitoring installation.
| Account | Description | Default password | How to change a password |
|---|---|---|---|
admin |
Grafana administrator, which is used for cluster monitoring |
No default. You should set a password in the Monitoring service configuration parameters |
|
ADCM user
The following user is created during ADCM installation.
| Account | Description | Default password | How to change a password |
|---|---|---|---|
admin |
ADCM admin |
admin |
After ADCM installation is complete, you can change a user password in the ADCM web UI. For more information, see Check the ADCM web-interface |
LDAP accounts
When configuring LDAP authentication, you need to enter and store LDAP admin accounts. Passwords are stored as plaintext in specific files that should be secured with OS file permissions.
LDAP authentication in ADB is configured according to the LDAP authentication in ADB article. To specify the LDAP admin account and its password, fill in the SA Login and Password fields on the ADB configuration page.
LDAP credentials are stored in the following file on the ADB master host: $MASTER_DATA_DIRECTORY/pg_hba.conf.
File permissions:
-rw-r----- 1 gpadmin gpadmin
Synchronization of ADB users and groups with LDAP is performed automatically via the pg-ldap-sync utility. For more information, see Synchronize ADB and LDAP.
|
IMPORTANT
After syncing with the LDAP server, two ADB local roles are still required since they cannot be replaced with LDAP users (see Arenadata DB roles):
All other users (including superusers) can be controlled via the LDAP server. |