@Darin_Patterson I have a scenario in make. I want to duplicate it for my clients with their unique connections. Make is going to serve as a backend sort of… for an app my clients interact with. I saw your post on some tips for creating oauth connections here.
I followed the steps you listed, but when I try to get the redirect url with the endpoint: GET /v2/oauth/auth/{connectionID}, it returns an html string instead. What could be the issue?
Hi Ayo, welcome to the Make Community. There are 2 answers to your question (the direct one and the long one).
- Based upon what you’ve described, I suspect this is either an authentication issue or a redirect issue.
- I suspect you are using an HTTP app to do this inside of Make (it’s not the normal Make app because you don’t want to actual go to the redirect…you just want the re-direct value).
- In that HTTP app, you’d need to use an authorization key in the header – as described here.
- If that is all correct, then it could also be the case that is is following the redirect. In the HTTP module, make sure the setting for “Follow redirect” is “no”. See screenshot.
- (the much longer reply) – It’s recently come to my attention that everything I posted in this thread is dependent on the user (who is establishing the connection) to be authenticated to Make (in the same browser session) for any of this to work. (I should post an update to that original message). That probably won’t meet the needs of what most people are trying to do with this setup. (but it depends on your overarching goal).
- This is unfortunate, but it kinda makes sense (in that they are creating a connection in Make and doing it through a front-end authorization method.
- Make is actually now working on a new product offering that does essentially what you describe in a much easier way. It’s currently in “early access” and you can see more about it here.
Send me a DM if you are interested in learning more about that solution.
Hope that helps.
5 Likes
