The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now
Hello Guys!
I've developed an application using power bi embedded that performs authentication on the portal to access a specific report. Everything works perfectly, but sometimes I get the error illustrated. What could be causing it? Has the token expired? Could the user be accessing during the scheduled update of the report? Thanks.
Solved! Go to Solution.
Hi @Fcunha,
As we can see from the error message, the Http Status Code 403 means something wrong with the authentication. Please check these things below.
1. The token could be expired.
2. Is the App workspace assigned to a capacity? Maybe the resource run out. Please refer to embed-sample-for-customers#create-a-dedicated-capacity.
Best Regards,
Dale
We are getting this error as well with an embedded report using Embed for Your Customers. Not all the time but several times a day. The page renders successfully but after a short time (well before the 1-hour token expiration time) upon clicking on a visualization, the visualization shows the error (X) with a See details link, which shows the error below. It seems to occur after a short period of inactivity. We have recreated it in Chrome, IE, Firefox and Edge.
I can refresh the page (which reuses the existing token) and the report re-loads and functions as it should. (Since original post, it occurred to me that our code will new the token when the page is refreshed. Regardless, we are getting errors well before the expected expiration of the token.)
I see this question is marked as resolved, but no indication of which of the suggestions resolved the issue. Further, I don't think our token is (or should be) expired.
Any idea what might be going on or how to troubleshoot further?
I believe we were causing our issue. We developed a common web site for embedding reports, essentially passing Workspace Id, Report Id, Effective Identify User Id and Effective Identity Role. The Azure Access and Power BI Embed tokens were saved as a global variables. I believe a new embed token was generated each time a user accessed the site to embed a report but the Azure Access token was not regenerated. Other users would then get errors when they altered filter criteria, etc., on their reports generated with tokens that were expired when most recent token was generated. I believe we changed the process to generate a new Access and Embed token for report request. Or at least I think it was something like this.
Hi @Fcunha,
Could you please mark the proper answers as solutions?
Best Regards,
Dale
Hi @Fcunha,
As we can see from the error message, the Http Status Code 403 means something wrong with the authentication. Please check these things below.
1. The token could be expired.
2. Is the App workspace assigned to a capacity? Maybe the resource run out. Please refer to embed-sample-for-customers#create-a-dedicated-capacity.
Best Regards,
Dale
Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.
User | Count |
---|---|
17 | |
2 | |
2 | |
2 | |
1 |
User | Count |
---|---|
19 | |
10 | |
5 | |
4 | |
3 |