Just tried it now, but the original plugin no longer seems to work. They have added a new "LinkedIn using OpenID Connect" plugin, which is the working one. Not sure why they still keep the obsolete one around...
Oh my... I spent 2 hours to figure out why it is not working till find this comment. Thank you so much! Bubble should remove the old version of Plug in....
hi hope you are well , can you plz make a video or guide me on advance filters ( 5 to 6 intersecting filters ) i created them but i am not satisfied that they are set in optimized way
VERY BIG PROBLEM, I implemented this exact thing a couple weeks ago and now my user's cannot log in when they click login it said: "user's email had already been used"
That does sound strange. When using the Oauth provider workflow step, Bubble should automatically determine if it needs to create a new account for someone, or log in an existing user. Have you added any additional workflow steps of your own after the Oauth step?
Thanks! If you'd like to collect more data, I'm under the impression that you'll need to request a higher level of permission through your LinkedIn developer portal. Hope this helps!
@@BuildingWithBubble Thanks man - you're right. Had to set up the API call myself using bubble connector, as the plugin only allows for lite profile scope
It seems like users end up outside of the usual 'rules' for Bubble, which always associate them with a unique email and a password. What does it look like in the database when we're looking at these users? Does this have any functional impacts for us as developers? As always, these videos are incredibly useful - thanks!
Great question! You're right, if someone registers an account through LinkedIn, their email and password won't actually be stored within your database. I'm under the impression that in the backend, Bubble would link the users LinkedIn account ID to their user ID in Bubble, but this isn't something you'll see as a developer.
Just tried it now, but the original plugin no longer seems to work. They have added a new "LinkedIn using OpenID Connect" plugin, which is the working one. Not sure why they still keep the obsolete one around...
Oh my... I spent 2 hours to figure out why it is not working till find this comment. Thank you so much! Bubble should remove the old version of Plug in....
@@rreport Well, I only wasted about 20 minutes. Don't have patience for that BS. :D
Très bonne vidéo. Thanks from France
My pleasure 😎
Awesome!!! Thank you for the good tips on bubbles :)
Glad it could help 🙌
Would greatly appreciate a video on how to post an image to LinkedIn via api connector. The existing videos seem outdated. Thanks for your videos!
Happy to add this one to my list 👍
@@BuildingWithBubble Thanks! It would be awesome to see it as an api connector but I don't mind any workarounds. Thanks again for the videos.
hi hope you are well , can you plz make a video or guide me on advance filters ( 5 to 6 intersecting filters ) i created them but i am not satisfied that they are set in optimized way
Happy to add this to my list ✌
Where to buy the full course
Hey, this is the full, free tutorial on RUclips. There's no need to pay for additional content for this video.
VERY BIG PROBLEM,
I implemented this exact thing a couple weeks ago and now my user's cannot log in
when they click login it said: "user's email had already been used"
That does sound strange. When using the Oauth provider workflow step, Bubble should automatically determine if it needs to create a new account for someone, or log in an existing user.
Have you added any additional workflow steps of your own after the Oauth step?
Hi there -
Awesome video, as always, but what if I want to collect the email addresses as well?
Thanks! If you'd like to collect more data, I'm under the impression that you'll need to request a higher level of permission through your LinkedIn developer portal.
Hope this helps!
@@BuildingWithBubble
Thanks man - you're right.
Had to set up the API call myself using bubble connector, as the plugin only allows for lite profile scope
@@AliAdel-dt3od Glad you got there in the end 🙌
It seems like users end up outside of the usual 'rules' for Bubble, which always associate them with a unique email and a password. What does it look like in the database when we're looking at these users? Does this have any functional impacts for us as developers?
As always, these videos are incredibly useful - thanks!
Great question! You're right, if someone registers an account through LinkedIn, their email and password won't actually be stored within your database.
I'm under the impression that in the backend, Bubble would link the users LinkedIn account ID to their user ID in Bubble, but this isn't something you'll see as a developer.