diff --git a/modules/ROOT/pages/authentication-authorization/dbms-administration.adoc b/modules/ROOT/pages/authentication-authorization/dbms-administration.adoc index c0d7206ff..654260ec6 100644 --- a/modules/ROOT/pages/authentication-authorization/dbms-administration.adoc +++ b/modules/ROOT/pages/authentication-authorization/dbms-administration.adoc @@ -97,7 +97,7 @@ This includes the following tasks and their relevant privileges: * Manage xref:authentication-authorization/privileges-reads.adoc[read] and xref:authentication-authorization/privileges-writes.adoc[write] sub-graph privileges. * Manage <>. * Manage <>. -* Manage <>. +* Manage xref:authentication-authorization/load-privileges.adoc[load data security]. To enable a user to perform these tasks, you can grant them the `admin` role, but it is also possible to make a custom role with a subset of these privileges. All privileges are also assignable using Cypher commands. diff --git a/modules/ROOT/pages/authentication-authorization/limitations.adoc b/modules/ROOT/pages/authentication-authorization/limitations.adoc index d9f1881d6..b71036ab3 100644 --- a/modules/ROOT/pages/authentication-authorization/limitations.adoc +++ b/modules/ROOT/pages/authentication-authorization/limitations.adoc @@ -26,10 +26,10 @@ Further to that, Neo4j's role-based access control has some limitations and impl == Security and indexes Neo4j lets you create and use indexes to speed up Cypher queries. -See the link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/[Cypher Manual -> Indexes] for more details on the different types of indexes available in Neo4j. +See the link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/[Cypher Manual -> Indexes] for more details on the different types of indexes available in Neo4j. However, Neo4j’s security model still controls what results you see, regardless of whether or not you use indexes. -For example, when you use link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/overview/[search-performance indexes] (non–full-text) indexes, queries return the same results they would without any index. +For example, when you use link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/search-performance-indexes/[search-performance indexes] (non–full-text) indexes, queries return the same results they would without any index. This means that, if the security model causes fewer results to be returned due to restricted read access in xref:authentication-authorization/manage-privileges.adoc[graph and sub-graph access control], the index will also return the same fewer results. diff --git a/modules/ROOT/pages/changes-deprecations-removals.adoc b/modules/ROOT/pages/changes-deprecations-removals.adoc index a626150de..5bf9107b1 100644 --- a/modules/ROOT/pages/changes-deprecations-removals.adoc +++ b/modules/ROOT/pages/changes-deprecations-removals.adoc @@ -408,7 +408,7 @@ Replaced by xref:procedures.adoc#procedure_dbms_unquarantineDatabase[`dbms.unqua | label:deprecated[Deprecated in 5.26] + label:removed[Removed in Cypher 25] + Replaced by the Cypher command `CREATE VECTOR INDEX`. -For more information, see the link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/semantic-indexes/vector-indexes/#create-vector-index/[Cypher Manual → Create a vector index]. +For more information, see the link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/semantic-indexes/vector-indexes/#create-vector-index[Cypher Manual → Create a vector index]. | xref:procedures.adoc#procedure_dbms_cluster_uncordonServer[`dbms.cluster.uncordonServer()`] diff --git a/modules/ROOT/pages/configuration/neo4j-conf.adoc b/modules/ROOT/pages/configuration/neo4j-conf.adoc index ebf868058..6e4c4844c 100644 --- a/modules/ROOT/pages/configuration/neo4j-conf.adoc +++ b/modules/ROOT/pages/configuration/neo4j-conf.adoc @@ -6,7 +6,7 @@ The _neo4j.conf_ file is the main source of configuration settings in Neo4j and The location of the _neo4j.conf_ file in the different configurations of Neo4j is listed in xref:configuration/file-locations.adoc[Default file locations]. Most of the configuration settings in the _neo4j.conf_ file apply directly to Neo4j itself, but there are also other settings related to the Java Runtime (the JVM) on which Neo4j runs. -For more information, see the xref:configuration/neo4j-conf.adoc#neo4j-conf-JVM[JVM specific configuration settings]. +For more information, see the <>. Many of the configuration settings are also used by `neo4j` launcher scripts. diff --git a/modules/ROOT/pages/database-administration/standard-databases/create-databases.adoc b/modules/ROOT/pages/database-administration/standard-databases/create-databases.adoc index e14406874..f6d371f6c 100644 --- a/modules/ROOT/pages/database-administration/standard-databases/create-databases.adoc +++ b/modules/ROOT/pages/database-administration/standard-databases/create-databases.adoc @@ -137,7 +137,7 @@ Replaced by `existingDataSeedServer`. | URI to a backup or a dump from an existing database. | Defines an identical seed from an external source which will be used to seed all servers. -For more information, see xref::database-administration/standard-databases/seed-from-uri.adoc[Seed from a URI]. +For more information, see xref:database-administration/standard-databases/seed-from-uri.adoc[Create a database from a URI]. | `seedConfig` | Comma-separated list of configuration values. @@ -198,14 +198,14 @@ Defines a seed from an external source, which will be used to seed all servers. | `seedConfig` | Comma-separated list of configuration values. | -For more information see xref::clustering/databases.adoc#cluster-seed-uri[Seed from URI]. +For more information see xref:database-administration/standard-databases/seed-from-uri.adoc[Create a database from a URI]. -| `txLogEnrichment` +| `txLogEnrichment`§ | `FULL` \| `DIFF` \| `OFF` | Defines the level of enrichment applied to transaction logs for Change Data Capture (CDC) purposes. -For details about enrichment mode, see link:{neo4j-docs-base-uri}/cdc/current/get-started/self-managed/#set-enrichment-mode/[Change Data Capture Manual -> Enable CDC on self-managed instances -> Set the enrichment mode]. +For details about enrichment mode, see link:{neo4j-docs-base-uri}/cdc/current/get-started/self-managed/#tweak-mode[Change Data Capture Manual -> Enable CDC on self-managed instances -> Toggle CDC mode]. | `storeFormat` | `aligned` \| `standard` \| `high_limit` \| `block` diff --git a/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc b/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc index 235e988a0..027f57f8c 100644 --- a/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc +++ b/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc @@ -1053,7 +1053,7 @@ To restore the `system` database, follow the steps described in xref:kubernetes/ To migrate from persistent volume-based backups to cloud-native backups, you need to follow these steps: . Perform a final traditional backup to ensure you have the latest data. -For more information, see <> and <>. +For more information, see <> and <<#_back_up_your_databases, Back up your databases>>. . Upload existing backups to the cloud storage bucket if needed. You can use cloud provider CLI tools to transfer your backup files: ** For AWS S3: `aws s3 cp /path/to/backups s3://your-bucket/backups --recursive` @@ -1062,5 +1062,5 @@ You can use cloud provider CLI tools to transfer your backup files: . Update the _backup-values.yaml_ file to configure the cloud provider, bucket name, and credentials. See <> for details. . Install the _neo4j-admin_ Helm chart with the updated _backup-values.yaml_ file to back up your databases to the cloud provider bucket. -See <<_back_up_your_databases, Back up your databases>> for details. +See <<#_back_up_your_databases, Back up your databases>> for details. diff --git a/modules/ROOT/pages/procedures.adoc b/modules/ROOT/pages/procedures.adoc index 9b078fba8..ce2ffc8f1 100644 --- a/modules/ROOT/pages/procedures.adoc +++ b/modules/ROOT/pages/procedures.adoc @@ -829,7 +829,7 @@ For more information, see the link:{neo4j-docs-base-uri}/cypher-manual/current/p ==== As of Neo4j 2025.05, `dbms.components()` returns the supported Cypher versions in a row where the `name` column has the value `"Cypher"`. As of Neo4j 2025.06, the row has the value `["5", "25"]`, indicating that both Cypher 5 and Cypher 25 are supported from this release onward. -For more information about Cypher versions, see the link:{neo4j-docs-base-uri}/cypher-manual/queries/select-version/[Cypher Manual -> Select Cypher version]. +For more information about Cypher versions, see the link:{neo4j-docs-base-uri}/cypher-manual/current/queries/select-version/[Cypher Manual -> Select Cypher version]. ==== [[procedure_dbms_info]] @@ -1140,7 +1140,7 @@ Starting with Neo4j 2025.04, the default database can also be set to a local or | `quarantined` | `BOOLEAN` | Whether or not the database is quarantined. | `result` | `STRING` | Details about the outcome of the procedure. | *Mode* 3+| DBMS -| *Replaced by* 3+| xref:procedures.adoc#procedure_dbms_unquarantineDatabase[`dbms.unquarantineDatabase()`] +| *Replaced by* 3+| <> |=== [NOTE] @@ -1296,7 +1296,7 @@ The types are still enforced as `LIST`. .2+| *Return arguments* | *Name* | *Type* | *Description* | `node` | `NODE` | The node on which the vector property was set. | *Mode* 3+| WRITE -| *Replaced by* 3+| xref:procedures.adoc#procedure_db_create_setNodeVectorProperty[`db.create.setNodeVectorProperty()`] and xref:procedures.adoc#procedure_db_create_setRelationshipVectorProperty[`db.create.setRelationshipVectorProperty()`] +| *Replaced by* 3+| <> and <> |=== .Known issue diff --git a/modules/ROOT/pages/tutorial/tutorial-sso-configuration.adoc b/modules/ROOT/pages/tutorial/tutorial-sso-configuration.adoc index 9e9653458..65e6e4ad5 100644 --- a/modules/ROOT/pages/tutorial/tutorial-sso-configuration.adoc +++ b/modules/ROOT/pages/tutorial/tutorial-sso-configuration.adoc @@ -291,7 +291,7 @@ dbms.security.oidc.azure.config=token_type_principal=id_token;token_type_authent [IMPORTANT] ==== `sub` is the only claim guaranteed to be unique and stable. -For details, see link:https://learn.microsoft.com/en-us/azure/active-directory/develop/id-tokens#using-claims-to-reliably-identify-a-user-subject-and-object-id[Microsoft documentation] as well as the https://openid.net/specs/openid-connect-core-1_0.html#ClaimStability[OpenId spec]. +For details, see link:https://learn.microsoft.com/en-us/azure/active-directory/develop/id-tokens[Microsoft documentation] as well as the https://openid.net/specs/openid-connect-core-1_0.html#ClaimStability[OpenId spec]. ==== + [source, properties]