How to Configure Greenplum Password Policy

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a greenplum password policy by loading a server module and defining host rules. These rules check secret strength, set expiration dates, and use strong hashing on the master node. Most data teams start by creating shared roles for analysts and apps. They set one strong secret and share it across the whole team. When these roles have broad read and write grants, one leaked secret risks all your data. How a greenplum password policy works Greenplum builds on Postgres and uses a maste

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up a greenplum password policy by loading a server module and defining host rules. These rules check secret strength, set expiration dates, and use strong hashing on the master node. Most data teams start by creating shared roles for analysts and apps. They set one strong secret and share it across the whole team. When these roles have broad read and write grants, one leaked secret risks all your data.

How a greenplum password policy works

Greenplum builds on Postgres and uses a master node to manage every user login. All users and apps talk to the master host first. The master host checks the host file to see how each role must log in. You must pick a strong hashing method in this file instead of plain text. Modern hashing protects stored secrets even if someone reads the system catalog tables.

Base database roles only support simple expiration dates out of the box. You can set a date when a role secret stops working. To check character length or complexity, you must load an extra check module on the master node. This module runs every time a user creates or changes a secret. It rejects weak strings that do not meet your team rules for length or mixed characters. It can also block users from putting their own role name inside the secret.

Steps to set up role and secret rules

First, the database admin updates the host file on the master node. You map each network range and database role to a strong hash check. Next, you load the secret check module into the main server settings file. You set the minimum length and require numbers, letters, and symbols. You then reload the master node so the new rules take effect right away.

After the module is active, you update existing roles with expiration dates and login limits. You can cap how many open sessions a single role can hold at once. You should also create separate roles for humans and automated jobs. Human roles need regular secret rotation, while app roles need strict network source limits. Finally, test the setup by trying to set a weak secret on a test role.

Application-to-Application Password Management: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

What native password rules leave open

A strong greenplum password policy stops bad logins at the front door. It makes sure users pick hard secrets and change them on schedule. Still, native login rules only check who logs in at the start of a session. Once the master node accepts the secret, the database trusts that session completely.

Native secret rules cannot see or control what queries run inside an active session. If an analyst logs in with a valid secret, they can still run a bad drop table command. They can also query full tables and pull sensitive emails, phone numbers, or card numbers. Shared roles make this worse because the audit log only shows the role name, not the person. Static secrets also sit in local text files where scripts or malware can read them. To fix this, teams need controls that inspect live queries and rewrite sensitive fields in results.

Add runtime guardrails and masking beside your databases and APIs

Login rules, role grants, and CI checks govern who connects to your stack. Yet any allowed script, engineer, or AI agent still runs commands with the full scope of its role. For workloads on Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes, SSH, or internal HTTP services, hoop.dev sits inline in the protocol beside the service as an open-source proxy, a sidecar for your database or API. On every production query an agent or human runs, hoop.dev decides whether to pass, mask, block, or escalate it for review.

Before a query runs, hoop.dev guardrails check the statement against your rules, an AI Analyzer you configure can score intent or hold risky calls for human approval, and hoop.dev data masking rewrites sensitive fields in responses in memory. Explore the MIT-licensed project on GitHub.

Frequently asked questions

Where do I enforce secret rules in a Greenplum cluster?

You enforce all login and secret rules on the master node and standby master. Users do not log in to segment hosts directly, so master rules cover all user sessions.

Does changing the password rule affect active database sessions?

No, changing secret rules or role expiration dates only affects new login attempts. Active sessions keeps the session active until the user logs out or an admin stops the process.

How can we protect card numbers and emails after a user logs in?

Password rules cannot hide table data once a role has read permissions. You need a query control tool that rewrites emails, phone numbers, and card numbers in query results.

The query runs. The emails stay hidden.