Creating a JSON Service Account Key

[Neil_Plantz]

Hi
I keep getting an error when I try to create a JSON Service account key. I am using a paid Google Workplace account. The error (attached) just keeps saying 'Please Try Again' but no matter what I do, I get the same error. I've tried deleting and starting over. Checked all my permissions and compared every setting I could find on this account to my other account (below).

I am trying to integrate my DialogFlow to Soul Machines.

To make matters worse, my other non-paid Google Account, DOES create a key. The one difference appears to be that on this account there is a role called 'DialogFlow One-Click Integration Agent' that isn't on the main account (above).

Any one else encountered this and found a solution?

 

[zhuht]

Hi Neil,

Thanks for reaching out. Is this for App Integration or Connector product? If so, could you provide more information around this, e.g did you get this issue when creating a AuthProfile or something different? Or, if this is not about those 2 product, kindly ask to use the correct tag in order for this question to be routed effectively. Thanks!

[Neil_Plantz]

Hi, it's for an App integration, specifically, from Conversational Agent to SoulMachines.com

I get the error when I try to create a JSON Key (as instructed by the Soul Machine documentation) in my Google Cloud > IAM > Service Account.

Frustratingly, I don't get the error when I use my free Google Account, only when I use my paid Google Account (this one). My suspicion is my account credentials have got snarled up somewhere in the Google Cloud workspace (likely my doing), preventing the JSON key from being created. 

I'm super keen to launch a video agent driven by Google's Conversational Agent, so any help is much appreciated.

[zhuht]

Hi Neil,

If I understand correctly, this is related to SoulMachines about creating JSON key. I'll try to have it routed to the DialogflowCX team for this. Thanks!

[Neil_Plantz]

I'm still getting the error message and it's been 2 weeks since I asked for help. I've gone through every permission I can find, switching on everything. I've given authority to the SoulMachine OAuth 2 Client ID (116003172620036743753) in Google Workspace. I've given all the Dialogflow permissions I can find to my own account (PII Removed by Staff). And it still won't create the JSON key I need. All I want is for someone to take a look and tell me if I've done something wrong or if it's an error on Google's side. I've used Google products for years and the first time I ask for help I feel totally ignored. 

[AlexET]

Hi @Neil_Plantz, thank you for reaching, we sincerely appreciate your patience and understand how frustrating this situation must be, and assure you that we’re here to help.

We apologize for the delay in support on this thread. I’ve escalated this internally to ensure it reaches the right team, and we’ll keep you updated as soon as we have more information. Your feedback is incredibly valuable, and we truly appreciate your patience while we work toward a resolution.

[dchiesa1]

It is possible in a Google Cloud Organization to completely disable the creation of downloadable JSON key pairs for service accounts. 

There is an "organization policy constraint"  named iam.disableServiceAccountKeyCreation , which, when set, disallows what you are trying to do. It does not matter what permissions you have, it is simply not allowed.  I am not sure of the shape of the error you would see in the UI if this constraint is set to disable service account key creation. I haven't tried it.  I would think the error would be something like this.

But it may be something for you to look into.  check this article for example. 

If not that, try creating a different service account, and try creating and downloading a key for THAT one. 

[Neil_Plantz · Accepted solution]

Hi

Thank you, dchiesa1. I eventually got it working, and this was indeed a factor. I also had to set up my organisation, I think. 

tbh, none of it was very clear and the Google Platform is a nightmare to navigate. I appreciate that GC is immensely complicated, with so many services packed into one console, but the downside is the learning curve to figure it out is very time consuming. BUT, that said, I got there in the end and my trained video agent, powered by Dialogflow, worked! Only for us to then decide it wasn't what we wanted so I've now moved onto using Datastax 🙂

Ah well.

Thank you though, N