diff --git a/docs/people-and-groups/authenticating-with-jwt.md b/docs/people-and-groups/authenticating-with-jwt.md index ecf98d20ed77117ff1a08bff0eeb82af8d199a53..9faa586772a331ff878f2c1d80925b5b39109fda 100644 --- a/docs/people-and-groups/authenticating-with-jwt.md +++ b/docs/people-and-groups/authenticating-with-jwt.md @@ -26,7 +26,7 @@ Currently, the only algorithm Metabase supports is [HS256](https://en.wikipedia. Assuming your site is localhost serving on port 3000: 1. Person attempts to view a question, e.g., `http://localhost:3000/question/1-superb-question`. -2. If the person isn't logged in, Metabase redirects them to `http://localhost:3000/auth/sso/`. +2. If the person isn't logged in, Metabase redirects them to `http://localhost:3000/auth/sso`. 3. Retaining the original `/question/1-superb-question` URI, Metabase redirects the person to the SSO provider (the authentication app). 4. Person logs in using the basic form. 5. 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: `http://localhost:3000/auth/sso?jwt=TOKEN_GOES_HERE&return_to=/question/1-superb-question`. diff --git a/docs/people-and-groups/authenticating-with-saml.md b/docs/people-and-groups/authenticating-with-saml.md index d854af194b5c4de8f36baad5cbaf9ea968d0d150..9c59783a6355eae8bfcbc83f49a7cefcd45492a6 100644 --- a/docs/people-and-groups/authenticating-with-saml.md +++ b/docs/people-and-groups/authenticating-with-saml.md @@ -53,9 +53,9 @@ However, the names of the fields in the Metabase SAML form won't always match th ### URL the IdP should redirect back to -The redirect URL is the web address that people will be sent to after signing in with your IdP. To redirect people to your Metabase, your redirect URL should be your Metabase [Site URL](../configuring-metabase/settings.md#site-url), with `/auth/sso/` at the end. +The redirect URL is the web address that people will be sent to after signing in with your IdP. To redirect people to your Metabase, your redirect URL should be your Metabase [Site URL](../configuring-metabase/settings.md#site-url), with `/auth/sso` at the end. -For example, if your Metabase Site URL is `https://metabase.yourcompany.com`, you'll use `https://metabase.yourcompany.com/auth/sso/` as the redirect URL in your IdP's SAML form. +For example, if your Metabase Site URL is `https://metabase.yourcompany.com`, you'll use `https://metabase.yourcompany.com/auth/sso` as the redirect URL in your IdP's SAML form. Different IdPs use different names for the redirect URL. Here are some common examples: diff --git a/docs/people-and-groups/saml-auth0.md b/docs/people-and-groups/saml-auth0.md index 1e01813a7541bf64682848cc0ec04a052927d9b5..210c661afe2813da4137b1576162ac9f21191cf6 100644 --- a/docs/people-and-groups/saml-auth0.md +++ b/docs/people-and-groups/saml-auth0.md @@ -28,7 +28,7 @@ Enter “Metabase†as the application name with type “Regular Web Applicatio Now go to Settings tab inside Auth0's Metabase App and fill in the following values: - Application Login URI: the URL of your Metabase instance. -- Allowed Callback URLs: the URL that's below **Configure your identity provider (IdP)** in SAML settings inside Metabase (it ends with `/auth/sso/`). +- Allowed Callback URLs: the URL that's below **Configure your identity provider (IdP)** in SAML settings inside Metabase (it ends with `/auth/sso`).  diff --git a/docs/troubleshooting-guide/saml.md b/docs/troubleshooting-guide/saml.md index 80bc1a2ad0bd8a1b54482eb596a0b728c62989c9..4c7785235ff056f7f1b7a7cd95ad397d66b8b9d7 100644 --- a/docs/troubleshooting-guide/saml.md +++ b/docs/troubleshooting-guide/saml.md @@ -21,9 +21,9 @@ After filling out the authentication form with your identity provider, you're ta **Steps to take**: 1. You should have received an XML file of metadata from your identity provider. Open that metadata file, and look for the correct issuer or entity ID. This ID is a unique identifier for the identity provider. Depending on your provider, the issuer or entity ID usually looks something like this: - ``` - http://www.example.com/141xkex604w0Q5PN724v - ``` + ``` + http://www.example.com/141xkex604w0Q5PN724v + ``` 2. Copy the issuer or entity ID from the XML file. 3. Go to Metabase and select **Admin settings** > **Settings** > **Authentication** > **SAML**. Enter the issuer or entity ID into the **SAML Identity Provider Issuer** field. @@ -37,13 +37,13 @@ After filling out the authentication form with your identity provider, you go ba 1. Go to Metabase and select **Admin settings** > **Settings** > **Authentication** > **SAML**. Check that the certificate that you entered into the **SAML Identity Provider Certificate** field matches the certificate in the XML file you got from your identity provider. - - Depending on your provider, you might need to download the XML file, open it in a text editor, then copy and paste the certificate's contents into the **SAML Identity Provider Certificate** field in Metabase. + - Depending on your provider, you might need to download the XML file, open it in a text editor, then copy and paste the certificate's contents into the **SAML Identity Provider Certificate** field in Metabase. - - Note that your certificate text may include header and footer comments that look like `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`. These comments should be included when pasting your certificate text into Metabase. + - Note that your certificate text may include header and footer comments that look like `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`. These comments should be included when pasting your certificate text into Metabase. ## Is the SSO URL correct? -Verify that the Single Sign On URL (or equivalent) that you enter on your SAML provider’s website has `/auth/sso/` appended to it. For instance, if you want your users to end up at `https://metabase.mycompany.com`, the full URL should be `https://metabase.mycompany.com/auth/sso/`. +Verify that the Single Sign On URL (or equivalent) that you enter on your SAML provider’s website has `/auth/sso` appended to it. For instance, if you want your users to end up at `https://metabase.mycompany.com`, the full URL should be `https://metabase.mycompany.com/auth/sso`. ## Searching for private key and found a null