Monday, October 5, 2026

How to Set Up Okta Single Sign-On for Apache Superset



Password logins are the first thing an auditor asks about and the last thing anyone wants to manage by hand.
If your team already uses Okta for everything else, Superset should not be the exception: one identity, one place to offboard, and roles that follow the person rather than the login.

Apache Superset supports this out of the box through Flask-AppBuilder (FAB), the framework Superset is built on. The pieces are all there. What is missing is a single, current walkthrough that covers the Okta side, the Superset side, the role mapping, and the handful of reverse-proxy and cookie settings that turn a working configuration into a redirect loop. This is that walkthrough.

By the end, you will have:

  •  Okta as the only login path for Superset, with the local password form gone.

  •  Users created automatically on first login, with their Okta groups mapped to Superset roles.

  •  Role changes in Okta reflected in Superset at next login.

  •  A troubleshooting table for the errors this setup produces in practice.


The configuration shown here applies to Superset 2.1 through 4.x. The examples were written against Superset 4.x with the Flask-AppBuilder 4 series it ships with.

See It in Action →


No comments:

Post a Comment