Forum Discussion

AlexeyRusinov's avatar
AlexeyRusinov
Icon for Helper II rankHelper II
10 years ago
Solved

Enterprise Gateway with Analysis Services not passing logged in users credentials

Hello everyone, I am trying to set power BI live connection to SSAS data warehouse. I need to set security model, so I create different roles and users in SSAS instance. When open power BI from non-...
Need Help
  • AlexeyRusinov's avatar
    AlexeyRusinov
    10 years ago

    Hello everyone,

     

    The issue's fixed now. The user was admin on the server, and in SSAS config there is a property <BuiltinAdminsAreServerAdmins>1</BuiltinAdminsAreServerAdmins>.
    As a result, even if the user is not shown as an admin in SSAS, he was, because of server admin and this property. 
    So, either changing property to 0 or removing user from server admins solved the issue.

    Thank you everyone who tried to help. 

AlexeyRusinov's avatar
AlexeyRusinov
Icon for Helper II rankHelper II
10 years ago

Hello everyone,

 

The issue's fixed now. The user was admin on the server, and in SSAS config there is a property <BuiltinAdminsAreServerAdmins>1</BuiltinAdminsAreServerAdmins>.
As a result, even if the user is not shown as an admin in SSAS, he was, because of server admin and this property. 
So, either changing property to 0 or removing user from server admins solved the issue.

Thank you everyone who tried to help. 

  • apetersen's avatar
    apetersen
    Regular Visitor
    7 years ago

    Hi Guys

     

    We having the exact same issue, problem is we have RLS security implemented on our tabular model (we have a security table setup on sql with these particular email addresses) we then deploy to from the tabular model to SSAS and  then hit a live connection on PowerBI. Now the problem is when logging on to POWER BI desktop or web with the user (non admin) we still seeing all rows and filters? When checking this in excel the filter applies? Our On Premise gateway is setup with the "admin user yes" but surely Power BI is smart enough to fiugure this out.

     

    Steps we have taken

    - User in Question is Read only on SSAS properties

    - is not a member of the admin group on SSAS

    - ON premise gateway and not personal gateway