Create a Pivotal Greenplum record in order to authenticate to a Greenplum database instance running on a Unix host, and scan it for compliance. Unix authentication is required so you'll also need a Unix record for the host running the database.
This record type is only available in accounts with PC or SCA and is only supported for compliance scans.
For the most current list of supported authentication technologies and the versions that have been certified for VM and PC by record type, please refer to the following article:
Authentication Technologies Matrix
- Go to Scans > Authentication.
- Check that you have a Unix record already defined for the host running the database.
- Create a Pivotal Greenplum record for the same host. Go to New > Databases > Pivotal Greenplum.
Tell me about user permissionsTell me about user permissions
Managers can add authentication records.
Unit Managers must be granted these permissions:
- Manage PC module / Manage SCA module
- Create/edit authentication records/vaults
You’ll need to tell us the user account to be used for authentication, the database instance to authenticate to, and the port where the database is installed.
The type of authentication method you use depends on your server settings and how you've configured client authentication.
You can use:
- a password (enter it on the Login Credentials tab or get it from a password vault),
- a client certificate (enter it on the Private Key / Certificate tab),
- a password AND client certificate (enter values on both tabs).
On the Unix tab, tell us the full path to the configuration file (postgresql.conf) on your Unix hosts. The file must be in the same location on all IPs listed in the record. If the file is in a different location for some hosts you must create additional records for those hosts. Unix authentication is also required.