rust/neon

mirror of https://github.com/neondatabase/neon.git synced 2026-01-10 06:52:55 +00:00

Files

Dmitry Ivanov 1d9d7c02db [proxy] Don't forward empty options to compute nodes

Clients may specify endpoint/project name via `options=project=...`,
so we should not only remove `project=` from `options` but also
drop `options` entirely, because connection pools don't support it.

Discussion: https://neondb.slack.com/archives/C033A2WE6BZ/p1676464382670119

2023-02-15 22:05:03 +03:00

src

[proxy] Don't forward empty options to compute nodes

2023-02-15 22:05:03 +03:00

Cargo.toml

[proxy] Fix possible unsoundness in the websocket machinery (#3569 )

2023-02-10 12:45:38 +03:00

README.md

Follow-up for neondatabase/neon#2448 (#2452 )

2022-09-15 15:21:22 +03:00

README.md

Proxy

Proxy binary accepts --auth-backend CLI option, which determines auth scheme and cluster routing method. Following backends are currently implemented:

console new SCRAM-based console API; uses SNI info to select the destination project (endpoint soon)
postgres uses postgres to select auth secrets of existing roles. Useful for local testing
link sends login link for all usernames

Using SNI-based routing on localhost

Now proxy determines project name from the subdomain, request to the round-rice-566201.somedomain.tld will be routed to the project named round-rice-566201. Unfortunately, /etc/hosts does not support domain wildcards, so I usually use *.localtest.me which resolves to 127.0.0.1. Now we can create self-signed certificate and play with proxy:

openssl req -new -x509 -days 365 -nodes -text -out server.crt -keyout server.key -subj "/CN=*.localtest.me"

start proxy

./target/debug/proxy -c server.crt -k server.key

and connect to it

PGSSLROOTCERT=./server.crt psql 'postgres://my-cluster-42.localtest.me:1234?sslmode=verify-full'