-
Notifications
You must be signed in to change notification settings - Fork 13.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to save database when impersonation is enabled #14377
Comments
Just following up to see if anyone else has ran into this and knows of a fix or workaround. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
@octonary |
There should be a way to force a connection to save. |
Closing this since it was reported on Superset 1.x, and we now only support Superset 3.1/4.0. If you're still facing this issue as described, let us know and we can re-open, but this sounds more like a feature request than a bug if I'm interpreting correctly :) |
I am getting the following error when I try to enable impersonation for a Presto database...
An error occurred while fetching databases: "Connection failed, please check your connection settings"
Impersonation was previously working before authentication was added to the Presto UI. I found a few other issues related to impersonation but they all appear to be closed or merged so I upgraded to the latest apache-superset version in hopes that these issues were all resolved. I am able to successfully add a database connection if the service account is using the same credentials as the currently logged in user so I thought this may be a similar issue to #7170. However, that issue yielded a 401 response whereas this issue clearly returns a 200 from Presto but then fails when trying to save the details to the superset metadata db.
I am able to successfully add a database connection when impersonation is not enabled. I am also able to successfully test the connection with impersonation enabled but when I try and save I get the error. The logs just show a 422 response...
How to reproduce the bug:
Environment:
The text was updated successfully, but these errors were encountered: