Forum Discussion
Power BI REST API "An error occurred when invoking the authorization extension."
All;
I am facing this issue when trying to use some REST API contexts on our Power BI On-Premises instance.
Using : https://servername/reports/api/v2.0/folders
we receive this error in the server's response.
{
"error":{
"code":"1251","message":"An error occurred when invoking the authorization extension."
}
}
I suspect it is a permissions error because it works for admins, but no longer for users. I have yet to uncover where the problem lies.
This works as expected and servers up the available contexts for all users
https://servername/reports/api/v2.0/
I am hoping you have some guidance or suggestion.
Thank you cordially
Thank you for that information.
I went thourgh it and it didn't solve my issue.
I put users are the 'root' or top level and no change was made.
I did stumble on this though.
When I use the API and add a ItemID I get a valid result.
https://servername/reports/api/v2.0/folders({id})
6 Replies
Hi, pdunbar
Not very clear about your question. I can't reproduce your scene. What did you do with this api url?
Best Regards
Janey Guo
Janey;
Thank you for your reply.
We use the api to get a list of all the folders in our Power BI instance. As it stands, only server admins can access the data the api should provide.
It is not really a valid option to grant power users administrative privileges
Is there some server permission or role I need to assign users to inorder for them to access the the api data?
Hi, pdunbar
Not sure if it is a permission problem, have you tried to give users other permissions, such as browser?
Reference:Role definitions - predefined roles - SQL Server Reporting Services (SSRS) | Microsoft Docs
If it doesn't solve your problem, Please feel free to ask me.
Best Regards
Janey Guo
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you for that information.
I went thourgh it and it didn't solve my issue.
I put users are the 'root' or top level and no change was made.
I did stumble on this though.
When I use the API and add a ItemID I get a valid result.
https://servername/reports/api/v2.0/folders({id})
I just realized I made a mistake in my request for support...
the URL should read more like
This works as expected and servers up the available contexts for all users
https://servername/reports/api/v2.0/folders
