You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/security.mdx
+13-19Lines changed: 13 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,6 @@ By default, Yorkie allows requests from any origin. To enhance security, you can
11
11
12
12
Each project in Yorkie can have its own allowed origins settings, which can be managed through the [Dashboard]({{DASHBOARD_PATH}}).
13
13
14
-
<Alertstatus="warning"> Allowed origins settings are project-specific and may take up to **10 minutes** to be applied due to caching. </Alert>
15
-
16
14
#### Configuring Allowed Origins
17
15
18
16
1. Open the Project Settings page in the Dashboard.
@@ -25,21 +23,19 @@ Each project in Yorkie can have its own allowed origins settings, which can be m
25
23
26
24
The Auth Webhook provides fine-grained access control by validating client requests through an external authentication server. This allows you to enforce custom authorization logic, ensuring that only authorized users can access and modify Yorkie documents.
@@ -61,8 +57,6 @@ You can easily set up the Auth Webhook via the the [Dashboard]({{DASHBOARD_PATH}
61
57
62
58
Alternatively, you can configure the webhook using the Yorkie CLI. See updating the project for details. Refer to the [updating the project](/docs/cli#updating-the-project).
63
59
64
-
<Alertstatus="warning"> Changes to the configuration may take up to 10 minutes to take effect. </Alert>
65
-
66
60
##### 2. Client Configuration
67
61
68
62
To provide authentication tokens dynamically, use the `authTokenInjector` option when creating a Yorkie client:
0 commit comments