You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "Appendino (via GitHub)" <gi...@apache.org> on 2023/03/07 16:47:55 UTC
[GitHub] [superset] Appendino opened a new issue, #23301: Get /api/v1/chart is only using Public Role with OAUTH
Appendino opened a new issue, #23301:
URL: https://github.com/apache/superset/issues/23301
We are using a Superset v2.0.1 with OAUTH Azure enabled, and when we try to get charts throw Superset API with a database user, like admin for example, is ignoring the user roles and it is using only the Public role, this happens even when the user does not has the Public Role.
But when test in a environment without OAUTH the charts api work fines with user roles.
#### How to reproduce the bug
1. Enable Azure OAUTH
2. Get tokens with "/api/v1/security/login", using a db user. "provider": "db"
3. Get charts using the "/api/v1/chart/"
4. If the Public role does not has the permission the results in json will be empty.
5. If the Public role has the necessary permissions the json will be filled.
### Expected results
Charts json with the result filed with the charts.
### Actual results
If Public role does not has the necessary permission the results filed is empty.
Thanks a lot!!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Get /api/v1/chart is only using Public Role with OAUTH [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #23301:
URL: https://github.com/apache/superset/issues/23301#issuecomment-1957587222
This version of Superset is no longer supported. If anyone is still encountering this in current versions (3.x) please open a new Issue or a PR to address the problem.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Get /api/v1/chart is only using Public Role with OAUTH [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #23301: Get /api/v1/chart is only using Public Role with OAUTH
URL: https://github.com/apache/superset/issues/23301
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
[GitHub] [superset] vedangparasnis commented on issue #23301: Get /api/v1/chart is only using Public Role with OAUTH
Posted by "vedangparasnis (via GitHub)" <gi...@apache.org>.
vedangparasnis commented on issue #23301:
URL: https://github.com/apache/superset/issues/23301#issuecomment-1458781728
I think we faced the same issue, @nytai , correct me if I am wrong, the superset api's having fab security decorators when called externally works only when security is LDAP or DB.
In case of Oauth, the default role mapping is public even though the api's are conceived with a provider as 'db' to use AUTH_DB security.
I think in order to achieve this you need 2 superset servers pointing to same meta database, one solely using oauth and other user complely ldap or AUTH_DB Security.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org