schoel-bis opened a new issue, #37008:
URL: https://github.com/apache/superset/issues/37008

   ### Bug description
   
   Since v6, when running Superset with `AUTH_LDAP` authentication type, it 
will fail in the `cached_common_bootstrap_data` of `BaseSupersetView` with:
   
   ```
   File "…/superset/views/base.py", line 417, in cached_common_bootstrap_data
       frontend_config["RECAPTCHA_PUBLIC_KEY"] = 
app.config["RECAPTCHA_PUBLIC_KEY"]
   KeyError: 'RECAPTCHA_PUBLIC_KEY'
   ```
   
   This is because `AUTH_LDAP` requires `AUTH_USER_REGISTRATION` to be set in 
order to pick up users from the directory server (see 
[auth_user_ldap](https://github.com/dpgaspar/Flask-AppBuilder/blob/f4a8cfd9f31f7eb36fb7891ccf9747b7506a41d3/flask_appbuilder/security/manager.py#L1157)
 in FAB's `SecurityManager`), but `cached_common_bootstrap_data` now requires 
the ReCaptcha key to be available when this is set, except for OAuth. ReCaptcha 
wouldn't be used with LDAP, though.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   6.0.0
   
   ### Python version
   
   3.11
   
   ### Node version
   
   Not applicable
   
   ### Browser
   
   Not applicable
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to