Additionally you can generate an access token by posting to the token endpoint and including grant_type=password, client_id, client_secret, username, and password in the body.
It looks like the retool OAuth 2.0 only supports server side and client credentials. So I'm guessing I'd need to use Custom Auth.
I'm a bit stuck here though. My first instinct was to use an API Request as my first Auth workflow step. When I add the POST request to the workflow I get an error "Action only supports GET".
Hi @henrymeiklejohn, Can you take a screenshot of the error you see on Retool? I wonder if that's an error returned by your server, not a Retool error. If you try to use "GET" method instead of "POST" method, does the error go away?
I think your requests succeeded and you would get the token in the http1 object in the response. You should expand it to see what it contains. For custom authentication flow, you have to manually extract the token out and set up the HTTP request to use it in its header. Please refer to the link here to see how to set up a custom authentication: Custom API authentication | Retool Docs
Hi @Harry_Doan. I just discovered that this API now supports Client Credentials. So looks like I can use actual OAuth2.0 setup rather than custom.
I'm still having a bit of trouble though. It looks like the token is probably being added to my requests because I see the Authorization header sanitized, but I'm getting "Authentication credentials were not provided" as a response. Could you help me troubleshoot this setup please?
