Redirect upon logging in based on user role in 6.0.0

[carlosaran667]

Hi,

I recently upgraded from 4.1.1 to 6.0.0 and found that my previous customization no longer works.

In 4.1.1, I had modified SupersetIndexView(IndexView) in initialization/init.py so that, after logging in, users were redirected to a different URL depending on their role. In other words, instead of always sending users to /superset/welcome/, I was routing each type of user to a specific dashboard or page after authentication.

After upgrading to 6.0.0, that customization no longer seems to apply.

What is the recommended way to achieve this in v6? I could not find any documentation or examples about role-based post-login redirects.

[dosubot[bot]]

Your previous approach no longer works because Superset v6 migrated to a React frontend that decoupled UI routing from Flask/FAB backend logic. The FAB_INDEX_VIEW configuration and custom IndexView classes are now ignored by the React frontend.

Recommended Solution: Use a custom security manager to implement role-based redirects:

# In your superset_config.py
from flask_appbuilder.security.views import AuthView
from flask import redirect, g
from superset.security import SupersetSecurityManager

class CustomAuthView(AuthView):
    @expose("/")
    def index(self):
        if g.user and g.user.is_authenticated:
            # Custom role-based redirect logic
            if 'Admin' in [role.name for role in g.user.roles]:
                return redirect('/superset/dashboard/list/')
            elif 'Alpha' in [role.name for role in g.user.roles]:
                return redirect('/chart/list/')
            else:
                return redirect('/superset/welcome/')
        return super().index()

class CustomSecurityManager(SupersetSecurityManager):
    authview = CustomAuthView

CUSTOM_SECURITY_MANAGER = CustomSecurityManager

This approach is confirmed to work in v6. You can adapt the role checks and redirect URLs to match your requirements.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[sfirke]

This seems like a good answer? Without me checking it. I ran into a related issue albeit in the base Superset code, between 4.x and 5.x the change from FAB to custom code for logging in broke a feature I need (anonymous users get a redirect to the target dashboard preserved during login). I wrote this PR that was merged to fix it: #35345

Sharing in case any of that helps!

[carlosaran667]

Hi @sfirke
The code suggested by dosu does not work. Also, the claim that it is “confirmed to work in v6” is misleading: the post it links to is still unanswered, so it does not actually confirm that point. In any case, that post is about a different problem from the one I am describing here.

I had already seen your PR, but it addresses a different use case as well. What I need is a redirect after users log in with their Superset account, to dashboards that are not public.
Thanks anyway for sharing it!

I will edit the main post to explain my goals better.

[carlosaran667]

@dosu I edited the post to better explain what I'm looking for with this discussion.

In 4.1.1, I had modified SupersetIndexView(IndexView) in initialization/init.py so that, after logging in, users were redirected to a different URL depending on their role. In other words, instead of always sending users to /superset/welcome/, I was routing each type of user to a specific dashboard or page after authentication.

After upgrading to 6.0.0, that customization no longer seems to apply.

What is the recommended way to achieve this in v6?

[dosubot[bot]]

@carlosaran667 Apologies for the incorrect suggestion earlier. I did more research and found that the CUSTOM_SECURITY_MANAGER approach doesn't work for this because v6 uses a unified SupersetAuthView that ignores custom auth view attributes.

The post-login flow in v6 is: SupersetAuthView.login() → SupersetIndexView.index() → Superset.welcome(). The recommended approach is to override the Superset.welcome() endpoint using FLASK_APP_MUTATOR:

# superset_config.py
from flask import g, redirect, url_for
from flask_appbuilder import expose
from superset.views.core import Superset
from superset.utils.core import get_user_id

class CustomSuperset(Superset):
    @expose("/welcome/")
    def welcome(self):
        if not g.user or not get_user_id():
            from superset.extensions import appbuilder
            return redirect(appbuilder.get_url_for_login)
        
        # Role-based redirect logic
        user_roles = [role.name for role in g.user.roles]
        
        if 'Admin' in user_roles:
            return redirect('/dashboard/list/')
        elif 'Alpha' in user_roles:
            return redirect('/chart/list/')
        # Add more role conditions as needed
        
        # Fall back to default welcome behavior
        return super().welcome()

def FLASK_APP_MUTATOR(app):
    app.appbuilder.add_view_no_menu(CustomSuperset)

This re-registers the Superset view with your custom welcome() method, which is the endpoint users land on after login. Adjust the role names and redirect URLs to match your requirements.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[carlosaran667]

For anybody interested, the solution is to write this piece of code in superset_config.py:

def FLASK_APP_MUTATOR(app):
    from flask import g, redirect, request
    from flask_login import current_user

    @app.before_request
    def clearbi_role_redirect():
        if request.path != "/superset/welcome/":
            return None

        if not current_user or not current_user.is_authenticated:
            return None

        user_roles = [role.name for role in g.user.roles]

        if "Role1" in user_roles:
            return redirect("/url1")

        if "Role2" in user_roles:
            return redirect("/url2")

        return None

Remember to change the role names and the urls.

[sfirke]

Excellent! Thanks for sharing back the answer.