Forum Discussion
Integrate PowerBI Embedded report and Paginated report with RLS
Yeah in App-Owns-Data scenarios, we're a bit more limited. That said depending on your specific sceanrio, you can also look at the embed-token user filters. The application would need to specificy the user name on the token, then do filtering in the report (this is a secure method). Just look under the "passing the configured parameter using the embed token" at:
https://docs.microsoft.com/en-us/power-bi/developer/embedded/paginated-reports-row-level-security
Otherwise, at a later date we are looking at using identify blobs, where a token can be used to do real "Single Sign On" auth to the data source.
Hope that helps!
Anonymous , RLS with embedded
https://www.youtube.com/watch?v=yNF-_l2f7w0&feature=youtu.be
Paginated embedded
https://docs.microsoft.com/en-us/power-bi/developer/embedded/paginated-reports-row-level-security
As mentioned earlier, we are already implementing PowerBI Embedded with RLS as of today.
In addition, I have already read the Paginated Embedded documentation earlier and I found it's difficult to understand the configuration especially how to link PowerBI Report and Paginated report together in consideration of passing the UserId from one to another.
Hi Emily - one thing to check, is what style of embedding you are doing. If you are using user owned vs app owned data for the pagainted report. Note that only in user-owns-data sceanrios will the user's context be passed through, and the documented RLS "trick" of filtering on user id in the pagainted report work. https://community.powerbi.com/t5/Developer/App-vs-User-Owns-Data/td-p/300729. Support for app-owned-data scenarios in this case are not yet supported.
One thing you might do (depeding if this is a security filter or not), you could pass the filter context on the pagainted report URL and bind it to a report parameter. Like shown here https://docs.microsoft.com/en-us/power-bi/paginated-reports/report-builder-url-parameters. Just note that anyone could manually change the value, so don't use it for securing data between users.
Jon-Heide Thank you for your reply and well noted your point.
We are using App Own Data for our PowerBI Embedded (external customers), so I think right now there is no way to pass the RLS parameters from PowerBI Report to Paginated Report in a secure way by configuring the URL itself.
I think this is a limitation of PowerBI itself and I hope there will be a solution by Microsoft in the future.
Thanks again for your help!
Yeah in App-Owns-Data scenarios, we're a bit more limited. That said depending on your specific sceanrio, you can also look at the embed-token user filters. The application would need to specificy the user name on the token, then do filtering in the report (this is a secure method). Just look under the "passing the configured parameter using the embed token" at:
https://docs.microsoft.com/en-us/power-bi/developer/embedded/paginated-reports-row-level-security
Otherwise, at a later date we are looking at using identify blobs, where a token can be used to do real "Single Sign On" auth to the data source.
Hope that helps!