[GitHub] [superset] chcharlet commented on issue #17074: Database Impersonification with PostgreSQL not working anymore

[GitBox <gi...@apache.org>]

chcharlet commented on issue #17074:
URL: https://github.com/apache/superset/issues/17074#issuecomment-1064850040


   Hi,
   
   I think this feature working would be a huge benefit in almost every enterprise context. We are just starting into our project, and we are missing it already!
   
   I have been looking at this , and I don't think logging the authorized superset user into postgres using their password is a realistic option (it just makes all kinds of headaches worse). But it would be perfectly possible to have superset use "[SET SESSION AUTHORIZATION](https://www.postgresql.org/docs/current/sql-set-session-authorization.html)" when connecting to postgres.
   
   The bad news is that that has to happen at a different point in time (and hence code).
   
   Would people be interested in a pull request on this?


-- 
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