Apache Superset single sign-on with Keycloak
Configuring Superset to log in through Keycloak over OpenID Connect: realm and client setup, the provider block, mapping Keycloak groups or roles to Superset roles and logout behavior.

Connecting Superset login to specific identity providers and directories, and mapping their groups to Superset roles, based on the Superset and Flask-AppBuilder documentation.
Configuring Superset to log in through Keycloak over OpenID Connect: realm and client setup, the provider block, mapping Keycloak groups or roles to Superset roles and logout behavior.
Signing in to Superset with Microsoft Entra ID: app registration, tenant endpoints, group claims and the group overage limit, role mapping and keeping a break-glass admin.
Using Okta as Superset's identity provider: OIDC application setup, the groups scope, mapping Okta groups to Superset roles and deprovisioning users who leave.
Letting Google Workspace users sign in to Superset: OAuth client setup, restricting to your domain, default roles for self-registered users and group-based access without directory sync.
Authenticating Superset users against LDAP or Active Directory: python-ldap, LDAPS or STARTTLS, search filters, group search for role mapping and the user experience compared with SSO.
Designing AUTH_ROLES_MAPPING so access follows IdP groups: role naming, syncing at login, default roles for new users, combining mapped roles with RLS and handling users in many groups.
Adding Proof Key for Code Exchange to Superset OAuth providers: when public clients need it, why it is recommended even with a client secret and testing the flow with your IdP.
Removing stored database passwords for AWS sources with Superset IAM authentication: the feature flag, boto3, encrypted extra settings, cross-account role assumption and SSL requirements.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.