No SSL settings or pool configuration - the connection string is not enough

[z4nr34l]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

There is no possibility to connect to DB using SSL connection (Providers like Vercel are not allowing to install custom CA certs in envs) with self-signed cert but lib only accepts connection string.

Error processing Stripe webhook: Error: self-signed certificate in certificate chain
    at async i.upsertManyWithTimestampProtection (.next/server/app/api/webhook/stripe/route.js:20:875)
    at async D.processEvent (.next/server/app/api/webhook/stripe/route.js:46:8459)
    at async j (.next/server/app/api/webhook/stripe/route.js:15:1682)
    at async (.next/server/chunks/7688.js:7:35620)
    at async k (.next/server/app/api/webhook/stripe/route.js:16:7086) {
  code: 'SELF_SIGNED_CERT_IN_CHAIN'
}

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to Supabase Dashboard
2. Enable forced SSL connection
3. Try to connect from stripe-sync-engine
4. See error in logs when webhook is called by stripe

Expected behavior

Possibility to pass CA cert or if possible even using existing pg pool client from code.

Screenshots

System information

• OS: [e.g. macOS, Windows] N/A
• Browser (if applies) [e.g. chrome, safari] N/A
• Version of supabase-js: [e.g. 6.0.2] N/A
• Version of Node.js: [e.g. 10.10.0] 22

Additional context

N/A

[kevcodez]

Can you post your code to connect to the database? Sync-Engine supports passing in a poolConfig including SSL configuration

Did you download your database SSL certificate and pass it into your SSL configuration as cert?

[z4nr34l]

Gimmie sec, I was on 0.41.1 - probably this was solved in newer versions

[z4nr34l]

Yeah, with newer version I managed to connect with SSL, but the docs and readme are outdated in that matter.

I dug through the package code to verify the actual config state and solved that on my end.

I'll make an PR with readme & docs update for SSL and pool configuration including a workaround for passing the SSL cert in base64 for Vercel/Netlify like providers.

[github-actions]

🎉 This issue has been resolved in version 0.45.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀