Instagram is not yet covered but we could definitely add support for it (it shouldnt take us too long to add this).
If I understand the profile picture question correctly, once the user logs in, you will have access to the profile picture for use in your app.
It however, makes sense for you to retrieve the information and store it against the users database in your Bubble app. That way, you wouldnt have to work with the SSOProfile as your login workflow should align with the current user and then the rest of your app should only interact with the currently user.
Iām looking to offer a dual login method for existing users. The issue is that if my existing users see āSign In With Googleā on the login page they will naturally click that first if they have a gmail account. I wanted to know if pathfix has a solution to handle the use case for a non-SSO existing user clicking on the SSO sign in? (i.e. associating SSO to an existing Bubble account on login)
Hey @messly the only way a user can sign in is using the āCurrent userā in Bubble. If the user has already been created, then creating a secondary user with the ID instead of the email might do it for you but all of the other mappings would be a bit of a nightmare.
However, you could add a column to check whether the user has previously logged in using SSO or id/pw and show the user a message accordingly.
Ok I see. So would it be possible to create a conditional logic where if a user who hasnāt previously created their account with SSO tries to login with SSO, I can prompt them to login normally without creating them a new account?
Hi @Pathfix, Im new to the world of OAuth. I remember manually managing social logins on bubble 2 years ago and it took me a few days to get it working, so the work you are doing is amazing.
Can you share, what your difference is with something like Auth0 SSO?
Pathfix focuses on more than just Identity. We are an integration platform that simplifies all aspects of integration - Authentication, Authorization, APIs and pretty soon, Automations (the 4 Aās of Integration).
More importantly, we donāt store ANY data (user or any other). We fetch the data and send it directly to your database. We believe its a more secure way and users never have to worry about their data sitting somewhere else.
I see, that make sense now looking at your app. Thanks for clarifying.
I really want to go ahead with this, Iāve even subscribed already. However, I canāt find a way to manage dual logins, ie, letting exisiting non OAuth users add additional external OAuth providers.
Hey @gavin1 it looks like a configuration error. Could you log in to your Pathfix account and reach out via live chat? We can go through the configuration together
Looks great and works well (except when pathfix is down) - I am a bit concerned about hard coding the same bubble password for all users in the system - is that a potential back door to every account if it gets found?
The password works in combination with the oauth process. Only on successful oauth verification will the password be called and the user will be logged in.
One wonāt work without the other
Additionally, you can add a custom field with the provider name and run a check to make sure the provider name matches before logging the user in.
Okay I had this all working then everything started to go wonky on me. Now when I try to log in the SSOUI screen is blank - sometimes (rarely) it works again. Now this started happening before I moved over to my own domain name so it isnāt entirely that but perhaps that is not helping.
I have not yet done anything on pathfix itself but the guides say I need to register on each SSO provider and redirect back to pathfix ā¦ with a pathfix account (okay but want this to work).
Looking at the page that entire div is empty - nothing is being returned.
Have seen similar behaviour on pathfix site itself over past week or so. Classic is it me or is it you or is it us?