Forum Discussion
Row Level Security for on prem analysis services stopped working
Hi benmarriott, I would suggest that you run a SQL Profiler on your SSAS Tabular Instance and ensure that the effictive username is getting passed from the Power BI Service to your SSAS Tabular model.
You can refer to this blog post by the Power BI Team
https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem-tshoot/
Or this community post which explains it in more detail.
Thanks GilbertQ
So I've run the Profile trace and it's showing my credentials when I access the Power BI service (web) by logging in as another user when running any queries.
Given that previously the security on the SSAS was working in Power BI something has changed and now it's passing my credentials rather than the user who's using the service. The only thing I can think is that I have added some additional users and mapped their credentials (our [email protected] email is XXX-DOM\XXX) but I don't really see how that would affect it...
I've tried updating the gateway to the latest version and it's not helped.
Any other ideas?
Cheers
Ben
- GilbertQ9 years ago
Super User
benmarriott I would recommend reading these blog posts.
https://powerbi.microsoft.com/en-us/documentation/powerbi-admin-power-bi-security/
https://powerbi.microsoft.com/en-us/documentation/powerbi-gateway-onprem-indepth/
I do recall reading somewhere about how to ensure that there is the mapping from the Power BI Service through to your On-Premise SSAS Tabular Model. I can remember that somewhere there is an option to actually do a manual mapping from a username through to a UPN in your organisation. I cannot just find the link right now.
I found it! And I think this is what you might need to do below.
- benmarriott9 years agoFrequent Visitor
GilbertQ I've already mapped the user names as it was all working previously! If they weren't mapped then they wouldn't be able to access the data at all.
Any other ideas?
- GilbertQ9 years ago
Super User
Hi benmarriott, I am all out of idea's
Something must have changed and when you run the trace is it still passing the wrong credentials?