We understand that you are facing issues related to Google Authentication node. Issue seems to be related to your p12 key which was downloaded from your Google service account. May i ask, which browser did you use to download the key? Sometimes Chrome works best as it keeps the binary format intact. Let’s retry to download the key from Google Chrome Browser and check if it resolves the issue.
Also if possible you can check your .p12 file (with key explorer) format as it should be (PKCS # 12). Sometimes it might be something else (BKS, JKS…) and might cause some issues.
Hope this information helps in resolving your issue.
Thanks for the info. I was sent the file by a client to give me access to their GCP environment. Can you recommend a safe application to check the file with?
You can download the explorer with the below link. https://keystore-explorer.org/downloads.html
In case the keys are of format PKCS#12, we can try reissuing the keys from service account from chrome browser and let us know how it goes.
Forgot to inform, yes we should provide password to access the file.
The default password from Google is “notasecret” , But this may vary and it depends on what client has provided while creating the key.
Hi @nagarjun36 … Is it possible to use the Google service account JSON file to authenticate in the “Google Authentication” node, or one of the other nodes?
Hi … the issue has been resolved. There was an issue with the PC12 file that I was given. My client recreated the service account the PC12 file for the connection and I was able to connect.