search

abhioncbr / docker-superset

Repository for Docker Image of Apache-Superset. [Docker Image: https://hub.docker.com/r/abhioncbr/docker-superset]
https://abhioncbr.github.io/docker-superset
Other
103 stars 55 forks source link

This endpoint requires the datasource **, database or `all_datasource_access` permission #33

Closed brachipa closed 5 years ago

brachipa commented 5 years ago

When trying to create a chart on data source I get error : This endpoint requires the datasource , database or all_datasource_access permission

With this stacktrace

Traceback (most recent call last):
  File "/home/superset/superset/views/base.py", line 114, in wraps
    return f(self, *args, **kwargs)
  File "/home/superset/superset/views/core.py", line 1256, in explore_json
    samples=samples,
  File "/home/superset/superset/views/core.py", line 1169, in generate_json
    security_manager.assert_datasource_permission(viz_obj.datasource)
  File "/home/superset/superset/security.py", line 470, in assert_datasource_permission
    self.get_datasource_access_link(datasource),
superset.exceptions.SupersetSecurityException: This endpoint requires the datasource poc-test, database or
            `all_datasource_access` permission

Happens in the latest docker image and also in the version before: 0.29.0rc7

issue-label-bot[bot] commented 5 years ago

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.90. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

abhioncbr commented 5 years ago

Can you please share the steps to reproduce the issue?

Also, from the last line of the stack trace, it looks like this happens when you trying to generate a chart using database 'poc-test'. If that is the case, can you please try with default dummy database and see if you are getting an error or not. Thanks.

brachipa commented 5 years ago

@abhioncbr same happens for the default DB, I tried birth_names. Steps: Just run SUPERSET_ENV=prod docker-compose up --build -d And then click new chart, and choose the data source (default).

When doing the same by taking the superset repo, and build the docker image, from the latest tag. Everything works well.

abhioncbr commented 5 years ago

@brachipa I just tried by running a container using Kitematic, and it is working. Let me try with the steps provided by you. In the meanwhile, you can try it a Kitematic way, if you want. Thanks.

brachipa commented 5 years ago

Can you send me some instructions? On how to do it?

On 17 Jul 2019, at 23:14, Abhishek Sharma notifications@github.com wrote:

I just tried by running a container using Kitematic, and it is working. Let me try with the steps provided by you. In the meanwhile, you can try it a Kitematic way, if you want. Thanks.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/abhioncbr/docker-superset/issues/33?email_source=notifications&email_token=ALA5TYS3AWY2XKQHEQQ6GOLP754THA5CNFSM4IENZNSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2GORDQ#issuecomment-512551054, or mute the thread https://github.com/notifications/unsubscribe-auth/ALA5TYQPPTS2RWTADPMCIVDP754THANCNFSM4IENZNSA.

abhioncbr commented 5 years ago

@brachipa try to follow README.md, https://github.com/abhioncbr/docker-superset#how-to-run-using-kitmatic

brachipa commented 5 years ago

@abhioncbr works when building this: cd docker-superset/docker-files/ && docker-compose up -d This takes superset version 0.29.0rc5. But when switching to latest I fail.

abhioncbr commented 5 years ago

@brachipa okay, reproduced the issue. It is not a bug; In my opinion, it is a feature in release. Admin role in the latest version doesn't have the permission to access the data and hence charting can not be done on top of it. For accessing the database give permission to the Admin role.

Please add the following permissions in Admin role and than chart will work,

database access on [main].(id:1), database access on [main-other].(id:2), datasource access on [main].energy_usage, datasource access on [main].wb_health_population, datasource access on [main].birth_names, schema access on [main-other].[information_schema], schema access on [main-other].[superset]]

I think this will resolve the issue.

PS: give a star to the repo if you like it.

brachipa commented 5 years ago

I'll try this.

Where should I set this permissions? Is it on the UI? Any file?

I just want to mention that when I'm building this version image from SuperSet repo itself,(Not pulling the image just build it) this works. So, seems to me like a regression in this specific docker image.

(BTW, building the image by using this repository Docker file, produces many errors, worth open on it a different issue...)

On Thu, Jul 18, 2019, 5:20 PM Abhishek Sharma notifications@github.com wrote:

@brachipa https://github.com/brachipa okay, reproduced the issue. It is not a bug; In my opinion, it is a feature in release. Admin role in the latest version doesn't have the permission to access the data and hence charting can not be done on top of it. For accessing the database give permission to the Admin role.

Please add the following permissions in Admin role and than chart will work,

database access on [main].(id:1), database access on [main-other].(id:2), datasource access on [main].energy_usage, datasource access on [main].wb_health_population, datasource access on [main].birth_names, schema access on [main-other].[information_schema], schema access on [main-other].[superset]]

I think this will resolve the issue.

PS: give a start to the repo if you like it.`

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/abhioncbr/docker-superset/issues/33?email_source=notifications&email_token=ALA5TYVI6O2UZFHVGUO4NSDQAB32ZA5CNFSM4IENZNSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2IUHCQ#issuecomment-512836490, or mute the thread https://github.com/notifications/unsubscribe-auth/ALA5TYUBY6X46SEUMV54HNTQAB32ZANCNFSM4IENZNSA .

abhioncbr commented 5 years ago

security -> List Roles -> edit Admin role -> from drop down add all above mentioned.

Possibly, they added another step for permissions to Admin role, which Superset repo have and mine not.

brachipa commented 5 years ago

Now, can't open the charts page:

sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError) (1054, "Unknown column 'tables.user_id' in 'field list'") [SQL: 'SELECT tables.created_on AS tables_created_on, tables.changed_on AS tables_changed_on, tables.id AS tables_id, tables.description AS tables_description, tables.default_endpoint AS tables_default_endpoint, tables.is_featured AS tables_is_featured, tables.filter_select_enabled AS tables_filter_select_enabled, tables.offset AS tables_offset, tables.cache_timeout AS tables_cache_timeout, tables.params AS tables_params, tables.perm AS tables_perm, tables.table_name AS tables_table_name, tables.main_dttm_col AS tables_main_dttm_col, tables.database_id AS tables_database_id, tables.fetch_values_predicate AS tables_fetch_values_predicate, tables.user_id AS tables_user_id, tables.schema AS tables_schema, tables.sql AS tables_sql, tables.is_sqllab_view AS tables_is_sqllab_view, tables.template_params AS tables_template_params, tables.created_by_fk AS tables_created_by_fk, tables.changed_by_fk AS tables_changed_by_fk \nFROM tables \nWHERE tables.id = %s \n LIMIT %s'] [parameters: (3, 1)] (Background on this error at: http://sqlalche.me/e/e3q8)

shauryagoel commented 1 year ago

Is anybody facing the problem in superset 2.1.0? I have added data from Postgres and created a dashboard with a refreshing interval, but, it is not refreshing.