DialogFlow PermissionDenied：403 IAM权限“ dialogflow.sessions.detectIntent” [英] DialogFlow PermissionDenied: 403 IAM permission 'dialogflow.sessions.detectIntent'

问题描述

PermissionDenied：403对'projects / XXXX-live / agent'的IAM权限'dialogflow.sessions.detectIntent'被拒绝。

PermissionDenied: 403 IAM permission 'dialogflow.sessions.detectIntent' on 'projects/XXXX-live/agent' denied.

我已将DialogFlow客户端用作

I have used the DialogFlow client as a role while creating the service.

可能是什么问题？

推荐答案

当我在使用服务帐户的权限时，我也遇到了同样的问题。我创建了一个全新的服务帐户，然后为它提供了客户端角色，并且它由于某些未知原因而起作用。
我建议尝试创建另一个帐户，然后为其赋予客户端角色，然后查看它是否适用于该帐户。
而且，这不一定是每个人都可以解决的问题，但是如果您授予该帐户管理员角色，那么您的问题也将得到解决。

When I was playing around with permissions with service accounts, I also encountered the same problem. I created a completely new service account and then gave it the client role, and it worked for some unknown reason. I would suggest trying to create another account and then giving it the client role and seeing if it works for that account. Also, this isn't necessarily a kosher fix per say, but if you give the account the admin role, then your problem will also be solved.

编辑：起初，我认为这可能与创建服务帐户的方式有关（云控制台与命令行），但事实并非如此。由于某些原因，它只是您创建的第一个服务帐户，该客户端帐户不起作用。

At first I thought it might have to do with how the service accounts were created (cloud console vs. command-line), but it seems that's not the case. For some reason it's just the first service account that you create that a client role doesn't work for.

这篇关于DialogFlow PermissionDenied：403 IAM权限“ dialogflow.sessions.detectIntent”的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！