JWT-based authentication is only available on Pro and Enterprise plans (both self-hosted and on Metabase Cloud).
You can connect Metabase to your identity provider using JSON Web Tokens (JWT) to authenticate people.
Metabase supports two auth flows that can be used with JWT:
- Authorization Code Flow
- Authorization Code Flow with PKCE
Metabase’s auth flows are custom workflows modelled after OAuth 2.0. You can use the auth flow with PKCE to incorporate random keys generated on demand.
Currently, the only algorithm Metabase supports is HS256 (HMAC + SHA-256.
Typical flow for a JWT-based SSO interaction with Metabase
Assuming your site is localhost serving on port 3000:
- Person attempts to view a question, e.g.,
- If the person isn’t logged in, Metabase redirects them to
- Retaining the original
/question/1-superb-questionURI, Metabase redirects the person to the SSO provider (the authentication app).
- Person logs in using the basic form.
- In the event of a successful sign-in, your authentication app should issue a GET request to your Metabase endpoint with the token and the “return to” URI:
- Metabase verifies the JSON Web Token, logs the person in, then redirects the person to their original destination,
Enabling JWT authentication
Navigate to the Admin>Settings section of the Admin area, then click on the Authentication tab. Click the Configure button in the JWT section of this page, and you’ll see this form:
Click the toggle at the top of the form to enable JWT-based authentication. Make sure to set the toggle to Enabled, otherwise JWT authentication won’t work, even if all of your other settings are correct.
Here’s a breakdown of each of the settings:
JWT Identity Provider URI: This is where Metabase will redirect login requests. That is, it’s where your users go to log in through your identity provider.
String Used by the JWT Signing Key: The string used to seed the private key used to validate JWT messages. Both Metabase and the authentication app should have the same JWT signing key.
User attribute configuration (optional)
These are additional settings you can fill in to pass user attributes to Metabase.
- Email attribute: the key to retrieve each JWT user’s email address.
- First Name attribute: the key to retrieve each JWT user’s first name.
- Last Name attribute: if you guessed that this is the key to retrieve each JWT user’s last name, well then you have been paying attention.
You can use your JWT to assign Metabase users to custom groups by following these steps:
- Add this to your JWT:
- In the Admin Panel in Metabase, go to the Authentication tab of the Settings section and click the Configure button on JWT. On this screen, turn on the toggle under “SYNCHRONIZE GROUP MEMBERSHIPS”.
- Next, click Edit Mappings. In this modal, type in the name of one of your groups as defined in the JWT, then click Add. In the row that appears, click the dropdown to pick the Metabase group that this should map to. Repeat this for each of the groups you want to map.
Creating Metabase accounts with SSO
Paid plans charge for each additional account.
A new SSO login will automatically create a new Metabase account.
Metabase accounts created with an external identity provider login don’t have passwords. People who sign up for Metabase using an IdP must continue to use the IdP to log into Metabase.
Disabling password logins
Avoid locking yourself out of your Metabase! This setting will apply to all Metabase accounts, including your Metabase admin account. We recommend that you keep password authentication enabled. This will safeguard you from getting locked out of Metabase in case of any problems with SSO.
To require people to log in with SSO, disable password authentication from Admin settings > Authentication.
Note about Azure
If you’re using Azure, you may need to use Azure AD B2C. Check out their tokens overview.
Example code using JWT-based authentication
You can find example code that uses JWT authentication in the SSO examples repository.