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

   ### Bug description
   
   # Bug: “Security” menu disappears in Superset 4 on MySQL
   
   |  | **Value** |
   | --- | --- |
   | **Superset version** | 4.0.x (verified on 4.0.0 & 4.1.0-SNAPSHOT) |
   | **Metadata DB** | MySQL
   | **Regression?** | Yes – Superset 3 shows the menu correctly |
   | **Impact** | *Admin* users lose access to **Security → Users / Roles / RLS 
/ Action Log*** |
   
   ---
   
   ## Steps to Reproduce
   
   1. **Build a local Superset 4 Docker image**  
   
   2. **Start a brand-new MySQL container**  
   
   3. **Run Superset 4 pointing at that MySQL instance**  
   
   4. **Log into the Superset UI as the admin user**  
      *open the Settings navigation menu and look for the **Security** 
category.*
   
   **Expected result:** *Security* section is visible for Admin.  
   **Actual result:** *Security* section is missing.
   
   (Repeat the same steps with PostgreSQL as the metadata DB and notice the 
menu appears, confirming the regression.)
   
   ---
   
   ## Findings (database state)
   
   | Database | Entries in `ab_view_menu` that match `%ecurity%` **after first 
init** |
   | --- | --- |
   | **MySQL** | Only one row: `"security"` (all lowercase) |
   | **PostgreSQL** | Two separate rows: `"Security"` **and** `"security"` |
   
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   I don't know
   
   ### Node version
   
   I don't know
   
   ### 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