-
-
Notifications
You must be signed in to change notification settings - Fork 67
Auth0 FDW API Key #459
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
I've tested on my account and it works fine. Can you confirm used correct create server auth0_server
foreign data wrapper auth0_wrapper
options (
url 'https://dev-xxx.au.auth0.com/api/v2/users',
api_key_id '<secret id in Vault>'
); |
Configuring it using SQL instead of the GUI indeed made it work! thanks! |
Currently there is no automatic way to handle token expiration, so we have to replace it every month. We will do some evaluation and research to see if possible to add OAuth support in Wrappers, hopefully in the next several months. |
Ok, thank you very much for your responses |
Hi
I’m trying to configure Supabase’s Auth0 FDW as outlined in the documentation.
According to the guide, the extension requires an “Auth0 API Key or PAT”. However, Auth0 doesn't supports creating Personal Access Tokens (PATs), and to interact with the Management API, a valid access token must be obtained through a client credentials flow — meaning the wrapper itself needs to request the token using the appropriate client ID, secret, and audience.
Has anyone successfully configured this FDW under these constraints?
If the wrapper currently lacks support for programmatic token retrieval, are there any recommended workarounds?
Thanks!
The text was updated successfully, but these errors were encountered: