6.4 How to implement RLS in Apache Superset

Поділитися
Вставка
  • Опубліковано 4 гру 2024

КОМЕНТАРІ • 14

  • @eduardovaz1971
    @eduardovaz1971 5 місяців тому +1

    Thank you so much, your videos came just in time for us to use the embed feature. Really helped, you understand the ins and outs of superset really well.

    • @ShantanuKhond
      @ShantanuKhond  5 місяців тому

      Thank you so much for your support! Glad I could help.

  • @biologadosdados
    @biologadosdados 2 місяці тому +1

    Thank you! It was really helpfull!

  • @ipsitasahu9821
    @ipsitasahu9821 6 місяців тому +2

    Thank you so much for your help.can you guide us how to handle this if it comes to large end users.how to dynamically filter the table based on the users who logs in

    • @ShantanuKhond
      @ShantanuKhond  6 місяців тому

      Hey. I almost forgot about it. For now i will put it in GitHub and then will record the video. If you need any help feel free to ping me.

  • @gabrielgarcia-x4q
    @gabrielgarcia-x4q 22 дні тому +1

    Hello, I would like to ask a question. I'm testing using superset in a scenario where there are more than 1000 users, each user with a different email address. And in this case of creating a role for each user or a filter for each user, it would be complicated. And I need each user who accesses with their unique email to have access to only the information on their dashboard, filtering by user. Is there any easier and faster way to create this?

    • @ShantanuKhond
      @ShantanuKhond  21 день тому +1

      If you only need restricted access to dashboards meaning limited data only what they want to see. Then you can use dynamic query. Basically you can create a mapping table and use it to filter using username. You can get supetset current user's username in sql query in superset.

    • @gabrielgarcia-x4q
      @gabrielgarcia-x4q 21 день тому

      ​@@ShantanuKhond Nice, thanks for the response. Do you have any related video ?

  • @MohamedMontaser91
    @MohamedMontaser91 6 місяців тому +1

    where is the videos about configuring superset for production?

    • @ShantanuKhond
      @ShantanuKhond  6 місяців тому

      Production is already there. Are you asking about celery redis? If yes then documentation is published. Tomorrow i will record and publish. It will take a more time and i am configuring bigger vm on azure.

  • @siddharthmishra6502
    @siddharthmishra6502 5 місяців тому +1

    Hi @shantanu this video is really good . But i've one doubt if
    sales level 1 sales level 2 sales level 3
    sl1 slm1 slmn1
    sl1 slm1 slmn2
    sl1 slm2 slmn3
    sl1 slm2 slmn4
    sl2 slm3 slmn5
    sl2 slm3 slmn6
    sl2 slm3 slmn7
    sl2 slm3 slmn8
    sl2 slm3 slmn9
    sl2 slm3 slmn10
    sl2 slm4 slmn11
    sl2 slm4 slmn12
    i've a hierarchy somewhat similar to this and i want to apply rls based on the same in superset in a way that data related to the hierarchy will only be visible . how can we do this on superset it's pretty straight forward in power bi and other visual tools but not able to get this done here . Hope you can help me out on this

    • @ShantanuKhond
      @ShantanuKhond  5 місяців тому

      For this kind of RLS I would suggest you to create user mapping table. Say user1 or in your case slm1 should have access to these level. Now you can get user id from superset and put it in query and inner join this access table with your data table. It will filter it automatically. BTW is it ok if I use your example to create a scenario for RLS?
      Thank you!

    • @siddharthmishra6502
      @siddharthmishra6502 4 місяці тому

      @@ShantanuKhondsure man it would be really helpful for me as well as others