Supavisor custom PostgreSQL role authentication failing — 28P01 #52595
Replies: 2 comments
🔗 Related PRs
📝 Issue Planner
🧪 Issue enrichment is currently in open beta.
💬 Have feedback or questions? Drop into our discord! |
|
Your configuration is right — the The direct answer to your implicit question: the Shared Supavisor pooler authenticates only the users its tenant carries — the managed roles. A custom # direct connection (no Supavisor in the path) - same role, same password
psql "postgresql://ripple_app@db.irbmsildasupximnsrlz.supabase.co:5432/postgres" # add the password prompt-side
# pooler, for contrast
psql "postgresql://ripple_app.irbmsildasupximnsrlz@aws-1-us-west-2.pooler.supabase.com:5432/postgres"Use The supported workaround that works today: connect as a managed role ( grant ripple_app to postgres; -- requires ADMIN OPTION on ripple_app, i.e. you created it
-- verify before relying on it:
select pg_has_role(current_user, 'ripple_app', 'USAGE') as can_set_role;The permanent fix, and the ticket text for it: support adds the role to the tenant's user set. With project ref Two things worth doing regardless, since they cost nothing and remove the next class of failure: keep |
Uh oh!
There was an error while loading. Please reload this page.
Hello Supabase Support,
We are preparing a production application using a restricted custom PostgreSQL role and are unable to authenticate that role through Supavisor.
Project: Our-Ripples-Production
Project reference: irbmsildasupximnsrlz
Database role: ripple_app
Connection configuration:
Shared Supavisor hostname: aws-1-us-west-2.pooler.supabase.com
Session-pooler port: 5432
Transaction-pooler port: 6543
Username: ripple_app.irbmsildasupximnsrlz
Database: postgres
Strict TLS certificate and hostname verification
Observed behavior:
We generated a new strong password and enabled LOGIN on the restricted role. Two controlled tests returned PostgreSQL authentication error 28P01, including one after waiting 90 seconds for credential propagation.
Strict TLS completed successfully, and the error occurred during Supavisor authentication.
The role is non-superuser, NOINHERIT, NOBYPASSRLS, and does not own application tables. We restored NOLOGIN and cleared the password after each failed test.
The direct database endpoint is IPv6-only, and our current Windows environment has no usable IPv6 connectivity, so we cannot independently verify the credentials against the direct endpoint.
Could you please:
Confirm whether custom PostgreSQL LOGIN roles are supported for this project's shared Supavisor pooler.
Confirm the correct endpoint and custom-role username format.
Investigate the 28P01 authentication failures using the project's pooler logs.
Advise whether additional pooler configuration or credential-cache propagation is required.
Recommend the safest supported method to verify restricted-role authentication from an IPv4-only network.
We can provide sanitized diagnostic timestamps and error logs. We will not share passwords or connection strings containing credentials.
Thank you.
All reactions