diff --git a/modules/ROOT/pages/authentication-authorization/index.adoc b/modules/ROOT/pages/authentication-authorization/index.adoc index 5db485a8e..2fc365811 100644 --- a/modules/ROOT/pages/authentication-authorization/index.adoc +++ b/modules/ROOT/pages/authentication-authorization/index.adoc @@ -3,6 +3,7 @@ = Authentication and authorization :description: An overview of authentication and authorization in Neo4j. :keywords: authentication, authorization, security, access control, roles, privileges, users, LDAP, Active Directory, Kerberos, SSO, single sign-on, authentication plugins, authentication providers, native auth provider, LDAP auth provider, Kerberos auth provider, SSO auth provider, custom auth provider, custom auth plugin, custom auth plugins, custom auth providers, custom authentication plugin, custom authentication plugins, custom authentication providers, custom authorization plugin, custom authorization plugins, custom authorization providers, custom authorisation plugin, custom authorisation plugin +:page-aliases: authentication-authorization/introduction.adoc, authentication-authorization/terminology.adoc This page provides an overview of authentication and authorization in Neo4j. diff --git a/modules/ROOT/pages/cloud-deployments/neo4j-gcp.adoc b/modules/ROOT/pages/cloud-deployments/neo4j-gcp.adoc index cc3ac79b7..f2c39a6df 100644 --- a/modules/ROOT/pages/cloud-deployments/neo4j-gcp.adoc +++ b/modules/ROOT/pages/cloud-deployments/neo4j-gcp.adoc @@ -1,4 +1,6 @@ :description: Deploy Neo4j on Google Cloud Platform (GCP) directly from the GCP Marketplace or by using the Neo4j Deployment Manager templates hosted on GitHub. +:page-aliases: cloud-deployments/neo4j-gcp/index.adoc, cloud-deployments/neo4j-gcp/single-instance-vm.adoc, cloud-deployments/neo4j-gcp/causal-cluster-vm.adoc, cloud-deployments/neo4j-gcp/automation-gcp.adoc + [[gcp]] = Neo4j on GCP diff --git a/modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc b/modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc index 5fb664f46..9e627fb26 100644 --- a/modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc +++ b/modules/ROOT/pages/clustering/monitoring/show-databases-monitoring.adoc @@ -1,4 +1,6 @@ :description: This section covers the use of `SHOW DATABASES`, and other related Cypher commands. +:page-aliases: monitoring/individual-db-states.adoc + [role=enterprise-edition] [[show-databases-monitoring]] = Monitor databases diff --git a/modules/ROOT/pages/clustering/setup/deploy.adoc b/modules/ROOT/pages/clustering/setup/deploy.adoc index b70fe8b7a..b5a6f5a4f 100644 --- a/modules/ROOT/pages/clustering/setup/deploy.adoc +++ b/modules/ROOT/pages/clustering/setup/deploy.adoc @@ -1,5 +1,5 @@ :description: This section describes how to deploy a Neo4j cluster. -:page-aliases: clustering/deploy.adoc +:page-aliases: clustering/deploy.adoc, tutorial/local-causal-cluster.adoc [role=enterprise-edition] [[clustering-deploy]] = Deploy a basic cluster diff --git a/modules/ROOT/pages/database-administration/routing-decisions.adoc b/modules/ROOT/pages/database-administration/routing-decisions.adoc index 62e2c1756..17c45826c 100644 --- a/modules/ROOT/pages/database-administration/routing-decisions.adoc +++ b/modules/ROOT/pages/database-administration/routing-decisions.adoc @@ -2,6 +2,7 @@ [[routing-decisions]] = Query routing decisions :description: This page describes in detail how queries are routed to databases for execution. +:page-aliases: routing-decisions.adoc Query routing is the process of deciding which Cypher executor (database) should be used and at which physical location the query should be executed. Every query that arrives at a Neo4j server, over the bolt protocol from a driver, undergoes the process described here. diff --git a/modules/ROOT/pages/database-internals/transaction-management.adoc b/modules/ROOT/pages/database-internals/transaction-management.adoc index 335129aee..5c43b026b 100644 --- a/modules/ROOT/pages/database-internals/transaction-management.adoc +++ b/modules/ROOT/pages/database-internals/transaction-management.adoc @@ -1,3 +1,5 @@ +:description: How transactions work in Neo4j and how to configure transactional behavior. +:page-aliases: monitoring/transaction-management.adoc [[transaction-management]] = Transaction management diff --git a/modules/ROOT/pages/docker/backup-restore.adoc b/modules/ROOT/pages/docker/backup-restore.adoc index cac28b073..f204b1496 100644 --- a/modules/ROOT/pages/docker/backup-restore.adoc +++ b/modules/ROOT/pages/docker/backup-restore.adoc @@ -1,4 +1,6 @@ :description: Backup and restore operations when running Neo4j in a Docker container. +:page-aliases: docker/maintenance.adoc + [role=enterprise-edition] [[docker-neo4j-backup-restore]] = Back up and restore a Neo4j database (online) diff --git a/modules/ROOT/pages/docker/dump-load.adoc b/modules/ROOT/pages/docker/dump-load.adoc index 2784f82c9..b852b072f 100644 --- a/modules/ROOT/pages/docker/dump-load.adoc +++ b/modules/ROOT/pages/docker/dump-load.adoc @@ -1,4 +1,5 @@ :description: Dump and load operations when running Neo4j in a Docker container. + [[docker-neo4j-dump]] = Dump and load a Neo4j database (offline) diff --git a/modules/ROOT/pages/kubernetes/accessing-neo4j.adoc b/modules/ROOT/pages/kubernetes/accessing-neo4j.adoc index 77fc6daf9..b2a6628ca 100644 --- a/modules/ROOT/pages/kubernetes/accessing-neo4j.adoc +++ b/modules/ROOT/pages/kubernetes/accessing-neo4j.adoc @@ -1,6 +1,7 @@ [[accessing-neo4j]] = Accessing Neo4j :description: How to access Neo4j running in Kubernetes. +:page-aliases: kubernetes/accessing-cluster.adoc A Neo4j running on Kubernetes is accessible via Kubernetes Services. Neo4j has a number of different interfaces for different application and operational purposes. diff --git a/modules/ROOT/pages/procedures.adoc b/modules/ROOT/pages/procedures.adoc index 27966947c..7293eebb9 100644 --- a/modules/ROOT/pages/procedures.adoc +++ b/modules/ROOT/pages/procedures.adoc @@ -4,7 +4,7 @@ :table-caption!: :table-stripes: hover :table-frame: topbot - +:page-aliases: /reference/procedures.adoc :stem: :mathjax-tex-packages: ams diff --git a/modules/ROOT/pages/tools/neo4j-admin/index.adoc b/modules/ROOT/pages/tools/neo4j-admin/index.adoc index 7a12739b5..2bcf30a28 100644 --- a/modules/ROOT/pages/tools/neo4j-admin/index.adoc +++ b/modules/ROOT/pages/tools/neo4j-admin/index.adoc @@ -1,4 +1,5 @@ :description: This section describes commands for managing and administering a Neo4j DBMS. +:page-aliases: tools/cli-commands.adoc, neo4j-admin.adoc [[neo4j-admin]] = Neo4j Admin and Neo4j CLI diff --git a/modules/ROOT/pages/tutorial/access-control.adoc b/modules/ROOT/pages/tutorial/access-control.adoc index 9410ce85b..747378027 100644 --- a/modules/ROOT/pages/tutorial/access-control.adoc +++ b/modules/ROOT/pages/tutorial/access-control.adoc @@ -2,6 +2,7 @@ [[auth-access-control]] = Fine-grained access control (example) :description: Describes an example that illustrates various aspects of security and fine-grained access control. +:page-aliases: authentication-authorization/access-control.adoc When creating a database, administrators may want to establish which users can access certain information.