-
Notifications
You must be signed in to change notification settings - Fork 167
Peer authentication for local connections #1185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
What errors are you seeing? AFAIK peer authentication should work fine. |
It may be that I don't understand how to use it? However, I'll mention that the docs say "Skunk currently supports the trust (no password necessary), password, md5 and scram-sha-256 authentication methods." (https://typelevel.org/skunk/reference/Sessions.html), so if peer authentication is supported, the docs are out of date. If it does work, I would expect it to work by calling, for instance, When I try with
This is not surprising, since When I try with
This is not surprising, either, as the empty string certainly isn't a valid host. Am I missing something? |
Oh sorry, I was incorrect. Folks have manually added in support in the past -- e.g. #928 -- but there's no current built-in support for connecting via unix domain sockets. I'd like to add it before shipping 1.0 though. |
Support added in #1192 |
I can't seem to find any way to make Skunk connect to a local Postgres with "peer" authentication (https://www.postgresql.org/docs/current/auth-peer.html). This authentication type is the default out-of-the-box for local Postgres connections, on Linux, and I believe MacOS. It is convenient, and secure, for local development. It would most typically be selected by leaving out the host, username, and password, and lets the local operating system authenticate the user as the user running the connecting process. I can live without it, but was surprised to see it seems to be missing.
The text was updated successfully, but these errors were encountered: