Skip to content

Commit 604eaff

Browse files
minor changes
1 parent 1ad904b commit 604eaff

File tree

2 files changed

+8
-7
lines changed

2 files changed

+8
-7
lines changed

modules/ROOT/pages/authentication-authorization/limitations.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -391,7 +391,8 @@ So due to the additional data access required by the security checks, this opera
391391
[[property-based-access-control-limitations]]
392392
=== Property-based access control limitations
393393
Extra element-level security checks are necessary when adding security rules based on property rules, and these can have a significant performance impact.
394-
The following example shows how the database behaves when adding security rules to roles `restricted` and `unrestricted`:
394+
395+
The following example shows how the database behaves when adding security rules for nodes to roles `restricted` and `unrestricted`, the same limitations apply to relationships as well:
395396

396397
[source, cypher]
397398
----

modules/ROOT/pages/authentication-authorization/property-based-access-control.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ CREATE ROLE regularUsers;
1212
[[property-based-access-control]]
1313
= Property-based access control
1414

15-
Property-based access control grants permissions to users to read element properties based on property/value conditions.
15+
Property-based access control grants/denies permission to read or traverse elements based on property/value conditions.
1616
Each property-based privilege can only be restricted by a single property.
17-
For information about read privileges and their syntax, see xref:authentication-authorization/privileges-reads.adoc[Read privileges].
17+
For information and syntax for these privileges, see xref:authentication-authorization/privileges-reads.adoc[Read privileges].
1818

1919
[IMPORTANT]
2020
====
@@ -25,7 +25,7 @@ Users who can change this property can affect the granted property-based privile
2525

2626
== Syntax
2727

28-
To specify the property/value conditions of the read privilege, you can use the following syntax:
28+
To specify the property/value conditions of the privilege, you can use the following syntax:
2929

3030
[source, syntax, role="noheader"]
3131
----
@@ -99,13 +99,13 @@ Alternatively, you can use the following syntax:
9999
GRANT READ { address } ON GRAPH * FOR (:Email|Website {domain: 'exampledomain.com'}) TO regularUsers
100100
----
101101

102-
=== Grant a property-based privilege on a specific property using the value of that same property
102+
=== Grant a property-based privilege on a specific property using the value of another property
103103

104-
The following example shows how to grant permission to `READ` the `since` property on `OWNS` relationships having `since` equal to `2025-01-01` to role `regularUsers`:
104+
The following example shows how to grant permission to `READ` the `since` property on `OWNS` relationships having `classification` equal to `UNCLASSIFIED` to role `regularUsers`:
105105

106106
[source, syntax, role="noheader"]
107107
----
108-
GRANT READ { since } ON GRAPH * FOR ()-[o:OWNS]-() WHERE o.since = date("2025-01-01") TO regularUsers
108+
GRANT READ { since } ON GRAPH * FOR ()-[o:OWNS]-() WHERE o.classification = 'UNCLASSIFIED' TO regularUsers
109109
----
110110

111111
=== Grant a property-based privilege using `NULL`

0 commit comments

Comments
 (0)