GitHub user dosubot[bot] added a comment to the discussion: Login redirection does not use subpath prefix
<!-- Answer --> You're right that the backend is in the same repo — PR #39465 is actually a frontend-only change (it modifies `RoleListEditModal.tsx`, `fetchOptions.ts`, and a test file) [[1]](https://github.com/apache/superset/pull/39465). It doesn't change any backend code; it just switches which existing endpoint the frontend calls. Now, here's the important detail: after PR #39465, the **initial permissions load** for an existing role uses `/api/v1/security/roles/{id}/permissions/` (which is working for you — you can see permission names). However, the **permissions dropdown** (for adding/searching all available permissions) still relies on a separate call to `/api/v1/security/permissions-resources/` to pre-load all available permissions [[2]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/pages/RolesList/index.tsx#L112-L126). The search/filter when you type in the field is supposed to be **client-side filtering** on that pre-loaded list — no new API call should be triggered on keystroke. But if the initial fetch of all available permissions from `/api/v1/security/permissions-resources/` is failing (perhaps partially), then searching would trigger the error. **To debug this:** 1. Open DevTools → Network tab 2. Open the role edit modal (watch what calls are made on load) 3. Then type in the permissions search field 4. Check if a new API request fires, or if the error is deferred from the initial load The error you're seeing ("There was an error while fetching permissions") might actually be from the **initial load** of all available permissions via `/api/v1/security/permissions-resources/`, which only surfaces visually when you interact with the field. This endpoint has a known issue in some FAB versions where it doesn't declare the proper `search_columns`, causing 400 errors when filters are applied [[3]](https://github.com/apache/superset/issues/39967). Could you check what requests are shown in the Network tab when you open the modal and when you type? That'll pinpoint whether it's the initial load or a search-triggered call that's failing. <!-- 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=423ace75-e933-47b1-aa22-6e0ca100356d) [](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/40082#discussioncomment-17240719 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
