Power BI iFrame Error ClientSideAuth

[Anonymous]

Hi,

I just facing very new issue when accesing PBI from iFrame.

Here is the detail.

The signin given wierd url, when we click signin :

https://app.powerbi.com/reportEmbed?reportId=xxxxxxxxxxxxxxxx&autoAuth=true&ctid=xxxxxxxxxxxxxxxxxxx...clientSideAuth=0&fallbackError=%7B%22flow%22%3A%22Reportembed%22%2C%22info%22%3A%22pkce_not_created%3A+The+PKCE+code+challenge+and+verifier+could+not+be+generated.+Detail%3ATypeError%3A+Cannot+read+properties+of+undefined+%28reading+%27digest%27%29%22%2C%22code%22%3A%22pkce_not_created%22%7D

And also this iframe only can loaded the signin by using auth office.com with localhost url.

Can some one help to provide any information regarding this issue ?



Update:
Solved
Assign local certificate on IIS (Self Signed Certificate) on IIS if you want running on HTTPS but for local environment.

[FabricioCoder]

I have the same problem here when calling reports using "iframe" that had been working for a long time as of 18/12/2023, they started to present this problem observed on HTTP servers, but HTTPS servers continued to work correctly! How should I proceed to resolve this problem? Did anyone manage to fix it?

(All report access accounts are associated with a Power BI-Pro account.)

Will it be necessary to use an SSL certificate on the server? Where is this information in Power BI? (always worked normally on HTTP servers)

[Anonymous · Accepted solution]

Yes, for local i just give it a local IIS certificate to make it https.
Self Signed Certificate.

[CGomezP]

Hola buen día FabricioCoder,

te escribo desde Mexico, preguntando que solución le diste, ya que tengo el mismo problema

[alfonsoalmada2]

Hi guys, I got the same error... 
It only works with localhost but once we deployed the app, we got same issue.
Did you solve it?

[Anonymous]

Hi @Martin_D ,

But in previous, i have no issue using http://172.18.100.162. Ok let me try using https now, maybe this is a new security patch from PBI.

Thanks for idea man.

[alfonsoalmada2]

Hi @Anonymous , 
did you solve it? 

[Anonymous]

Yes, for local i just give it a local IIS certificate to make it https.
Self Signed Certificate.

[Martin_D]

Hi @Anonymous ,

Are you sure it only works with localhost? To me it looks like the web-browser won't send the authentication token to an unsecure server. Have you already tried calling 172.18.100.162 using https protocol and a trusted certificate?

BR
Martin