Oauth 2.0 user agent - working in Postman, not in API Connector

Hi everyone,
Qq around topic above.
I’m trying to connect to an API that works fine with Postman but not with the API Connector. I think there is just some minor configuration that I’m missing or a workflow step to get the token perhaps that I haven’t done.
If anyone has any tips to get this over the line so I can initialise that would be very helpful (secret shown in images has been changed).



Cheers
Steve

Where does it fail when you try to login? Do you go to the authorization page? (login)? Does it fail after the redirect? Do you get error from this API or from Bubble when you are back to Bubble?

which scopes do you have?
Also, I’m sure you need to delete the shared headers for all call “x-api-key”.

Do you have a link to the user profile endpoint? I didn’t found it…
Also, is your goal is to connect your user Intelliflo account or your own account?

Hi Jici,
Thank you for the response.
Where I’m struggling is the concept of getting to the authorisation page to get the token in the first place.
I understand that I’m trying to use the Sign Up/Login with Social Network workflow action (which opens a new page, and I’m getting a http 500 error).
Is the handling of the token response simply handled by Bubble and then I can start to play around with the APIs.
In Postman screen shot just above, I’m asked to Get New Token (which works fine and I enter my UN/PW details) and then I’m redirected back to Postman and can then send requests to the Intelliflo API.
To answer your questions.
Noted about the x-api-key.
I don’t think their api has a publicised User Profile Endpoint so I just guessed as to what it could be.
The scopes are as follows and these marry up to the scopes on their end
client_data client_financial_data firm_data fund_data openid myprofile
Cheers

below is console from Postman showing a successful token request

Can you record a screencast when you try to login using social network?

Hi Jici,
FYI I was able to get it working with a lot of trial and error. Here is what I did.
The API Connector had most of the details I required although during the copy & paste, a space had appeared in the Client ID so that was one (rookie) mistake I made.
Secondly, the User Profile Endpoint isn’t documented on the API docs so I ended up stumbling on this GET request from Claude, which gave me additional unpublished information about the end point.
https://identity.au.intelliflo.net/.well-known/openid-configuration
The end portion of text being the important part.
When I requested this I saw the URL for the User Info, which I queried and the details I needed were presented.
https://identity.au.intelliflo.net/connect/userinfo
Most importantly the User ID key path was incorrect so I changed it to the right value.



I ran my workflow and was finally presented with the success dialog!
Thanks for looking at this post and hopefully my struggles could benefit someone else who is running into the same problems.
Cheers,
Steve

1 Like