before sending it to Greenplum Database, once on the password and role name and then again with a salt value shared between the client and server, so the clear text password is never sent on the network encrypted with SCRAM-SHA-256, it has the format: SCRAM-SHA-256$:<salt>$: where <salt>, , and are in base64-encoded format. This format is the "username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two

before sending it to Greenplum Database, once on the password and role name and then again with a salt value shared between the client and server, so the clear text password is never sent on the network encrypted with SCRAM-SHA-256, it has the format: SCRAM-SHA-256$:<salt>$: where <salt>, , and are in base64-encoded format. This format is the "username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two

before sending it to Greenplum Database, once on the password and role name and then again with a salt value shared between the client and server, so the clear text password is never sent on the network encrypted with SCRAM-SHA-256, it has the format: SCRAM-SHA-256$:<salt>$: where <salt>, , and are in base64-encoded format. This format is the "username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" VMware Tanzu Greenplum 6 Documentation VMware, Inc 1034 auth_file contains

before sending it to Greenplum Database, once on the password and role name and then again with a salt value shared between the client and server, so the clear text password is never sent on the network encrypted with SCRAM-SHA-256, it has the format: SCRAM-SHA-256$:<salt>$: where <salt>, , and are in base64-encoded format. This format is the "username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two

before sending it to Greenplum Database, once on the password and role name and then again with a salt value shared between the client and server, so the clear text password is never sent on the network encrypted with SCRAM-SHA-256, it has the format: SCRAM-SHA-256$:<salt>$: where <salt>, , and are in base64-encoded format. This format is the "username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two

before sending it to Greenplum Database, once on the password and role name and then again with a salt value shared between the client and server, so the clear text password is never sent on the network encrypted with SCRAM-SHA-256, it has the format: SCRAM-SHA-256$:<salt>$: where <salt>, , and are in base64-encoded format. This format is the "username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two

"username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two Database users from the pg_shadow view. PostgreSQL SCRAM secret format: SCRAM-SHA-256$:<salt>$: See the PostgreSQL documentation and RFC 5803 for details on this. VMware specify a user name, and the SCRAM secrets are identical in PgBouncer and the PostgreSQL server (same salt and iterations, not merely the same password). This is due to an inherent security property of SCRAM:

"username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two Database users from the pg_shadow view. PostgreSQL SCRAM secret format: SCRAM-SHA-256$:<salt>$: See the PostgreSQL documentation and RFC 5803 for details on this. VMware specify a user name, and the SCRAM secrets are identical in PgBouncer and the PostgreSQL server (same salt and iterations, not merely the same password). This is due to an inherent security property of SCRAM:

"username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two Database users from the pg_shadow view. PostgreSQL SCRAM secret format: SCRAM-SHA-256$:<salt>$: See the PostgreSQL documentation and RFC 5803 for details on this. VMware specify a user name, and the SCRAM secrets are identical in PgBouncer and the PostgreSQL server (same salt and iterations, not merely the same password). This is due to an inherent security property of SCRAM:

"username1" "password" ... "username2" "md5abcdef012342345" ... "username2" "SCRAM-SHA-256$:<salt>$:" auth_file contains one line per user. Each line must have at least two Database users from the pg_shadow view. PostgreSQL SCRAM secret format: SCRAM-SHA-256$:<salt>$: See the PostgreSQL documentation and RFC 5803 for details on this. The specify a user name, and the SCRAM secrets are identical in PgBouncer and the PostgreSQL server (same salt and iterations, not merely the same password). This is due to an inherent security property of SCRAM: