topic Re: Embeded report in iframe using the API with embedded token in Developer

Embeded report in iframe using the API with embedded token

Nephilim — Thu, 04 Apr 2024 13:00:55 GMT

Hi Community,

I'm working on embedding a PowerBI report in an iframe, doing the API calls myself.

We are using oauth2:

https://login.microsoftonline.com/{TenantId}/oauth2/token endpoint.

Then I do an API call to get our reports:

https://api.powerbi.com/v1.0/myorg/groups/{GroupId}/reports, with body: {"accessLevel": "View"}

Than I generate embedded token:

https://api.powerbi.com/v1.0/myorg/groups/{GroupId}/reports/{ReportId}/GenerateToken with body

{"accessLevel": "View",

"allowSaveAs": "false",

"identities": [{

"username": "XXXXX",

"roles": ["XXXXXXDynamic"],

"datasets": ["72XXXX-XXXXX-XXXX-XX09"] // (from response of previous call)

}]}

Now I want to use all of this to create the source of the iframe. And I can't find out how to do that successfully.

This works but user still needs to login.

I want to use the generated token to do that for me instead. Wonder if this is possible?

Re: Embeded report in iframe using the API with embedded token

Anonymous — Fri, 05 Apr 2024 03:30:45 GMT

Hi @Nephilim ,

Based on my query and research, it's possible to embed a Power BI report using the generated token instead of relying on user login. Here's how you can achieve that:

Obtain the access token using OAuth2 authentication. You've already outlined this step, where you retrieve the access token from the https://login.microsoftonline.com/{TenantId}/oauth2/token endpoint.
Use the access token to call the Power BI REST API to generate an embed token. You've also covered this step, where you call the GenerateToken endpoint.
Construct the URL for embedding the Power BI report in the iframe. You need to include the report ID and the embed token in the URL

You may try the URL like this
<iframe title="Client Portal Report" width="1140" height="541.25" src=https://app.powerbi.com/reportEmbed?reportId={ReportId}&groupId={GroupId}&config=your bearer token generated&$filter=XXXXX frameborder="0" allowFullScreen="true"></iframe>
Replace {ReportId} and {GroupId} with your report and group IDs, respectively. Also, make sure to replace XXXXX in the $filter parameter with the appropriate filter condition if needed.

Best Regards,

Liu Yang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Embeded report in iframe using the API with embedded token

Nephilim — Wed, 10 Apr 2024 10:23:39 GMT

Hi Liu Yang,

Thank you for the quick response.

Unfortunately I dont know if it works, because I get as a response: "The sandbox is too restrictive and preventing correct functioning." It blocked some cookies to "playground.powerbi.com".
So I asked our PBI and System collegues to look into it first...

Kind regards

Marc

Re: Embeded report in iframe using the API with embedded token

Anonymous — Wed, 17 Apr 2024 08:33:26 GMT

Hi @Nephilim ,

Is your problem solved, if so, mark the correct answer as a marker, if not, provide more detailed information and we can help you better!

Best Regards,

Liu Yang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Re: Embeded report in iframe using the API with embedded token

Nephilim — Wed, 17 Apr 2024 09:16:56 GMT

Hi Liu Yang,

I still haven't gotten it to work, but I have a few aditional question though. Using your scrUrl for the iframe, you mention "your bearer token generated". I put the response from the GenerateToken endpoint below to illustrate. It's the long string in the token-key that I have to put in the config param of the url right?

Second question, what is the difference between the url you provided and the one I get back from the reports endpoint (with a much shorter config paran in the url) eg:

"embedUrl": "https://app.powerbi.com/reportEmbed?reportId=8655xxx-xxxx-xxxx-xxxx-xxxx89f1f344&groupId=xxxxe9e1-xxxx-xxxx-xxxx-xxxx84c645e0&w=2&config=eyJjbHVz ... ldHJpY3NWTmV4dCI6dxxxxxx",

GenerateToken endpoint response:

{

"@odata.context": "http://wabi-us-east2-redirect.analysis.windows.net/v1.0/myorg/groups/0386xxxx-xxxx-xxxx-xxxx-xxxx84c645e0/$metadata#Microsoft.PowerBI.ServiceContracts.Api.V1.GenerateTokenResponse",

"token": "H4sIAAAAAAAEAC2Ux66ZgQmga7we ... pmQxLCJhbGxvd0FbnRlcm5ldCI6dHJ1ZX0=",

"tokenId": "fb74xxxx-xxxx-xxxx-xxxx-xxxxf4d53b49",

"expiration": "2024-04-17T09:49:01Z"

}

Re: Embeded report in iframe using the API with embedded token

vdmc — Fri, 28 Jun 2024 13:57:15 GMT

Hello @Nephilim
Have you managed to make it work? I'm considering using this path you presented, but your last message said it wasn't working and I would like to know if it is indeed a viable way to achieve our goal.

Re: Embeded report in iframe using the API with embedded token

Anonymous — Tue, 23 Jul 2024 14:44:29 GMT

@Nephilim were you able to find out the reason?

Re: Embeded report in iframe using the API with embedded token

Hari_Adinovus — Mon, 23 Dec 2024 08:34:03 GMT

@Nephilim Found any solution? for "The sandbox is too restrictive and preventing correct functioning" error

Re: Embeded report in iframe using the API with embedded token

vdmc — Mon, 23 Dec 2024 13:09:11 GMT

Hi, @Hari_Adinovus.
You may wanna check this Forum: Solved: Re: When clicking on Sign-in on embedded report no... - Microsoft Fabric Community.
It's not exactly the same link used to iframe presented here, but it's a very similar problem that also had the same message "The sandbox is too restrictive and preventing correct functioning"