We use cloud-hosted Retool Database and are preparing a restricted connection for a replacement sync in staging. An existing administrator connection works with TLS certificate and hostname verification.
We created a custom runtime role and a separate owner role. Both remain NOLOGIN. We want to initialize the runtime role's password while preserving its grants and ownership relationships, then enable LOGIN only after a separate approved validation step. The application should use a dedicated restricted connection rather than the administrator connection.
Using PostgreSQL 18.6 psql, the following command fails (role name below is illustrative):
\password example_sync_runtime
The control plane returns HTTP 400:
Neon only supports being given plaintext passwords
We have not placed a real password in saved Retool SQL or enabled the role's LOGIN attribute. We do not have established access to the underlying Neon management account.
What is the supported credential-initialization route for an existing custom SQL-created role in managed Retool Database?
Is there a Retool credential UI or managed control-plane operation that can set this role's password while leaving it NOLOGIN and preserving its existing privileges?
If plaintext password submission through SQL is required, what supported approach keeps it out of saved query text/history? What protection or redaction applies to Retool query, audit and error logs, and to underlying database/control-plane/proxy logs?
Can an encrypted Retool secret configuration variable be used for this specific role-password operation without exposing its value in those logs? If so, what documented execution method is supported?
If custom login-role provisioning is unsupported, what supported alternative provides a dedicated least-privilege database identity for a Retool workflow?
We have already reviewed the documentation on external database access and forum posts about copying masked connection strings, missing Connection tabs, and saving a resource before testing a connection. Those concern accessing existing credentials or connection configuration. Our question is specifically about initializing a custom role's credential securely.
We are looking for a supported provisioning method and its logging behavior, rather than a workaround that stores a plaintext password in saved SQL.
On a cloud-hosted managed Retool Database (Neon-backed), a custom NOLOGIN PostgreSQL runtime role was created for a least-privilege external connection, but initializing its password with psql's \password fails with Neon HTTP 400 "Neon only supports being given plaintext passwords." The request is for the supported way to set the role's credential securely while preserving its grants and NOLOGIN state.
AI Response
This error occurs because psql's \password performs client-side SCRAM hashing and submits a pre-hashed verifier, which the managed Neon control plane rejects — it only accepts a plaintext password literal in the SQL statement itself. The supported route is to set the credential via a plaintext-literal DDL statement run from an external client/psql session (e.g., ALTER ROLE <role> WITH PASSWORD '...';), which does not alter the role's existing grants, ownership, or its NOLOGIN attribute — you can enable LOGIN separately later after your validation step. Creating and scoping a dedicated least-privilege role with GRANT/REVOKE over the admin connection string is a supported pattern for cloud orgs. To keep the secret out of saved Retool SQL and its history, run the password statement interactively in an external PostgreSQL client (psql/pgAdmin) rather than saving it as a Retool query.
Sources
Can I restrict retool database external connection permissions
Solved thread showing how to connect to managed Retool Database via psql/pgAdmin and create a dedicated restricted login role scoped with GRANT/REVOKE for least-privilege external access. Access Retool Database tables externally | Retool Docs
Official docs confirming cloud-hosted orgs can access Retool Database externally via the admin PSQL command or PostgreSQL connection URL, including supplying role names and passwords in external clients/ORMs.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a , , or . Or by marking this post as the "Solution"! Let us know if you have any feedback here.
Thanks. Using an external PostgreSQL client would keep the statement out of saved Retool queries. Could a Retool engineer confirm the remaining details?
When submitting ALTER ROLE ... PASSWORD, is the password redacted from managed database, Neon control-plane/proxy, and statement/error logs—including failed requests?
Is there a Retool-managed credential flow for initializing an existing custom role’s password while keeping it NOLOGIN?
If external-client SQL is the only supported route, what procedure prevents the password from remaining in both local client history and managed logs?
We have not run the password-changing statement and would like to confirm the supported handling first.
Following up on the engineering questions above. Our staging resource still uses the administrator identity, and the restricted runtime role remains NOLOGIN while we confirm the supported credential setup. Local tests of the restricted permission design are passing, but they do not resolve managed credential initialization.
Could a Retool engineer confirm the supported way to initialize an existing custom role's password, and whether secret values are redacted from managed database, Neon control-plane/proxy, statement and error logs? If a Retool-managed credential flow or another supported least-privilege workflow connection is available, please point us to it. We have not submitted a plaintext password-changing statement or enabled the role's LOGIN attribute.