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!
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!
This limit is still present at this day. Although i would like to share a solution:
When user sends embedurl request to your application, your application can generate an app "session token" (saved to db with related context , userid, ...). User can then request power bi paginated report with this "session token" by url parameter.
The report can then resolve it's user_id parameter value by retrieving it from db using this session token.
Although not straightforward solution, it's secure and only way found in a app owned embedding where RLS is not applicable.
Hope this helps someone.