Skip to content

Conversation

@ikalnytskyi
Copy link
Owner

When trust authentication [1] is specified, PostgreSQL assumes that anyone who can connect to the server is authorized to access the database with whatever database user name they specify (even superuser).

Since this action is intended to be used on CI, this is unlikely a desired behaviour. First, all credentials are known and must be specified in order to avoid flakes. Second, most commonly folks around there want to test that secrets are gathered and passed down to the database server correctly.

This patch turns off 'trust' authentication for the PostgreSQL server.

[1] https://www.postgresql.org/docs/15/auth-trust.html

Resolves #5

@ikalnytskyi ikalnytskyi force-pushed the turn-off-trust-auth branch 5 times, most recently from 6eeaa6d to 8051eba Compare January 2, 2023 19:16
When trust authentication [1] is specified, PostgreSQL assumes that
anyone who can connect to the server is authorized to access the
database with whatever database user name they specify (even superuser).

Since this action is intended to be used on CI, this is unlikely a
desired behaviour. First, all credentials are known and must be
specified in order to avoid flakes. Second, most commonly folks around
there want to test that secrets are gathered and passed down to the
database server correctly.

This patch turns off 'trust' authentication for the PostgreSQL server.

[1] https://www.postgresql.org/docs/15/auth-trust.html

Resolves #5
@ikalnytskyi
Copy link
Owner Author

Closed in favor of #12

@ikalnytskyi ikalnytskyi closed this Jan 3, 2023
@ikalnytskyi ikalnytskyi deleted the turn-off-trust-auth branch January 3, 2023 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wrong credentials are not rejected

2 participants