Forum Discussion

mork's avatar
mork
Helper V
10 years ago

Possible bug with RLS

So a couple of days ago I was experimenting with RLS trying to see if I could use it for my dataset. I ended up giving up on it. But I didn't delete one rule that was about a single test user having access to some rows.

 

I though that leaving it wouldn't matter since it's only a test user and the rest of the users would have the same access as before since there weren't any rules about them. That wasn't the case though because after all the visuals in all the reports for all users where empty. it only displayed a message saying something along the lines of "The visual cannot be displayed" or something. 

 

 

Only me as the admin had access to everything and all the visuals worked. After I deleted the last rule aout the test user everything started working again. I don't believe this is expected behavior by the RLS. Creating a rule for a user making the rest users unable to see anything?

7 Replies

  • ankitpatira's avatar
    ankitpatira
    Community Champion

    mork what you're experiencing is actually the expected behaviour and atleat what I would expect. When you decide to implement RLS you're saying you want to restrict access to data within that report and so that means from that point on any user you want to share this report with you have to explicitly put them under a role in RLS. If you want user to see everything then you leave DAX filter empty for that role but you have to add them to a role. I would consider this as a good design becuase imagine if you had a user that you've shared report with but forgot to add him to a role and so now he is able to see everything within report even though you have RLS implemented.

     

    Hope that make sense.

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      To put it a simpler way, RLS is like any other security measure: if you only give one person the key, nobody else is getting through the door.

  • sicoobes's avatar
    sicoobes
    Regular Visitor

    I have same problem, error "status code Http401", version 13.0.1500.307.

     

    Portuguese language

    Código de status Http401

    ID da atividadea6929675-0667-4f2a-bb41-520fcc1232d5

    ID de correlação077b48fc-4e71-59da-057a-440542bbf145

    Solicitar ID88fee152-131d-d10d-182f-5f51efb519c8

    HoraTue Jun 28 2016 14:31:08 GMT-0300 (Hora oficial do Brasil)

    Versão13.0.1500.307

    Cluster URIhttps://wabi-south-east-asia-redirect.analysis.windows.net

  • sicoobes's avatar
    sicoobes
    Regular Visitor

    Hello, i from Brazil, and I have same problem.

     

    Portuguese Language:

    Código de status Http401

    ID da atividadea6929675-0667-4f2a-bb41-520fcc1232d5

    ID de correlação077b48fc-4e71-59da-057a-440542bbf145

    Solicitar ID88fee152-131d-d10d-182f-5f51efb519c8

    HoraTue Jun 28 2016 14:31:08 GMT-0300 (Hora oficial do Brasil)

    Versão13.0.1500.307

    Cluster URIhttps://wabi-south-east-asia-redirect.analysis.windows.net

     

     

     

     

     

     

    • sicoobes's avatar
      sicoobes
      Regular Visitor

      Dear

      The following RLS error again . It seems field problem because the domain ".com.br" is hosted in Singapore. I tested with another domain hosted in southern Brazil and it worked.

      Could you help me because my model stopped working.

      Thank you.

       

      • Anonymous's avatar
        Anonymous
        Not applicable

        sicoobes That sounds like an actual bug that you should report to Microsoft. Send a frown.