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: content/docs/guides/(data-access)/definitions/access-policies.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,11 +41,11 @@ Access policies evaluate claims and key/value pairs in the provided context. The
41
41
42
42
-**context.server**: This context is generated by the server and is generally considered trusted. It includes information like trusted JWT claims, IP addresses, and actions.
43
43
-**context.server.claims**: Contains claims extracted from a JSON Web Token (JWT) that has been signed by a trusted issuer. This is typically used for claims that are standardized and validated by an identity provider like Okta.
44
-
-**context.server.purpose_names**: the purposes specified on an accessor to which this access policy is attached (does not apply in all cases)
45
-
-**context.server.ip_address**: the IP address of the user or system initiating the request
44
+
-**context.server.purpose_names**: the purposes specified on an accessor to which this access policy is attached (does not apply in all cases).
45
+
-**context.server.ip_address**: the IP address of the user or system initiating the request.
46
46
-**context.client**: This context contains key/value pairs specified in the request comments by the client and is not considered trusted. It includes data such as user-specified parameters that are not verified by the server.
47
47
-**context.user**: Information about data for the user whose data is row being accessed.
48
-
evaluated by the access policy
48
+
evaluated by the access policy.
49
49
-**context.query**: Specific query parameters relevant to the request.
50
50
-**context.row_data**: Specific Column data for the user row data values related to being evaluated by the request.
51
51
@@ -232,7 +232,7 @@ function policy(context, params) {
232
232
233
233
UserClouds has several built-in access policies for common use cases, like role-based and time-based expiration of data. However you can also create custom policies, in two ways:
234
234
235
-
- Call the [CreateAccessPolicy API](/docs/reference/tokenizer/policies/access/post)
236
-
- Compose a new policy from existing policies and parametrizable templates in the UserClouds Console
235
+
- Call the [CreateAccessPolicy API](/docs/reference/tokenizer/policies/access/post).
236
+
- Compose a new policy from existing policies and parametrizable templates in the UserClouds Console.
237
237
238
238
To learn more about creating access policies, see our How to Guide on Creating Access Policies.
0 commit comments