You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "GeoFeng-TTI (via GitHub)" <gi...@apache.org> on 2026/01/16 02:27:22 UTC
[D] The Security menu is missing from the interface after configuring the MySQL metadata database in Apache Superset version 6.0.0 [superset]
GitHub user GeoFeng-TTI created a discussion: The Security menu is missing from the interface after configuring the MySQL metadata database in Apache Superset version 6.0.0
When I deploy Apache Superset on my windows computer, The Security menu is missing from the interface after configuring the MySQL metadata database in Apache Superset version 6.0.0. Why?? But it exists for the Sqlite metadata database.
GitHub link: https://github.com/apache/superset/discussions/37189
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] The Security menu is missing from the interface after configuring the MySQL metadata database in Apache Superset version 6.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: The Security menu is missing from the interface after configuring the MySQL metadata database in Apache Superset version 6.0.0
<!-- Greeting -->
Hi @GeoFeng-TTI! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
This is a known issue in Superset 6.0.0 when using MySQL as the metadata database: the Security menu may be missing because the menu name is stored as lowercase 'security' instead of capitalized 'Security' in the ab_view_menu table. To fix this, run the following SQL query on your MySQL metadata database:
```sql
UPDATE ab_view_menu SET name='Security' WHERE name='security';
```
This should restore the Security menu in the interface. The issue is specific to MySQL and does not affect SQLite, which is why you see the menu when using SQLite but not MySQL. For more details, see [this discussion](https://github.com/apache/superset/issues/37013) and [this related issue](https://github.com/apache/superset/issues/33672).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/3751dbf5-668b-4a1c-8623-90fd7187e1e2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/3751dbf5-668b-4a1c-8623-90fd7187e1e2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/3751dbf5-668b-4a1c-8623-90fd7187e1e2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/3751dbf5-668b-4a1c-8623-90fd7187e1e2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3751dbf5-668b-4a1c-8623-90fd7187e1e2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/3751dbf5-668b-4a1c-8623-90fd7187e1e2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3751dbf5-668b-4a1c-8623-90fd7187e1e2?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20in%20Superset%206.0.0%20when%20using%20MySQL%20as%20the%20metadata%20database%3A%20the%20Security%20menu%20may%20be%20missing%20because%20the%20menu%20name%20is%20stored%20as%20lowercase%20%27security%27%20instead%20of%20capitalized%20%27Security%27%20in%20the%20ab_view_menu%20table.%20To%20fix%20this%2C%20run%20the%20following%20SQL%20query%20on%20your%20MySQL%20metadata%20database%3A%0A%0A%60%60%60sql%0AUPDATE%20ab_view_menu%20SET%20name%3D%27Security%27%20WHERE%20name%3D%27security%27%3B%0A%60%60%60%0A%0AThis%20should%20restore%20the%20Security%20menu%20in%20the%20interface.%20The%20issue%20is%20specific%20to%20MySQL%20and%20does%20not%20affect%20SQLite%2C%20which%20is%20why%20you%20see%20the%20menu%20when%20using%20
SQLite%20but%20not%20MySQL.%20For%20more%20details%2C%20see%20%5Bthis%20discussion%5D%28https%3A//github.com/apache/superset/issues/37013%29%20and%20%5Bthis%20related%20issue%5D%28https%3A//github.com/apache/superset/issues/33672%29.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/37189)
GitHub link: https://github.com/apache/superset/discussions/37189#discussioncomment-15512961
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] The Security menu is missing from the interface after configuring the MySQL metadata database in Apache Superset version 6.0.0 [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: The Security menu is missing from the interface after configuring the MySQL metadata database in Apache Superset version 6.0.0
<!-- Greeting -->
Hi @GeoFeng-TTI! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
This is a known issue in Superset 6.0.0 when using MySQL as the metadata database: the Security menu may be missing because the menu name is stored as lowercase 'security' instead of capitalized 'Security' in the ab_view_menu table. To fix this, run the following SQL query on your MySQL metadata database:
```sql
UPDATE ab_view_menu SET name='Security' WHERE name='security';
```
This should restore the Security menu in the interface. The issue is specific to MySQL and does not affect SQLite, which is why you see the menu when using SQLite but not MySQL. For more details, see [this discussion](https://github.com/apache/superset/issues/37013) and [this related issue](https://github.com/apache/superset/issues/33672).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=3751dbf5-668b-4a1c-8623-90fd7187e1e2) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/37189#discussioncomment-15512961
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org