DataStrategistTeam opened a new issue, #35626:
URL: https://github.com/apache/superset/issues/35626

   ### Bug description
   
   
   I noticed a difference between the `5.0.0` tag and the current `master` 
branch regarding reCAPTCHA support.  
   
   In `master`, there is logic like:  
   
   ```python
   if auth_user_registration:
       frontend_config["AUTH_USER_REGISTRATION_ROLE"] = 
app.config["AUTH_USER_REGISTRATION_ROLE"]
   if should_show_recaptcha:
       frontend_config["RECAPTCHA_PUBLIC_KEY"] = 
app.config["RECAPTCHA_PUBLIC_KEY"]
   ```
   
   But in the `5.0.0` tag, the `RECAPTCHA_PUBLIC_KEY` (and related config) does 
not exist.  
   
   - Is this intentional (i.e., reCAPTCHA support only added after 5.0.0)?  
   - Or should this configuration be available in 5.0.0 as well?  
   
   I ran into errors like:  
   ```
   RuntimeError: RECAPTCHA_PUBLIC_KEY config not set
   ```
   when enabling `AUTH_USER_REGISTRATION` on 5.0.0.  
   
   Could you clarify whether reCAPTCHA is expected to work in 5.0.0, or if it’s 
only supported in newer versions?  
   
   
   <img width="570" height="353" alt="Image" 
src="https://github.com/user-attachments/assets/4e48a371-9cb1-4a0f-92ef-0e1ff64441e1";
 />
   
   <img width="683" height="226" alt="Image" 
src="https://github.com/user-attachments/assets/eb357ece-cda3-44ca-9bf4-6f5785b5b7b9";
 />
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] 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