Add page aliases for 4.2 to 4.3

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

@@ -1,7 +1,9 @@
 [role=enterprise-edition]
 [[access-control-built-in-roles]]
 = Built-in roles and privileges
-:description: This section explains the default privileges of the built-in roles in Neo4j and how to recreate them if needed. 
+:description: This section explains the default privileges of the built-in roles in Neo4j and how to recreate them if needed.
+:page-aliases: administration/security/built-in-roles.adoc
+
 
 All of the commands described in this chapter require that the user executing the commands has the rights to do so.
 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

@@ -1,7 +1,8 @@
 [role=enterprise-edition]
 [[access-control-database-administration]]
 = Database administration
-:description: This section explains how to use Cypher to manage Neo4j database administrative privileges. 
+:description: This section explains how to use Cypher to manage Neo4j database administrative privileges.
+:page-aliases: administration/security/administration.adoc
 
 The administrators can use the following Cypher commands to manage Neo4j database administrative rights.
 The components of the database privilege commands are:

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

@@ -1,7 +1,9 @@
 [role=enterprise-edition]
 [[access-control-dbms-administration]]
 = DBMS administration
-:description: This section explains how to use Cypher to manage Neo4j DBMS administrative privileges. 
+:description: This section explains how to use Cypher to manage Neo4j DBMS administrative privileges.
+// :page-aliases: administration/security/administration.adoc
+
 
 All DBMS privileges are relevant system-wide.
 Like user management, they do not belong to one specific database or graph.

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

@@ -1,6 +1,8 @@
 [[access-control]]
 = Access control
-:description: This chapter explains how to manage Neo4j role-based access control and fine-grained security. 
+:description: This chapter explains how to manage Neo4j role-based access control and fine-grained security.
+:page-aliases: administration/security/index.adoc, administration/security/introduction.adoc
+
 
 Neo4j has a complex security model stored in the system graph, maintained in a special database called the `system` database.
 All administrative commands need to be executing against the `system` database.

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

@@ -1,6 +1,8 @@
 [[access-control-limitations]]
 = Limitations
 :description: This section explains known limitations and implications of Neo4js role-based access control security. 
+:page-aliases: administration/security/limitations.adoc
+
 
 [[access-control-limitations-indexes]]
 == Security and Indexes

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

@@ -1,6 +1,8 @@
 [[access-control-manage-privileges]]
 = Managing privileges
-:description: This section explains how to use Cypher to manage privileges for Neo4j role-based access control and fine-grained security. 
+:description: This section explains how to use Cypher to manage privileges for Neo4j role-based access control and fine-grained security.
+:page-aliases: administration/security/subgraph.adoc
+
 
 Privileges control the access rights to graph elements using a combined allowlist/denylist mechanism.
 It is possible to grant access, or deny access, or a combination of the two.

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

@@ -1,7 +1,10 @@
 [role=enterprise-edition]
 [[access-control-manage-roles]]
 = Managing roles
-:description: This section explains how to use Cypher to manage roles in Neo4j. 
+:description: This section explains how to use Cypher to manage roles in Neo4j.
+// Note: we can't add a page-alias here because it is already specified in manage-users.adoc
+// :page-aliases: administration/security/users-and-roles.adoc
+
 
 Roles can be created and managed using a set of Cypher administration commands executed against the `system` database.
 

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

@@ -1,6 +1,8 @@
 [[access-control-manage-users]]
 = Managing users
-:description: This section explains how to use Cypher to manage users in Neo4j. 
+:description: This section explains how to use Cypher to manage users in Neo4j.
+:page-aliases: administration/security/users-and-roles.adoc
+
 
 Users can be created and managed using a set of Cypher administration commands executed against the `system` database.
 When connected to the DBMS over `bolt`, administration commands are automatically routed to the `system` database.

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

@@ -2,6 +2,8 @@
 [[access-control-privileges-reads]]
 = Read privileges
 :description: This section explains how to use Cypher to manage read privileges on graphs. 
+:page-aliases: administration/security/reads.adoc
+
 
 There are three separate read privileges:
 

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

@@ -2,6 +2,8 @@
 [[access-control-privileges-writes]]
 = Write privileges
 :description: This section explains how to use Cypher to manage write privileges on graphs. 
+:page-aliases: administration/security/writes.adoc
+
 
 Write privileges are defined for different parts of the graph:
 

modules/ROOT/pages/constraints/index.adoc

@@ -1,6 +1,8 @@
 [[administration-constraints]]
 = Constraints
 :description: This section explains how to manage constraints used for ensuring data integrity. 
+:page-aliases: administration/constraints.adoc
+
 
 == Types of constraint
 

modules/ROOT/pages/databases.adoc

@@ -1,6 +1,8 @@
 [[administration-databases]]
 = Database management
-:description: This chapter explains how to use Cypher to manage Neo4j databases: creating, deleting, starting and stopping individual databases within a single server. 
+:description: This chapter explains how to use Cypher to manage Neo4j databases: creating, deleting, starting and stopping individual databases within a single server.
+:page-aliases: administration/index.adoc, administration/databases.adoc
+
 
 Neo4j supports the management of multiple databases within the same DBMS.
 The metadata for these databases, including the associated security model, is maintained in a special database called the `system` database.

modules/ROOT/pages/indexes-for-full-text-search.adoc

@@ -1,6 +1,8 @@
 [[administration-indexes-fulltext-search]]
 = Full-text search index
 :description: This chapter describes how to use full-text indexes, to enable full-text search. 
+:page-aliases: administration/indexes-for-full-text-search.adoc
+
 
 Full-text indexes are powered by the link:https://lucene.apache.org/[Apache Lucene] indexing and search library, and can be used to index nodes and relationships by string properties.
 A full-text index allows you to write queries that match within the _contents_ of indexed string properties.

modules/ROOT/pages/indexes-for-search-performance.adoc

@@ -1,6 +1,8 @@
 [[administration-indexes-search-performance]]
 = Indexes for search performance
-:description: This section explains how to manage indexes used for search performance. 
+:description: This section explains how to manage indexes used for search performance.
+:page-aliases: administration/indexes-for-search-performance.adoc
+
 
 This section describes how to manage indexes.
 For query performance purposes, it is important to also understand how the indexes are used by the Cypher planner.