Question time! So, I have an API that I need to authorize on behalf of users. What I need to do is basically exactly what Bubble’s “User-Agent” flow (the login type flow we’re all pretty familiar with)… except that this particular API has no user profile endpoint.
So this API cannot be used to “log the user in”, BUT, I need to authorize, get access token and come back to my own app.
Basically, if there were a user profile endpoint, I’d be done. I’ve got everything working, but of course, if I do this thru “User-Agent” flow, I get at the very last step, this error – AS WE WOULD ANTICIPATE:
To which I say, “Well, DUH, Bubble. I don’t have one and so I’ve left this blank.” Of course, this isn’t helpful to me or to Bubble.
Anyway, the question is this: For situations like this – where we are simply asking the user’s permission to connect on their behalf via an Oauth flow…
What is the correct alternative Oauth authentication scheme to use??? Neither “Password Flow” nor “Custom Token” offer exactly analogous setups to the User-Agent scheme (which, for example, has built in fields for App ID and App Secret, the name of the token, etc.).
Does anyone have an example of how one does this properly then? I’m sure it’s not “impossible”, but I’m a bit lost in terms of how one goes about creating an alternative Oauth based authentication if the built-in User-Agent flow can’t be used.
Again, it seems to me that “User-Agent” flow cannot be used here because the API I’m attempting to auth to does not have a user profile endpoint. (And, yes, I’ve confirmed this with the provider. I’ve also suggested that they really really need that… because I really really need that. But at present, it’s not an option.)
Thanks for any tips/pointers, or just the actual solution. (I can’t imagine what I’m describing is particularly rare.)