Skip to content

Commit 1951837

Browse files
authored
Add page aliases for 4.2 to 4.3 (#719)
1 parent 73958da commit 1951837

14 files changed

+37
-9
lines changed

modules/ROOT/pages/access-control/built-in-roles.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
[role=enterprise-edition]
22
[[access-control-built-in-roles]]
33
= Built-in roles and privileges
4-
:description: This section explains the default privileges of the built-in roles in Neo4j and how to recreate them if needed.
4+
:description: This section explains the default privileges of the built-in roles in Neo4j and how to recreate them if needed.
5+
:page-aliases: administration/security/built-in-roles.adoc
6+
57

68
All of the commands described in this chapter require that the user executing the commands has the rights to do so.
79
The privileges listed in the following sections are the default set of privileges for each built-in role:

modules/ROOT/pages/access-control/database-administration.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
[role=enterprise-edition]
22
[[access-control-database-administration]]
33
= Database administration
4-
:description: This section explains how to use Cypher to manage Neo4j database administrative privileges.
4+
:description: This section explains how to use Cypher to manage Neo4j database administrative privileges.
5+
:page-aliases: administration/security/administration.adoc
56

67
The administrators can use the following Cypher commands to manage Neo4j database administrative rights.
78
The components of the database privilege commands are:

modules/ROOT/pages/access-control/dbms-administration.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
[role=enterprise-edition]
22
[[access-control-dbms-administration]]
33
= DBMS administration
4-
:description: This section explains how to use Cypher to manage Neo4j DBMS administrative privileges.
4+
:description: This section explains how to use Cypher to manage Neo4j DBMS administrative privileges.
5+
// :page-aliases: administration/security/administration.adoc
6+
57

68
All DBMS privileges are relevant system-wide.
79
Like user management, they do not belong to one specific database or graph.

modules/ROOT/pages/access-control/index.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
[[access-control]]
22
= Access control
3-
:description: This chapter explains how to manage Neo4j role-based access control and fine-grained security.
3+
:description: This chapter explains how to manage Neo4j role-based access control and fine-grained security.
4+
:page-aliases: administration/security/index.adoc, administration/security/introduction.adoc
5+
46

57
Neo4j has a complex security model stored in the system graph, maintained in a special database called the `system` database.
68
All administrative commands need to be executing against the `system` database.

modules/ROOT/pages/access-control/limitations.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
[[access-control-limitations]]
22
= Limitations
33
:description: This section explains known limitations and implications of Neo4js role-based access control security.
4+
:page-aliases: administration/security/limitations.adoc
5+
46

57
[[access-control-limitations-indexes]]
68
== Security and Indexes

modules/ROOT/pages/access-control/manage-privileges.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
[[access-control-manage-privileges]]
22
= Managing privileges
3-
:description: This section explains how to use Cypher to manage privileges for Neo4j role-based access control and fine-grained security.
3+
:description: This section explains how to use Cypher to manage privileges for Neo4j role-based access control and fine-grained security.
4+
:page-aliases: administration/security/subgraph.adoc
5+
46

57
Privileges control the access rights to graph elements using a combined allowlist/denylist mechanism.
68
It is possible to grant access, or deny access, or a combination of the two.

modules/ROOT/pages/access-control/manage-roles.adoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,10 @@
11
[role=enterprise-edition]
22
[[access-control-manage-roles]]
33
= Managing roles
4-
:description: This section explains how to use Cypher to manage roles in Neo4j.
4+
:description: This section explains how to use Cypher to manage roles in Neo4j.
5+
// Note: we can't add a page-alias here because it is already specified in manage-users.adoc
6+
// :page-aliases: administration/security/users-and-roles.adoc
7+
58

69
Roles can be created and managed using a set of Cypher administration commands executed against the `system` database.
710

modules/ROOT/pages/access-control/manage-users.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
[[access-control-manage-users]]
22
= Managing users
3-
:description: This section explains how to use Cypher to manage users in Neo4j.
3+
:description: This section explains how to use Cypher to manage users in Neo4j.
4+
:page-aliases: administration/security/users-and-roles.adoc
5+
46

57
Users can be created and managed using a set of Cypher administration commands executed against the `system` database.
68
When connected to the DBMS over `bolt`, administration commands are automatically routed to the `system` database.

modules/ROOT/pages/access-control/privileges-reads.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
[[access-control-privileges-reads]]
33
= Read privileges
44
:description: This section explains how to use Cypher to manage read privileges on graphs.
5+
:page-aliases: administration/security/reads.adoc
6+
57

68
There are three separate read privileges:
79

modules/ROOT/pages/access-control/privileges-writes.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
[[access-control-privileges-writes]]
33
= Write privileges
44
:description: This section explains how to use Cypher to manage write privileges on graphs.
5+
:page-aliases: administration/security/writes.adoc
6+
57

68
Write privileges are defined for different parts of the graph:
79

0 commit comments

Comments
 (0)