Skip to content

Added relationship PBAC to the Deprecations, additions, and compatibility page #1239

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 5 commits into from
Apr 29, 2025
Merged

Added relationship PBAC to the Deprecations, additions, and compatibility page #1239

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
10ee856
added relationship PBAC to the Deprecations, additions, and compatibi…
HannesSandberg Apr 10, 2025
34e1408
review fix
HannesSandberg Apr 11, 2025
56dd44b
review fixes
HannesSandberg Apr 11, 2025
3d519ad
Update modules/ROOT/pages/deprecations-additions-removals-compatibili…
HannesSandberg Apr 15, 2025
887d951
Merge branch 'dev' into relationship-pbac
JPryce-Aklundh Apr 29, 2025
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
17 changes: 17 additions & 0 deletions modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,23 @@ CALL (i) {
This option applies an exponential delay between retries for transaction batches failing due to transient errors, with an optional maximum retry duration, and handles failure based on a specified fallback error mode if the transaction does not succeed within the given time.
For more information, see xref:subqueries/subqueries-in-transactions#on-error-retry[`CALL` subqueries in transactions -> `ON ERROR RETRY`].

a|
label:functionality[]
label:new[]
[source, cypher, role=noheader]
----
GRANT READ {*} ON GRAPH * FOR ()-[r]-() WHERE r.securityLevel > 3 TO regularUsers
----
[source, cypher, role=noheader]
----
GRANT TRAVERSE ON GRAPH * FOR ()-[r:Knows]-() WHERE r.classification IS NULL TO regularUsers
Copy link
Contributor

@ikwattro ikwattro Apr 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the examples could follow the neo4j syntax recommendations https://neo4j.com/docs/cypher-manual/current/syntax/naming/#_recommendations :KNOWS

Copy link
Contributor Author

@HannesSandberg HannesSandberg Apr 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just out of curiosity, do you know why the naming convention is camel-case for labels and uppercase for relationship types?

Copy link
Contributor

@ikwattro ikwattro Apr 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good question :) I don't have the answer.

----
[source, cypher, role=noheader]
----
DENY MATCH {*} ON GRAPH * FOR ()-[r]-() WHERE r.classification <> 'UNCLASSIFIED' TO regularUsers
----
| Property-based access control for relationships is now supported in Enterprise Edition. For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/property-based-access-control[property-based access control]

|===

[[cypher-deprecations-additions-removals-2025.01]]
Expand Down