-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Cannot configure ldap in Superset 4.1.0 rc2 #30553
Comments
A similar issue was discussed in a closed thread regarding the installation of the
This should help resolve the issue with LDAP configuration in Superset 4.1.0 rc2. |
Is there a reason superset isn't standardizing on python 3.11? It would save a great deal of frustration, given that most of the distro-supplied python packages are built for 3.11. |
I'm going to have to give up on rc2. I keep running into one problem after another. I bit the bullet and built the ldap module. Now when Superset starts up, it seems to not know if it should be using postgres or SQLite. superset db upgrade generates numerous foreign key errors, the postgres database is only partially populated, and I get a 500 error when I try to access the UI. I can understand wanting to slim down the build, but there has to be a better way than just stripping out all the drivers and forcing the burden onto users. This is a mess. |
Thanks for testing it out. How are you deploying - with the PyPI package? I ran into some similar problems when I tried out 4.1.0rc2, see my comment here: #29999 (comment) I'm deploying from Docker and for the purposes of testing I just switched to 4.1.0rc2-dev which fixed things. But maybe we can/should do better to support folks who want a production-ready image without building their own. In addition to |
I was creating a docker container, using the superset provided docker container as the base and adding the required drivers. And yes, it seems like all of that is missing. I think sqlite may be included by default because I didn't install that myself, but everything else is missing. Seems like too much has been stripped out. I think a better option would be to provide a curated superset build container, where a user just have to provide a list of the desired drivers, and the build container will take care of making sure everything is installed. |
Bug description
Apparently as part of the database driver purge, ldap drivers have also been removed and have to be reinstalled by the user.
There are currently 2 options, neither of which are ideal:
It would be much better if Superset restored the necessary ldap libraries by default.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.10
Node version
Not applicable
Browser
Not applicable
Additional context
The following appears in the logs:
Checklist
The text was updated successfully, but these errors were encountered: