-
Notifications
You must be signed in to change notification settings - Fork 493
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.
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
Neo4j 4 on Aura permissions adjustment due to PUBLIC role #1612
Comments
This is due to a security feature introduced in Neo4j 3.1 allowing procedures to run with adjusted security settings, so that Neo4j could provide a kind of fine-grained access control. Now that real fine-grained access control is available in Neo4j 4.0, all that is missing to facilitate the removal of the old mechanism is procedure privileges. There are plans to add these to Neo4j, hopefully soon. Until that happens, Cypher run through a procedure can be affected by the mode of the procedure, as we see here. |
We also need to add a |
Probably we should also add an alias |
@jexp I don't know what needs to be done, other than adjusting the mode of the procedure as suggested by @craigtaverner . Also not sure if this is something you want to do -- in theory any APOC call which can run Cypher needs every possible permission that the database could grant to a procedure, since you can do pretty much anything with cypher. Less clear to me is whether apoc.cypher.doIt should work if it's not cypher (are index creations cypher? CREATE USER definitely isn't cypher) |
@jexp I created a pr with the procedure |
#1968) Co-authored-by: Giuseppe Villani <[email protected]>
#1968) (#1981) Co-authored-by: Giuseppe Villani <[email protected]> Co-authored-by: Andrea Santurbano <[email protected]> Co-authored-by: Giuseppe Villani <[email protected]>
#1968) (#1981) Co-authored-by: Giuseppe Villani <[email protected]> Co-authored-by: Andrea Santurbano <[email protected]> Co-authored-by: Giuseppe Villani <[email protected]>
…to PUBLIC role (neo4j-contrib#1968) Co-authored-by: Giuseppe Villani <[email protected]>
…to PUBLIC role (neo4j-contrib#1968) Co-authored-by: Giuseppe Villani <[email protected]>
…to PUBLIC role (neo4j-contrib#1968) Co-authored-by: Giuseppe Villani <[email protected]>
…to PUBLIC role (neo4j-contrib#1968) Co-authored-by: Giuseppe Villani <[email protected]>
#1968) Co-authored-by: Giuseppe Villani <[email protected]>
For Neo4j 4 running on Aura, the neo4j user was adjusted to have the role PUBLIC, with some special exceptions. The reasons why this is the case are complicated, but that's how it works.
APOC has some security checks in it (I think) which is causing some functions to fail specifically on Neo4j 4 running on Aura.
Specific example, this succeeds in the "Neo4j 4 on Aura" environment:
But this fails:
The text was updated successfully, but these errors were encountered: