Google Events nodes OAuth configuration lost

Hi guys, I have 2 workflows where I use 2 Google Calendar nodes to create and to delete events from my primary Google Calendar. The problem is that the after configuring the authentication of these Google Calendar nodes, the authentication information seems to be lost. This happens several minutes or hours after the latest authentication configuration. The message I get when this happens is the following one: { "error": { "code": 401, "message": "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.", "errors": [ { "message": "Invalid Credentials", "domain": "global", "reason": "authError", "location": "Authorization", "locationType": "header" } ], "status": "UNAUTHENTICATED" } } Please, have a look at the attached screenshots too 😉 I have logged out and in the authentication information for the Google Calendar nodes several time and I have removed and added the Google Calendar nodes to start from scratch but the issue persists 😦 Anything I could do from my side to fix this problem? 🙂 Thank you very much!!! Cheers.
No description
No description
No description
Solution:
Click on the last text link if it says (advance).
Jump to solution
10 Replies
Gaurav Chadha
Gaurav Chadha8mo ago
Hi @Germán Toro del Valle, could you please share (copy/paste) the full message error here, which you are getting as result? Als, can you try it on a fresh workflow?
Germán Toro del Valle
Hi @Gaurav Chadha !!! 🙂 First off, thank you very much for your reply 😉 What full error message do you refer to? 🙂 The error I get when testing the workflow from buildship.app or consuming the endpoint is: { "error": { "code": 401, "message": "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.", "errors": [ { "message": "Invalid Credentials", "domain": "global", "reason": "authError", "location": "Authorization", "locationType": "header" } ], "status": "UNAUTHENTICATED" } } On the other hand, I have tried to remove and to add a brand new Google Calendar node several times as well as creating new workflows from scratch with the same result 😦 Would you like me anything else to try? 🙂 Thank you very much!!!
Gaurav Chadha
Gaurav Chadha8mo ago
Hi @Germán Toro del Valle We are making some more updates to the OAuth access management, we'll update you when fixed.
Germán Toro del Valle
Looking forward to it ❤️ Any news?, @Gaurav Chadha ☺️
Gaurav Chadha
Gaurav Chadha8mo ago
Sorry I missed replying you. Can you retry logout and login again from the GCal OAuth node?
Germán Toro del Valle
Right now 😉 I'll keep you posted 🙂 Looking good for the time being 🙂 Let's see how it evolves :p
Germán Toro del Valle
BTW, I passed through this page I do not know if you are aware of (I guess you do :p)
No description
Germán Toro del Valle
I could translate the page into English if you need me to :p
Solution
Gaurav Chadha
Gaurav Chadha8mo ago
Click on the last text link if it says (advance).
Germán Toro del Valle
Yeah, yeah, I did since I deeply trust you ☺️ Just wondering if you were aware of this 😜 On the other hand, let me share with you that it is working today so the issue seems to be fixed 😍 Thank you very much, @Gaurav Chadha !!! ❤️