Skip to content

Add token privilege notes #1015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 12, 2024
Merged

Add token privilege notes #1015

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
210ded1
add token privilege notes
JPryce-Aklundh Aug 9, 2024
5728761
fix
JPryce-Aklundh Aug 9, 2024
b6d8b98
Merge branch '4.4' into add_token_privilege
JPryce-Aklundh Aug 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions modules/ROOT/pages/administration/access-control/database-administration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -837,6 +837,10 @@ GRANT NAME [MANAGEMENT]

|===

[NOTE]
====
The `SHOW PRIVILEGES` commands return the `NAME MANAGEMENT` privilege as the action `token`, when not using `AS COMMANDS`.
====

For example, to grant the role `regularUsers` the ability to create new properties on nodes or relationships on the database `neo4j`, use:

Expand Down
15 changes: 15 additions & 0 deletions modules/ROOT/pages/administration/access-control/manage-privileges.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -599,6 +599,11 @@ Lists all privileges for all roles:
6+a|Rows: 39
|===

[NOTE]
====
The `token` action corresponds to the `NAME MANAGEMENT` privilege.
====

It is also possible to filter and sort the results by using `YIELD`, `ORDER BY` and `WHERE`:

[source, cypher, role=noplay]
Expand Down Expand Up @@ -688,6 +693,11 @@ In this example:
4+a|Rows: 12
|===

[NOTE]
====
The `token` action corresponds to the `NAME MANAGEMENT` privilege.
====

`WHERE` can also be used without `YIELD`:

[source, cypher, role=noplay]
Expand Down Expand Up @@ -782,6 +792,11 @@ SHOW PRIVILEGES YIELD * RETURN role, access, collect([graph, resource, segment,
3+a|Rows: 8
|===

[NOTE]
====
The `token` action corresponds to the `NAME MANAGEMENT` privilege.
====

The `RETURN` clause can also be used to order and paginate the results, which is useful when combined with `YIELD` and `WHERE`.
In this example the query returns privileges for display five-per-page, and skips the first five to display the second page.

Expand Down
8 changes: 7 additions & 1 deletion modules/ROOT/pages/administration/access-control/privileges-writes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -380,10 +380,16 @@ GRANT ALL GRAPH PRIVILEGES ON GRAPH neo4j TO regularUsers

[NOTE]
====
Unlike the more specific `READ` and `WRITE` commands, it is not possible to restrict `ALL GRAPH PRIVILEGES` to specific +ELEMENTS, +NODES+ or +RELATIONSHIPS+.
Unlike the more specific `READ` and `WRITE` commands, it is not possible to restrict `ALL GRAPH PRIVILEGES` to specific +ELEMENTS+, +NODES+ or +RELATIONSHIPS+.
If you wish to prevent a user from reading or writing to a subset of database objects, a `GRANT ALL GRAPH PRIVILEGES` can be combined with more specific `DENY` commands to target these elements.
====

[NOTE]
====
The `ALL GRAPH PRIVILEGES` privilege does not allow creating new labels, relationship types, or property names.
These are instead managed by the `NAME MANAGEMENT` privileges.
====

The `ALL GRAPH PRIVILEGES` privilege can also be denied:

[source, syntax, role="noheader"]
Expand Down