Skip to content
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

supabase-py self-hosted with self-signed certificate verify CLient Option not exposed #1086

Open
nibler-fox-kiki opened this issue Mar 26, 2025 · 1 comment · May be fixed by #1091
Open
Assignees
Labels
bug Something isn't working

Comments

@nibler-fox-kiki
Copy link

Bug report

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

Describe the bug

Unable to access httpx verify kwarg from the create_client options. The verify kwargs are clearly available in _sync/client.py and _async/client.py but does not seem to be exposed to the SyncClientOptions/AsyncClientOptions

To Reproduce

supabase: Client = create_client(settings.SUPABASE_URL, settings.SUPABASE_KEY, options=SyncClientOptions(verify=False))

>>> TypeError: SyncClientOptions.__init__() got an unexpected keyword argument 'verify'

Expected behavior

verify kwarg should be passed to the httpx client to allow working with self-signed certificate

@nibler-fox-kiki nibler-fox-kiki added the bug Something isn't working label Mar 26, 2025
@silentworks silentworks self-assigned this Mar 26, 2025
@silentworks silentworks linked a pull request Mar 31, 2025 that will close this issue
@grdsdev grdsdev linked a pull request Apr 1, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants