Hi!
We use auth0 in our mobile application and are having issues with the LinkedIn social connection. Starting a few days ago, when a user choses “log in with Linkedin”, the user is sent in to the Linkedin mobile app (if they have it installed) and not back to our application. If the Linkedin mobile app is not installed on the device it works fine. Any ideas what could have happened?
This is super crucial for our product because our users cant login and also the candidates applying for jobs cant do that from the Linkedin option. Anyone else that has experience from this?
I understand that you are encountering issues with authentication using the LinkedIn Social Connection.
To help me understand the problem better, I have some clarifying questions.
First, could you please clarify if you have configured your callback URL properly? The callback URL redirects your users back to your application after being successfully authenticated.
The callback has worked for a long time and this issue only happens fore some, it still works for others – so that should not be the problem right?
We have a browser-based flow.
We have not done any changes in our product or our Auth0 settings recently (and the problem only and usually occurs when you have the Linkedin app installed on your phone), so we wonder if it has to do with an update of linkedins app.
When I dont have the Linkedin app installed on my phone, Im sent to Linkedins webb login. That works.
But when the LInkedin app is installed Im sent to some form of app-login instead, then it does not work. See pictures. Hope that helps.
Here comes the issue with more info and slightly re-frased (new things in the bottom):
We are having issues with the LinkedIn social connection. Probably starting with Linkedins update to the version 9.1.234. Still the same issue on version 9.1.235. When a user choses “log in with Linkedin”, the user is sent in to the Linkedin mobile app (if they have it installed) and not to LinkedIn’s login form. This problem started when Linkedin updated their app. If the Linkedin mobile app is not installed on the iOS device, it works fine.
This is super crucial for our product because our users cant login and also the candidates applying for jobs cant do that from the Linkedin option.
We have a browser-based flow and have not done any changes in our product or our autentification service (Auth0) recently (and the problem only occurs when you have the Linkedin app installed on your phone).
When I dont have the Linkedin app installed on my phone, Im sent to Linkedins webb login. That works. But when the LInkedin app is installed Im sent to some form of app-login instead, then it does not work.
To reproduce the issue, simple visit this link from an iOS device with the LinkedIn mobile app installed:
Since the oauth parameters are valid, this link redirects to a url similar to
It is this link that opens the installed app instead of just continuing in the web browser and then the oauth dance stops abruptly since the app cannot communicate any authentication code back to the browser.
After collaborating with our teams, we discovered that this is an issue with LinkedIn producing a Universal Link and opening the LinkedIn mobile app.
Unfortunately, there is nothing we can do on our end to fix this. We apologize for any convenience this may have caused you or your end-users. We are currently working to find a resolution on this issue as soon as we can.
Meanwhile, your end-users can continue authentication onto your Application with a workaround that does not involve uninstalling the LinkedIn mobile app:
Open Safari
Type “LinkedIn” in the Safari search bar to pull up the search result
Tap on the LinkedIn search result link
Select “cancel” when a dialogue opens asking if you want to open the LinkedIn app
Navigate back to the app and login successfully with LinkedIn without opening the LinkedIn app
I understand. Thanks for the workaround even if it will not delight our users
Lets hope LInkedin updates their app, and please let us know if you find any other solution from your side. Might be a good idea that you also contact Linkedin to make them aware that this issue should be highly prioritized?
Thank you for making these suggestions. We have escalated this to our Engineering teams to address the problem. They will be in contact with LinkedIn Support to work on a resolution.
As soon as there are any updates, I will be sure to relay that information to you.
Thanks Rueben,
Did you get any time estimation on when Linkedin should have this solved? Have they said anything? We need to communicate with our customers.
Thanks!
Linus
