ไม่สามารถเล่นวิดีโอนี้
ขออภัยในความไม่สะดวก
OAuth 2.0 Explained | Bubble.io API Tutorial Part 06
ฝัง
- เผยแพร่เมื่อ 6 ส.ค. 2024
- This is part 6 of my series on APIs. In this video we connect to Spotify's API in order to access a user's list of followed artists. In the process, we'll learn all about OAUTH 2.0 authorization -- which, as far as I'm concerned, is one of the trickiest forms of authentication / authorization you'll run into when dealing with APIs in Bubble.io.
If you missed the earlier videos in this series, the links are below:
Part 1: • What is an API? | Bubb...
Part 2: • Using the API Connecto...
Part 3: • Making Dynamic Calls |...
Part 4: • Dealing with Authentic...
Part 5: • GPT-3 and the OPEN AI ...
The only regret that I have is that I didn't watch this sooner. Thanks so much for this series
Thanks for watching! :)
Incredibly helpful in understanding how everything works. AMAZING tutorial. Thank you!
Such a good series enabled me to integrate a payments module for my new app idea, cheers!
This series was so useful. Very specific and detailed. Other videos on TH-cam used Postman or Xano, and I don't want to download a friking coding platform to simply connect an API to bubble.
Massively helpful video. I used these steps to help me through the Reddit connection. For anyone else dealing with Reddit, the "Code" that comes back has an extra "#_" that you have to remove with find and replace action.
Great video! I will have to watch it again, slowly, but it's very clear. Thanks a lot. Greatings from Argentina!
Thank You SOO MUCH FOR THIS VIDEO.
From Brazil.
👏👋👍
Would just like to thank you for this series. Very grateful for your thoughtful style of teaching. Greetings from London
Thanks for the kind words J! Glad you're finding it helpful.
The video really helped me understand Oauth 2.0 on bubble.
Thank you so much.
Is it possible for you to make a video about Instagram basic API too?
That would really really save me.
Using this for podcasts. Such a game changer.
One of my favorite tutorial on api. Thanks man
Glad it helped! Thanks for watching :)
Thanks for the video.
It will be fine if you could explain how to handle with access token and refresh token.
A video please 🙏
Thanks! I'll keep that in mind for a future vid.
Thanks Bro for such easy explanation. Very useful
Ur the man for making this video! I would be interested to see you set up the OAuth2 User-Agent Flow using Bubble's out of the box API connector like u talk about at the end of the video.
Very well explained! Thank you!
Glad you found it helpful!
Thank you! This was very helpful and learned a lot
Happy to hear!
Thanks for the video. Your explanation was very helpful. I have one question though. In the video, you mentioned that if we don't use Bubble's API connector authentication integration, we would need to worry about things like where to store the access and refresh token. Can you explain how you handled the storage of the access and refresh tokens when you set everything up manually, which was effectively what you did for this video. I am not quite sure where that happened. Thanks!!
Awesome!
Great Tutorials. Thanks!
Glad you like them!
This is a really great video. Demystifies Oauth for me. thank you.
Glad it was helpful!
Great video, thank you.
Thank you!
Love the explanation. Thank youh
Thanks!
Minute 28:57 - is there a way to make the parameters dynamic on bubble or do you have to use the Body field?
P.S. this whole series is AMAZING!! Thank you for making it!
Question: how do you use refresh tokens? I understand that after one hour, the access token becomes invalid; but then what call do you make to get a new access token?
Thank you for a helpful video!
Can I use the OAuth2 User-Agent Flow method for multiple app users, who each need to authorise access to THEIR Google Calendar? Is Bubble capable of managing (storing and refreshing) the tokens for multiple users OR the only option is to store all the tokens in the database and manage them manually?
Hello Jacob. I configured the API with the OAuth User-Agent Flow authentication mode that comes native to Bubble. In theory, I understand that once configured, it is not necessary to put the Authorization header in each call, but even so, I still get the error message "undefined error: this header name is not correct undefined". It would be nice if you make a tutorial about using this configuration for the APIs. Also, I have another question. You put the access token in the Authorization header to configure the call, but that doesn't vary depending on who logs in and when? Thanks for everything!
Hi Jacob, thanks so much for this video! Can I ask you a question？ Is there a way we can hide the authorization code on the user's end? In your experience, if not hiding it, will that cause any concern?
Thank you so much, Great tutorials, it will be great idea if you make more tutorials about API ( Course ) includes some topics like connecting bubble with Xano for scalable Apps , Maybe more API services from "Rapid API, PayPal API, Pinterest and more ....I would buy this course. Thanks A lot
Thanks for the suggestion! Thinking of bringing some tutorial style vids back in the new year.
Hey Jacob - At 35:11 you mention that signup/login with social network, behind the scenes, bubble is creating a username/password using the unique token, and allowing users to login with that. How would you do this manually? I have to reverse engineer this for shopify auth
TURBO-useful!
Happy to hear that!
Hi Jacob! Your video tutorials are super! With this tutorial I managed to authorize an API using oAuth2 and cryptographic tokens via Bubble's OAuth2 User Agent Flow method.
Next steps I'm taking and some possible tutorial content ideas lol:
I'm trying to add multiple API endpoints, while having to refresh the auth token each time, since my token expires every 60 minutes! I keep refreshing the token manually, pretty sure it's not supposed to be like that haha it's too much work! I want the token to AT LEAST be in a shared header when re-initializing all the APIs, however when the authorization Bearer Token is in a shared header, I then lose the ability to check/uncheck "private"? Hmmm makes me think my user agent flow is working, but not setup in an optimized way.
I'm also curious how to manage API call requests on the user interface side, like is bulk-data-save best practice, then refresh the API sometime...later...in some way? (I'm managing sales/transaction data using Etsy's brand new API)
Thanks for sharing your knowledge!!
Thanks for the kind words! Glad you found this helpful. Could you set up some sort of check to see if the token is expired (if yes, get the refresh token?). Not sure how you've set things up or if that's what you're getting at with the manual refresh. And yeah, the shared header thing not being dynamic is a bummer. Last question depends really on what you're trying to do I think! I'd recommend posting about this in the Bubble forum!
@@jacobgershkovich I'll try a token expiration "check", great idea! I'm still wrapping my head around token expiration and when/how to refresh live data. Thank you for your response, I really appreciate it! I'm going to spend the weekend on Bubble forums lol~!
Hi Jacob, I'm trying to follow your procedure to show the data of a call that brings the list of Google Ads accounts at the front-end level, but I can't show it because when the call starts it doesn't show the object with the results property and so your way of doing it doesn't work for me. Could you tell me what I should do in this case?
I wanted to share a picture of my call with you so you understand, but TH-cam doesn't allow it. Do you have any contact to share the image with you?
I'm stuck at 26:39. Keep getting error code 401 "invalid access token."
Is it secure to save the access token on the User? This should be no problem, if the privacy settings have been done correctly, right?
If you’ve set up privacy rules yeah.
Can you do a video on the 0auth2 user agent flow?
If I start doing tutorials again I'll keep that one in mind!
@@jacobgershkovich I hope you do you are an great teacher. If you do a udemy course I would definitely buy one