Open pmagnuson opened 4 years ago
@pmagnuson: psql
may connect through Unix socket too, please double check with another tool. It is likely that either the password auth is disabled, or the source IP is not enabled (is there any networking involved?)...
@isoos: I appreciate you looking into this issue.
I have double checked the connectivity using a python program and psycopg2
. It works correctly and returns results.
From this I believe I have the correct connection information and user/password.
Not sure where to go from here.
This library does not implement the cleartext password authentication method in the frontend/backend protocol; it only implements the md5 password method. If you wanted to implement this method, check out the docs for the authentication messages the client/server send here.
You might need new state types (like the class that method belongs to) to handle the different states the connection will be in for the differing authentication methods. I believe the clear text method you want to use requires an authentication challenge and would require a state to respond to this challenge. You'll also note the error message you are seeing in your issue is located in this method.
edit: Or optionally allow md5 authentication type in your postgres config, if possible.
I am running into the same exact issue with cockroachdb - which is a blocker.
being able to connect via a secure connection is a must have ... are there any plans to address this?
fwiw, I'm using cockroachdb with insecure setup + wireguard to connect the nodes and the clients.
Following the example code of
produces the error
PostgreSQLSeverity.error : Unsupported authentication type 3, closing connection.
I verified that the connection parameters work by using the same with
psql
on this database.The full stack trace is