Skip to content

Commit 994b9bd

Browse files
authored
Merge pull request #4482 from ClickHouse/Blargian-patch-803946
force load image
2 parents e687723 + 43d2e5b commit 994b9bd

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

docs/cloud/guides/security/cloud_access_management/saml-sso-setup.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ We recommend setting up a **direct link to your organization** in addition to yo
3939

4040
1. Sign in to your [ClickHouse Cloud](https://console.clickhouse.cloud) organization.
4141

42-
<Image img={samlOrgId} size="md" alt="Organization ID" />
42+
<Image img={samlOrgId} size="md" alt="Organization ID" force/>
4343
4444
3. In the lower left corner, click on your organization name under **Organization**.
4545

@@ -197,7 +197,7 @@ You will configure two App Integrations in Okta for each ClickHouse organization
197197

198198
12. On the **Sign On** tab for your new app, click the **View SAML setup instructions** button.
199199

200-
<Image img={samlOktaSetup} size="md" alt="Okta SAML Setup Instructions" />
200+
<Image img={samlOktaSetup} size="md" alt="Okta SAML Setup Instructions" force/>
201201

202202
13. Gather these three items and go to Submit a Support Case above to complete the process.
203203
- Identity Provider Single Sign-On URL
@@ -215,7 +215,7 @@ You will configure one SAML app in Google for each organization and must provide
215215

216216
1. Go to your Google Admin console (admin.google.com).
217217

218-
<Image img={samlGoogleApp} size="md" alt="Google SAML App" />
218+
<Image img={samlGoogleApp} size="md" alt="Google SAML App" force/>
219219

220220
2. Click **Apps**, then **Web and mobile apps** on the left.
221221

@@ -272,7 +272,7 @@ Azure (Microsoft) SAML may also be referred to as Azure Active Directory (AD) or
272272

273273
5. Enter a name and select **Integrate any other application you don't find in the gallery (Non-gallery)**, then click **Create**.
274274

275-
<Image img={samlAzureApp} size="md" alt="Azure Non-Gallery App" />
275+
<Image img={samlAzureApp} size="md" alt="Azure Non-Gallery App" force/>
276276

277277
6. Click **Users and groups** on the left and assign users.
278278

@@ -298,7 +298,7 @@ Azure (Microsoft) SAML may also be referred to as Azure Active Directory (AD) or
298298
| (A) email | Basic | user.mail |
299299
| (U) /identity/claims/name | Omitted | user.mail |
300300

301-
<Image img={samlAzureClaims} size="md" alt="Attributes and Claims" />
301+
<Image img={samlAzureClaims} size="md" alt="Attributes and Claims" force/>
302302

303303
12. Gather these two items and go to Submit a Support Case above to complete the process:
304304
- Login URL
@@ -366,4 +366,3 @@ Security is our top priority when it comes to authentication. For this reason, w
366366
- **All users assigned to your app via your IdP must have the same email domain.** If you have vendors, contractors or consultants you would like to have access to your ClickHouse account, they must have an email address with the same domain (e.g. user@domain.com) as your employees.
367367

368368
- **We do not automatically link SSO and non-SSO accounts.** You may see multiple accounts for your users in your ClickHouse user list even if they are using the same email address.
369-

0 commit comments

Comments
 (0)