Did you check scopes?
LinkedIn allows me to sign in and accept the scopes that I send in the AUTH, but when it redirects back to my appâs page, it returns that error
Could you share some screenshots of the process and if you tried on another app for the purpose of debugging?
Yes, but if you donât have scopes to access user info, you will get unauthorized to the endpoint entered in user info field.
Here are screenshots of the relevant plugin configuration, my LinkedIn definitions for the app, the login and the authorization pages, and the error popup that is displayed after redirection back to the app:
Full details of the error that I get when I open in the bubble debugger:
API Connector error: the Oauth2 API LinkedIn AUTH login is not configured properly - Received error from api The service this service just returned an error (HTTP 403). Please consult their documentation to ensure your call is setup properly. Raw error:
Unauthorized
You must be authenticated to access this page.
I tried this redirect link as well as the generic redirect link, and also different scopes of permission, but I get the same error back. Any ideas?
Have you tried with âopenidâ instead of âprofileâ scope?
Hard to see, please check the following article: How to create a sign-in via LinkedIn and collect the primary email address on Bubble | by Shenal Harakh | Medium
Although not possible for photo and name, rather linkedin email and id (which my app also uses with no issues)
@another Tried all combinations of scopes. None worked. Even tried setting up a new App in LinkedIn with only the openid functionality added. Still the same results. Followed the tutorial you sent in the link. Maybe OAUTH needs to be configured differently if my app is given the openid permission, I donât know, but I didnât find a way to only get the r_liteprofile permission granted.
The error says itâs on the API Connector side. Can you please follow the steps from the link and thread shared previously, make sure to copy/paste texts, rather of writing it manually, also for API connector to be on the latest updated version, Linkedin auth to be right with the API Connector.
Do you have any workflowâs after in relation, as it seems the Linkdin auth passes, and when it comes back to the appâs loggin page, the issus arise?
I followed everything to the letter. I tried every variation I could think of and even updated to conform to the recent changes made by LinkedIn (use openid scope and profile endpoint). I also created a new page in the app that only has a button and an alert. The button tries to login and the workflow only shows an alert afterwards. Nothing works. It keeps coming back with the message, you have to be authenticated.
I tried logging in with Postman and managed to do it but it didnât work until I changed the option Client Authentication to âSend client credentials in bodyâ. It then returned an Access Token that I used in a different GET call to retrieve the profile and the image successfully. The callback url Postman uses is âhttps://oauth.pstmn.io/v1/browser-callbackâ.
These are the settings of the authorization in postman:
This is the subsequent GET call that I use to retrieve profile (it works):
I really canât figure out what the problem is.