Your snaps are helping me a lot. As I am trying to let 3rd parties to interact with my bubbles app user and get their info as response via Oauth 2.0 agent flow.
Hi Sam, glad they were helpful. I don’t have much experience with Oauth 2 coming into a bubble app (and actually don’t know if you could do this right now since exposing Oauth2 is on the bubble roadmap page (bubble.is/roadmap), however I think in general the API connector is for when you want to access external services FROM your bubble app, whereas if you want an external service to access your application, what you need to do is go to the API workflows section which is found at the bottom of the menu at the top left that lists all of your pages. From there you would create the endpoint that you just listed above so that an external service to access your bubble app. I do this already for email parsing, so an external email parser would create an inbound call to an API workflow that i define in that menu.
Again, have no experience whatsoever with exposing Oauth2 in an api workflow but going there should get you moving. Let me know if you have any other questions!
Creation of endpoints is fine for me but I am worried about security, I don’t want 3rd parties to fetch bubble app users passwords.
Any other authentication to suggest for a more secured API?
Example:
Bubble app is a wallet
3rd party is an ecommerce website
User wants to pay with his credit (bubble app)
=> I want to let 3rd party integrate bubble app as payment way which implies login first (go to url) in order to make sure only one user will be debited.
Gotcha. Don’t have much experience in this area sorry about that, but if I think of anything down the road or come up with something will let you know!
Is this logging in of the first oauth account, what would explain my issue posted here? What are people doing in order to use the API Connector for api calls, not social login?
