I'm just created a new bot and try to make an integration with dialogflow. Yesterday, 2-3 days ago everything was OK.
Today i get this error. Can't find anything similar in internet.
IAM permission 'dialogflow.agents.get' on 'projects/xxxxxxx-06xx-49xx-xx31-2313x47x2xxx1' (not my real but examle of ID) denied.
I have the same exact problem.
The problem is not just in one account, it's happening on all my Dialogflow account.
There is no solution yet.
It's a very annoying problem.
But based on the error message you can try to give a Project owner role to your Dialogflow service account. Maybe it will affect differently for your case.
An additional role for Dialogflow service account:
A similar problem:
This issue should be resolved. You can try to start your integrations again to verify.
Related
I have created an app on Azure Portal to access some information via Microsoft Graph API but I am not able to add any permissions to it. It was working earlier but not any more. I also tried to register a new app, the app gets register but yet again the permissions could not be added.
As soon as I press the button to add the selected permissions these two popup notifications come up ..
1. Your session will end in a few minutes. You will have to refresh your browser to start a new session.
2. The portal is having issues getting an authentication token. The experience rendered may be degraded.
Additional information from the call to get a token:
Extension: Microsoft_AAD_RegisteredApps
This is happening since last 3 days now. I also searched on Google and found that people had similar issues earlier as well. Though I have raised a ticket on the portal for this but haven't received any reply yet.
Any help here would be very much appreciated. Also is there any way to check any logs on the portal itself. I did try to check the network logs via browser developer tools but they aren't much help.
It seems to be an issue with the Azure Portal for your region.
As #Hury Shen suggested, you should contact Azure Support for further investigation.
See how to open a support ticket on Azure portal.
Seems like there was an issue with my account address. I changed the address to one of US and it worked for me.
#Allen Wu Thanks for the suggestions. I had already asked them about it but no one replied.
PermissionDenied: 403 IAM permission 'dialogflow.sessions.detectIntent' on 'projects/XXXX-live/agent' denied.
I have used the DialogFlow client as a role while creating the service.
What could be the problem?
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.
Edit: 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.
I faced the same issue while integrating Dialogflow with external client.
The root cause for my case was that even though I created the service account for my external client, I forgot to add the service account and give "Dialogflow API Admin' Role.
How I resolve: In GCP project, go to IAM > click the top "+ADD" button and search for the service account that you want to grant permission access, choose role type "Dialogflow API Admin"
I solved my error by doing this
from google.oauth2 import service_account
credentials = service_account.Credentials.from_service_account_file(
'C:\\Users\\ashis\\Downloads\\id.json')
def create_intent(project_id, display_name, training_phrases_parts,
message_texts):
"""Create an intent of the given intent type."""
intents_client = dialogflow.IntentsClient(credentials=credentials)
# session_client = dialogflow.SessionsClient(credentials=credentials)
Then I went to the IAM settings for my project
https://console.cloud.google.com/iam-admin/iam?project=
and gave the dialogflow service account members a higher role(like project owner).
You have to give permission to the mega agent.
When I try and call file.getSignedUrl({ action: 'read', expires: '03-01 2500'
}), I am returned the error of Failure from metadata server.
This is code that was previously working (a few days ago) so my gut says something funky happened in the permissions? Is there something I'm missing here?
I found the real cause of the problem.
In the IAM & Admin portal within Google Cloud, the member representing my Firebase Project (i.e. myproject-memberId#myproject.iam.gserviceaccount.com) only had the Owner permission.
I had a flawed understanding, and assumed that this was the highest level of auth, which it evidently is not. At some point, I must have changed it to this "higher" permission, without realizing I removed the Editor permission.
To SOLVE my problem I had to simply add the Editor permission back to my member in the IAM & Admin portal in Google cloud for my project.
Another instance, of human error.
I have encountered "ajaxExtended call failed" error when tried to create a bot using the Azure services. I don't have any SDK bot that I can migrate.
Provided the screenshot below.
Error Screenshot
I had the same issue when I was trying to build a Web App Bot with the same name as one I'd recently deleted. I changed the name and it worked.
Ensure that you have the permission .. in our case super admin was able to do it.
I'm having a problem that I cannot find any information on anywhere on the Internet. I'm sharing an Azure directory with a number of my cohorts, and as such, any number of us might be working on a Resource in the Portal. However, when anyone creates a Bot Service, nobody else can access that Resource. Mind you, whoever creates the Bot Service can do whatever they want with it, but anyone else will see the error "Unable to find the bot with the specified id." (Written as is.)
We know that there's no problem with permissions, as everyone has full access to everything, and the problem only seems to be present for the Bot Service Resource.
UPDATE
All righty; so the problem's been solved. In order to avoid this error, I had to go to the dev.botframework.com website (where MSDN Bot Framework bots are hosted). Then, I went to the "Edit" section in the details panel on the bot's info page:
Next, I added the email addresses (corresponding to the appropriate Azure accounts) of the users who I wanted to have access to the bot to the Admin section's list of Owners:
And that's all there was to it. Would have been a lot simpler to figure out if there was a better error message! Jeeeeeeez.