Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service Principle for Gateway #1067

Closed
v-kerwan opened this issue May 20, 2019 · 5 comments
Closed

Service Principle for Gateway #1067

v-kerwan opened this issue May 20, 2019 · 5 comments
Assignees
Labels
assigned-to-author Issues label doc-enhancement Issues label needs-more-info Issues label

Comments

@v-kerwan
Copy link

Please add this information and below Link to this page:
https://docs.microsoft.com/en-us/power-bi/developer/embedded-row-level-security#on-premises-data-gateway-with-service-principal-preview

On-premises data gateway with service principal (Preview)
Customers that configure row-level security (RLS) using an SQL Server Analysis Services (SSAS) on-premises live connection data source can enjoy the new service principal capability to manage users and their access to data in SSAS when integrating with Power BI Embedded.

Using Power BI REST APIs, allows you to specify the effective identity for SSAS on-premises live connections for an embed token using a service principal object.

Until now, to be able to specify the effective identity for SSAS on-premises live connection, the master user generating the embed token had to be a gateway admin. Now, instead of requiring the user to be gateway admin, the gateway admin can give the user dedicated permission to that data source, that allows the user to override the effective identity when generating the embed token. This new ability enables embedding with service principal for a live SSAS connection.

To enable this scenario, the gateway admin uses the Add Datasource User REST API to give the service principal the ReadOverrideEffectiveIdentity permission for Power BI Embedded.

You can't set this permission using the admin portal. This permission is only set with the API. In the admin portal, you see an indication for users and SPNs with such permissions.

@maggiesMSFT
Copy link
Contributor

Hi, @v-kerwan -- Thanks for your suggestion! I've added a few people who can help.

@markingmyname
Copy link
Member

@v-kerwan

So we are clear, which page are you requesting to be edited? Is it the RLS page or the main Service Principal page?

@markingmyname markingmyname added the needs-more-info Issues label label May 23, 2019
@v-kerwan
Copy link
Author

v-kerwan commented May 24, 2019 via email

@markingmyname
Copy link
Member

Hi @v-kerwan,

Thanks for clearing that up.

We decided to keep it with the RLS information as the information fit more in that space.

However, we should have had a reference to it in the main Service Principal article.

As such, I have added a link to that section from the Service Principal article to the RLs article in the Next steps section.

The article should show the change early next week.

Did you know: For minor things like typos, you can edit the doc! Click the little Edit pencil icon in the article, then click the little Edit pencil in GitHub, make your change, scroll to the bottom, and click Propose file change. And voila! It's sent directly to the writer. Then all the writer has to do is sign off and it goes into the publishing queue.

Hope this helps.

Thank you again!

@markingmyname
Copy link
Member

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion, and we will reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned-to-author Issues label doc-enhancement Issues label needs-more-info Issues label
Projects
None yet
Development

No branches or pull requests

5 participants