Hi,
Have wake up, your toke is not valid, and last 7 user registrations where data is missing.
Have you experieced this before and how to deal with the Token expiration?
Thanks!
In API Connector, Bubble will not refresh your token (But just for API Connector when you create it and initialize calls).
It shouldn’t affect user login. Refreshing token is handled by Bubble for users.
If you need to create / reinitialize call, you need to redo the same process as the first time to get a valid token (run in debug_mode=true)
1 Like
Not sure about this, because when token is exipired, and when new member creates a profile via the Linkedin (API Connector), there is no Linkedin ID, nor the email fetched from the Linkedin in the new user database, despite user being able to login, wierd 
Will try to check more often when working around the API Connector, it might be how the token expires bit later, rather right away when you touch the API Connector.
Once the token is expired, you can’t see, when you click on the expand, you see. If the element is not expanded, you can’t know, you need to expand, and then is the same, if it was or not expired, because it will be.
When you validate the token, and you press the same button, I am not sure if token is still expired or not because the element is closed.
Is there anywhere else to see if token is expired, just to be sure about it because is very sensitive thing in relation to the new users.
Again happend, it seems the trigger is not on the “expand” button, rather on the Plugins > API Connector… This time haven’t clicked expand button, rather just went to see if it will validate the token with the Linkedin login under debuger mode, and yes, it has been validated, which means token was expired…
Again…
Registered user without Linkedin ID and email…
If I now go to the API Connector and expand the credentials, it will say the token is expired, but how to now before hand or why it has been ispired, haven’t touched the API Connector…
Have already submited Idea to add a notifications, and have published two threads about it, what to do?
@mikeloc 
@adamhholmes
Thanks!
Again, API connector itself never refresh expired token. You need to get a new one following the same process you did yo get the first one to be able to edit calls in API connector. But it shouldn’t affect front end users. Only backend dev in API Connector if you need to edit it
1 Like
Thanks for the response here!
Well, there is a new user without a Linkedin Id and email, and the only way to create a profile is via Linkedin (API Connector). How I can know if the API C. token is not expried? If I look inside, of course it will be…
Any other way to troubleshoot this?
So what I understand, you use linkedin as auth provider to create new user? When you say they don’t have email and ID, what is your workflow after signup with social network?
Yes, it goes through the API Connector…
And then having the changes to the data when page is loaded, or after the Linkedin login is passed…
Update here: when the user is logged in through LinkedIn and the page starts to load, the user might click the refresh button on the page or close the page, and there the data (Linkedin ID and email) might be lost.
The good thing is that if there is a workflow on the login page with the condition that the user doesn’t have a LinkedIn ID, to make changes to the user data and update the LinkedIn ID (and email), it will update the right user, although I am not sure how this is done as there is no data between the user and their LinkedIn credentials at that moment.
Question here: If we add a workflow action behind login with Linkedin (authentication), the next action will be to update user data with Linkedin ID and email. Is this the right way to set up?
Bubble have the data about the logged in user (even if you don’t see it in DB, Bubble store in an hidden field, the linkedin ID). Any update/create action after the user is logged in will be on behalf of this user. Any request made using the API Connector with this oauth connection will be made on behalf of this user too.
1 Like
This is very good; then, how Bubble saves LinkedIn IDs in the database and saves the case here. It is much easier to breathe as well. However, if there is a button to “login with LinkedIn”, and the user clicks, the following actions are taken: To trigger the LinkedIn authentication > Make changes to the user’s LinkedIn ID and email field. This workflow action will be executed after the authentication (on another page). The workflow will continue after the authentication?
@another Sorry to barge in on the conversation, but could you please show how you defined the AUTH flow in the API Connector configuration? I don’t understand how to continue the authentication flow after the authorization key is sent back from LinkedIn. Do I define another call within the same API or do I need a new API? Is there a tutorial somewhere?
1 Like
@mayaorr1010 To initiate the auth is in the runmode (version-test) [debug_mode=true].
@another I understood that part, but do I need to have a POST call defined in my API Connector plugin’s configuration within the LinkedIn API where I defined the AUTH that I need to call in my workflow after I get the redirection response somehow?
1 Like
@another Thanks for the detailed response 
I tried it and I’m getting to the login page of LinkedIn where I authorize my app, but then it returns back to my app page with a 403 error that says: >Unauthorized
You must be authenticated to access this page.
Any ideas how to solve this?
1 Like
How about Linkedin dev > Auth > Authorized redirect URLs for your app?
@Jici Here might be the tirgger for the “not valid token”? Although there was definitelly time when there was much more than 2 months…
That was what I thought too, I tried both the generic url redirect and a specific page url but both of them did not work.
1 Like