Skip to content

Commit a3695b1

Browse files
chore: added missing images (#2232)
1 parent e83260a commit a3695b1

File tree

10 files changed

+8
-12
lines changed

10 files changed

+8
-12
lines changed

docs/polis/_assets/sso/box-1.png

30.5 KB
Loading
47.9 KB
Loading
50.1 KB
Loading
40.9 KB
Loading
62.2 KB
Loading
49.3 KB
Loading
34.7 KB
Loading
15.2 KB
Loading

docs/polis/guides/configuring-saml-sso.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,9 +46,7 @@ the **Security** tab.
4646

4747
Here is how Sentry does the SAML SSO configuration for their customers.
4848

49-
<p>
50-
<img src="/images/guides/sso/sentry-metadata.png" style={{ border: "1px solid black" }} title="The SAML SSO settings" />
51-
</p>
49+
![The SAML SSO settings](../_assets/sso/sentry-metadata.png)
5250

5351
To create an [SSO connection with Ory Polis](../sso-flow/#2-sso-connection-api), you must pass the tenant identifier, product
5452
name, and XML metadata. So your settings page UI must display a form to capture the XML Metadata.

docs/polis/guides/login-with-saml-sso.mdx

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ they click the button.
2424

2525
**Postman** takes this approach to enable SAML SSO for their enterprise users.
2626

27-
<img src="/images/guides/sso/postman-1.png" style={{ border: "1px solid black" }} />
27+
![Postman Login 1](../_assets/sso/postman-1.png)
2828

29-
<img src="/images/guides/sso/postman-2.png" style={{ border: "1px solid black" }} />
29+
![Postman Login 2](../_assets/sso/postman-2.png)
3030

3131
The user flow would be something similar to the one below.
3232

@@ -43,9 +43,9 @@ This approach hides the password field if SSO is enabled for a domain.
4343

4444
You can see this approach on the **Dropbox** login form.
4545

46-
<img src="/images/guides/sso/dropbox-1.png" style={{ border: "1px solid black" }} />
46+
![Dropbox Login 1](../_assets/sso/dropbox-1.png)
4747

48-
<img src="/images/guides/sso/dropbox-2.png" style={{ border: "1px solid black" }} />
48+
![Dropbox Login 2](../_assets/sso/dropbox-2.png)
4949

5050
The user flow would be something similar to the one below.
5151

@@ -63,11 +63,9 @@ application redirects users to the subdomain page to show the available authenti
6363

6464
You can see this approach on the **Freshchat or Freshworks** login form.
6565

66-
<img src="/images/guides/sso/freshchat-1.png" style={{ border: "1px solid black" }} />
66+
![Freshchat Login 1](../_assets/sso/freshchat-1.png)
6767

68-
<p align="center">
69-
<img src="/images/guides/sso/freshchat-2.png" width="70%" style={{ border: "1px solid black" }} />
70-
</p>
68+
![Freshchat Login 2](../_assets/sso/freshchat-2.png)
7169

7270
The user flow would be something similar to the one below.
7371

@@ -85,7 +83,7 @@ the current user.
8583

8684
**Box** uses this approach for its authentication flow.
8785

88-
<img src="/images/guides/sso/box-1.png" style={{ border: "1px solid black" }} />
86+
![Box Login](../_assets/sso/box-1.png)
8987

9088
The user flow would be something similar to the one below.
9189

0 commit comments

Comments
 (0)