Forum Discussion
Sign in fails for embedded report
- 2 years ago
Looks like I found the answer to my own question. The embedded code is hosted on an internal only web application using HTTP. That's no good anymore, has to be on HTTPS now for the embedded visual to load. I'll have to submit a ticket to our IT to get a SSL cert installed on the web server. 😞
- 2 years ago
Registered just to reply.
I have PowerBi reports embedded to nwjs.io application, and reports stopped working. Had to use chrome.webRequest.onBeforeRequest to remove &clientSideAuth=0 from the url to get reports working.
Thanks for pointing me to the right direction.
Hey, I'm having the same issue but instead of a nwjs.io app, I have it on Flask and tried requestly api to perform the same change in the URL as you did with chrome.webRequest.onBEforeRequest but not working correctly unless I open the embedded report in a new tab. How did you do the webrequest? so I can try that option while we get IT to perform a deeper troubleshooting.
thanks in advance!
Hi, My bubblegum sollution was basically just using addListener to try replace "clientSideAuth=0" with nothing if it exists. It's been working so far, but i believe somebody more skilled can make it neater.
chrome.webRequest.onBeforeRequest.addListener(
function(details) {
return {redirectUrl: details.url.replace("&clientSideAuth=0","")};
},
{urls: ["https://app.powerbi.com/*"]},
["blocking"]);
Other option that is untested but could work. Create separate file that you request when you need to open powerbi report. for example.
powerbi.html?report=[url to powerbireport]
then replace clientSideAuth from report url parameter and redirect to the new url with for example window.location.
Microsoft hopefully at some point starts fixing things that doesn't work and stops breaking working things.