GitHub user dosubot[bot] added a comment to the discussion: Custom User Info Fields and FAB User View Overrides No Longer Work in Superset v6 (React Migration)
<!-- Answer --> Here’s a detailed breakdown based on your questions and the current state of Superset v6: 1. **Why did custom user field overrides work in v5 but not v6?** In v5, the User Info/Profile page was rendered by Flask AppBuilder (FAB) views like `UserOAuthModelView`, so you could customize fields and layout in Python. In v6, the User Info page was rewritten as a React component that fetches user data from `/api/v1/me/` and displays only a fixed set of fields (username, active, roles, login count, first/last name, email). The frontend no longer uses FAB views or their Python configuration, so any custom fields or overrides are ignored. This is a deliberate architectural shift to decouple the UI from backend Python code and make the UI more modern and consistent, but it removed the previous extension points for user info customization [(source)](https://github.com/apache/superset/issues/32116#issuecomment-2657483490). 2. **Is the User Info/Profile page still rendered by FAB in v6?** No. FAB is now responsible only for authentication, authorization, and security logic. The User Info/Profile page UI is fully handled by the React frontend. Any extra fields you added to the user model or FAB views are not surfaced in the UI, and FAB view overrides (like `show_fieldsets`) have no effect on the React page [(source)](https://github.com/apache/superset/issues/32116#issuecomment-2657483490). 3. **Is there any supported way to add custom user fields to the User Info page in v6?** No. There is currently no supported way—via `superset_config.py`, security manager overrides, or any other documented extension point—to add custom user fields to the User Info page in v6. The React component is hardcoded to display only the default fields, and the backend API does not return custom attributes. Any Python-side customizations are ignored by the frontend [(source)](https://github.com/apache/superset/issues/32116#issuecomment-2657483490). 4. **Recommended approach for teams that relied on custom FAB user views?** There is no official migration path or alternative for teams that relied on custom FAB user views and fields. The only options are to maintain a fork with your own backend and frontend changes, or to monitor ongoing SIPs (Superset Improvement Proposals) and plugin architecture discussions for future extensibility. As of now, `superset_config.py` cannot restore this functionality [(source)](https://github.com/apache/superset/issues/32116#issuecomment-2657483490). 5. **How to handle custom pages and landing pages after OAuth login in v6?** Superset v6 does not provide a simple config option in `superset_config.py` to redirect users to a custom page or dashboard after OAuth login. The only supported way is to define a custom `IndexView` class and use a `mutate_app` function assigned to `FLASK_APP_MUTATOR` in your config to set `appbuilder.indexview` to your custom class. For more advanced login/redirect logic (e.g., based on user attributes or OAuth provider), you need to implement a custom security manager and/or override authentication views [(source)](https://github.com/apache/superset/issues/34575). **Roadmap:** There are ongoing SIPs and roadmap discussions about making Superset more extensible and pluggable (e.g., plugin architecture, security model redesign), but there is no concrete plan or timeline for making the User Info page extensible for custom fields [(source)](https://github.com/apache/superset/issues/32116#issuecomment-2657483490). **Summary:** - Custom user fields and FAB view overrides are not supported in the v6 React User Info page. - FAB now only handles backend auth/security, not user/profile UI. - No config or extension point exists for custom user fields in the UI. - Custom post-login redirects require backend code, not just config. - Extensibility for user info is a known gap, but not yet on the roadmap. Let me know if you want code examples for custom login/redirect logic or more details on the ongoing SIPs. <!-- 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/f47a0a4d-6a6a-453a-a41d-622966bfd808?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f47a0a4d-6a6a-453a-a41d-622966bfd808?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f47a0a4d-6a6a-453a-a41d-622966bfd808?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f47a0a4d-6a6a-453a-a41d-622966bfd808?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f47a0a4d-6a6a-453a-a41d-622966bfd808?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f47a0a4d-6a6a-453a-a41d-622966bfd808?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f47a0a4d-6a6a-453a-a41d-622966bfd808?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Here%E2%80%99s%20a%20detailed%20breakdown%20based%20on%20your%20questions%20and%20the%20current%20state%20of%20Superset%20v6%3A%0A%0A1.%20%2A%2AWhy%20did%20custom%20user%20field%20overrides%20work%20in%20v5%20but%20not%20v6%3F%2A%2A%20%20%0A%20%20%20In%20v5%2C%20the%20User%20Info/Profile%20page%20was%20rendered%20by%20Flask%20AppBuilder%20%28FAB%29%20views%20like%20%60UserOAuthModelView%60%2C%20so%20you%20could%20customize%20fields%20and%20layout%20in%20Python.%20In%20v6%2C%20the%20User%20Info%20page%20was%20rewritten%20as%20a%20React%20component%20that%20fetches%20user%20data%20from%20%60/api/v1/me/%60%20and%20displays%20only%20a%20fixed%20set%20of%20fields%20%28username%2C%20active%2C%20roles%2C%20login%20count%2C%20first/last%20name%2C%20email%29.% 20The%20frontend%20no%20longer%20uses%20FAB%20views%20or%20their%20Python%20configuration%2C%20so%20any%20custom%20fields%20or%20overrides%20are%20ignored.%20This%20is%20a%20deliberate%20architectural%20shift%20to%20decouple%20the%20UI%20from%20backend%20Python%20code%20and%20make%20the%20UI%20more%20modern%20and%20consistent%2C%20but%20it%20removed%20the%20previous%20extension%20points%20for%20user%20info%20customization%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/32116%23issuecomment-2657483490%29.%0A%0A2.%20%2A%2AIs%20the%20User%20Info/Profile%20page%20still%20rendered%20by%20FAB%20in%20v6%3F%2A%2A%20%20%0A%20%20%20No.%20FAB%20is%20now%20responsible%20only%20for%20authentication%2C%20authorization%2C%20and%20security%20logic.%20The%20User%20Info/Profile%20page%20UI%20is%20fully%20handled%20by%20the%20React%20frontend.%20Any%20extra%20fields%20you%20added%20to%20the%20user%20model%20or%20FAB%20views%20are%20not%20surfaced%20in%20the%20UI%2C%20and%20FAB%20vie w%20overrides%20%28like%20%60show_fieldsets%60%29%20have%20no%20effect%20on%20the%20React%20page%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/32116%23issuecomment-2657483490%29.%0A%0A3.%20%2A%2AIs%20there%20any%20supported%20way%20to%20add%20custom%20user%20fields%20to%20the%20User%20Info%20page%20in%20v6%3F%2A%2A%20%20%0A%20%20%20No.%20There%20is%20currently%20no%20supported%20way%E2%80%94via%20%60superset_config.py%60%2C%20security%20manager%20overrides%2C%20or%20any%20other%20documented%20extension%20point%E2%80%94to%20add%20custom%20user%20fields%20to%20the%20User%20Info%20page%20in%20v6.%20The%20React%20component%20is%20hardcoded%20to%20display%20only%20the%20default%20fields%2C%20and%20the%20backend%20API%20does%20not%20return%20custom%20attributes.%20Any%20Python-side%20customizations%20are%20ignored%20by%20the%20frontend%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/32116%23issuecomment-2657483490%29.%0A%0A4.%20%2A%2ARecommended%20a pproach%20for%20teams%20that%20relied%20on%20custom%20FAB%20user%20views%3F%2A%2A%20%20%0A%20%20%20There%20is%20no%20official%20migration%20path%20or%20alternative%20for%20teams%20that%20relied%20on%20custom%20FAB%20user%20views%20and%20fields.%20The%20only%20options%20are%20to%20maintain%20a%20fork%20with%20your%20own%20backend%20and%20frontend%20changes%2C%20or%20to%20monitor%20ongoing%20SIPs%20%28Superset%20Improvement%20Proposals%29%20and%20plugin%20architecture%20discussions%20for%20future%20extensibility.%20As%20of%20now%2C%20%60superset_config.py%60%20cannot%20restore%20this%20functionality%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/32116%23issuecomment-2657483490%29.%0A%0A5.%20%2A%2AHow%20to%20handle%20custom%20pages%20and%20landing%20pages%20after%20OAuth%20login%20in%20v6%3F%2A%2A%20%20%0A%20%20%20Superset%20v6%20does%20not%20provide%20a%20simple%20config%20option%20in%20%60superset_config.py%60%20to%20redirect%20users%20to%20a%20custom%20page%20or% 20dashboard%20after%20OAuth%20login.%20The%20only%20supported%20way%20is%20to%20define%20a%20custom%20%60IndexView%60%20class%20and%20use%20a%20%60mutate_app%60%20function%20assigned%20to%20%60FLASK_APP_MUTATOR%60%20in%20your%20config%20to%20set%20%60appbuilder.indexview%60%20to%20your%20custom%20class.%20For%20more%20advanced%20login/redirect%20logic%20%28e.g.%2C%20based%20on%20user%20attributes%20or%20OAuth%20provider%29%2C%20you%20need%20to%20implement%20a%20custom%20security%20manager%20and/or%20override%20authentication%20views%20%5B%28source%29%5D%28https%3A//github.com/apache/superset/issues/34575%29.%0A%0A%2A%2ARoadmap%3A%2A%2A%20%20%0AThere%20are%20ongoing%20SIPs%20and%20roadmap%20discussions%20about%20making%20Superset%20more%20extensible%20and%20pluggable%20%28e.g.%2C%20plugin%20architecture%2C%20security%20model%20redesign%29%2C%20but%20there%20is%20no%20concrete%20plan%20or%20timeline%20for%20making%20the%20User%20Info%20page%20extensible%20for%20custom%20fields%20%5B%2 8source%29%5D%28https%3A//github.com/apache/superset/issues/32116%23issuecomment-2657483490%29.%0A%0A%2A%2ASummary%3A%2A%2A%20%20%0A-%20Custom%20user%20fields%20and%20FAB%20view%20overrides%20are%20not%20supported%20in%20the%20v6%20React%20User%20Info%20page.%0A-%20FAB%20now%20only%20handles%20backend%20auth/security%2C%20not%20user/profile%20UI.%0A-%20No%20config%20or%20extension%20point%20exists%20for%20custom%20user%20fields%20in%20the%20UI.%0A-%20Custom%20post-login%20redirects%20require%20backend%20code%2C%20not%20just%20config.%0A-%20Extensibility%20for%20user%20info%20is%20a%20known%20gap%2C%20but%20not%20yet%20on%20the%20roadmap.%0A%0ALet%20me%20know%20if%20you%20want%20code%20examples%20for%20custom%20login/redirect%20logic%20or%20more%20details%20on%20the%20ongoing%20SIPs.) [](https://go.dosu.dev/discord-bot) [](htt ps://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/36925) GitHub link: https://github.com/apache/superset/discussions/36925#discussioncomment-15430439 ---- 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]
