Forum Discussion
Power BI Embedded Row Level Security
Hi Andy,
Since the "App Owns Data" only use one Power BI account, we can't identify the end users (your application users) with Power BI accounts.
1. No, the users are your application users.
2. In one words, there is only one Power BI account in this scenario. The end users are identified by the tokens. So it won't work here that we assign roles in Power BI Service. Please refer to: #considerations-and-limitations.
>>>Assignment of users to roles within the Power BI service does not affect RLS when using an embed token.
3. Yes, if we assign roles to users in the Service, they must be Power BI users. But this won't be necessary in this scenario. Please refer to the item 2 above for reasons.
Best Regards,
Dale
Hi,
My organisation is considering using Power BI and I have been tasked with looking into how we could integrate it into our solution. I have read a lot of online documentation and a fair few of the "Guy in a Cube" training videos. I guess I am looking for some advise on a recommended approach to embedding power bi into our solution.
We are looking to embed dashboards etc into our web application and therefore would be looking to use Power BI embedded; as we dont want the end user to be aware of or need individual power BI accounts to use it. We currently use keycloak as our authentication provider which issues JWTs to authenticated users (oAuth 2.0). The JWT will contain certain claims that restrict the data the user is able to view. As far as I can tell, there seems to be no way to re-use/issue such tokens to power BI so that we can restrict the data based on their claims.
What is the recommended approach to achieve this?
Would we need to re-create all of our users from keycloak in AAD?
How do I pass the users claims to Power BI and have the service filter the data based on those claims?