The Admin> Authentication screen allows users with Operator Basic, Operator, and Admin permission to view the Greenplum Database host-based authentication file, pg_hba.conf
.
Users with Admin permission can add, remove, change, and move entries in the file. The Command Center UI validates entries to ensure correct syntax. Previous versions of the file are archived so that you can restore an earlier version or audit changes.
See Authentication Options for an overview of user authentication options for Greenplum Database and Greenplum Command Server.
See Configuring Client Authentication in the Greenplum Database Administrator Guide for a detailed description of the contents of the pg_hba.conf
file.
Choose Admin>Authentication to display the content of the Greenplum Database pg_hba.conf
file.
The pg_hba.conf
file contains a list of entries that specify the characteristics of database connection requests and authentication methods. When Greenplum Database receives a connection request from a client, it compares the request to each entry in the pg_hba.conf
entry in turn until a match is found. The request is authenticated using the specified authentication method and, if successful, the connection is accepted.
Command Center users with the Admin permission can edit the pg_hba.conf
file. Note that any changes you make are lost if you move to another screen before you save them.
#
from the Type
list.#
) at the beginning of the entry.When you select Save and Update, the pg_hba.conf
file is saved and refreshed in Greenplum Database. Note that existing client connections are unaffected.
When you save a new version of the pg_hba.conf
file, a copy is saved in the Greenplum Database $MASTER_DATA_DIRECTORY/pg_hba_archive
directory as pg_hba.conf-<timestamp>
.
To view an archived version of the pg_hba.conf
file, click Load versions… and click the timestamp for the version to display.
To revert to a previous version of the file, load the previous version and then click Save config and update GPDB. The configuration is refreshed in Greenplum Database and saved as a new version in the archive directory.