You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/05/02 03:16:15 UTC
Re: [D] 403 Forbidden when accessing /api/v1/extensions/_info (Superset 6.1.0rc1 + extension 0.1.0rc1, Docker) [superset]
GitHub user dosubot[bot] edited a comment on the discussion: 403 Forbidden when accessing /api/v1/extensions/_info (Superset 6.1.0rc1 + extension 0.1.0rc1, Docker)
<!-- Answer -->
This looks like a permission synchronization issue that's common after upgrades. The `ExtensionsRestApi` endpoint you're hitting requires permissions that haven't been registered in your FAB security database.
**Try these steps in order:**
1. **Run database migrations and resync permissions:**
```bash
docker compose exec superset superset db upgrade
docker compose exec superset superset init
```
2. **Restart Superset** after the init completes.
3. **Verify permissions were created:**
```bash
docker compose exec superset superset fab list-permissions | grep -i extension
```
**Why this happens:** Superset uses Flask-AppBuilder's [permission auto-generation system](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/cli/main.py#L62-L68) which runs during `superset init`. If the init service failed or ran before the extension packages were installed, the extension API permissions won't exist.
**If that doesn't work:** The [March 2026 extension API changes](https://github.com/apache/superset/pull/38412) introduced a new unified `@api` decorator with automatic route prefixing to `/extensions/{publisher}/{name}`. If you're using 6.1.0rc1, the extension packages may need to follow this new registration pattern. Check if the extension packages are compatible with 6.1.0rc1.
For Docker specifically, ensure the `superset-init` service [completed successfully](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/docker-init.sh#L46-L79) - other services wait for this via `condition: service_completed_successfully`. Check the init container logs for any errors:
```bash
docker compose logs superset-init
```
This is a [known pattern of issues](https://github.com/apache/superset/issues/36485) after upgrades where permissions aren't properly synced.
<!-- 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).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-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=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=89d5e586-1fac-45c6-ba94-11e6453eea49) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-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=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/38736#discussioncomment-16203687
----
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