Skip to content

Commit fb2e918

Browse files
Fix the path and name of the metadata_script.cypher (neo4j#2266)
1 parent b659df3 commit fb2e918

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

modules/ROOT/pages/authentication-authorization/manage-users.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -782,7 +782,7 @@ The `'password'` can either be a string value or a string parameter with default
782782
The `PLAINTEXT` and `ENCRYPTED` keywords are optional and can be used to specify the format of the password, i.e. whether Neo4j needs to hash it or it has already been hashed.
783783
By default, all passwords are encrypted (hashed) when stored in the Neo4j `system` database.
784784
* The optional `PLAINTEXT` in `SET PLAINTEXT PASSWORD` has the same behavior as `SET PASSWORD`.
785-
* The optional `ENCRYPTED` is used to recreate an existing user when the plaintext password is unknown, but the encrypted password is available in the _data/scripts/databasename/restore_metadata.cypher_ file of a database backup.
785+
* The optional `ENCRYPTED` is used to recreate an existing user when the plaintext password is unknown, but the encrypted password is available in the _data/databases/databasename/tools/metadata_script.cypher_ file of a database backup.
786786
See xref:backup-restore/restore-backup#_restore_users_and_roles_metadata[Restore users and roles metadata]. +
787787
With `ENCRYPTED`, the password string is expected to be in the format of `<encryption-version>,<hash>,<salt>`, where, for example:
788788
** `0` is the first version and refers to the `SHA-256` cryptographic hash function with iterations `1`.
@@ -850,7 +850,7 @@ SET AUTH 'native' {SET PASSWORD 'abcd1234' SET PASSWORD CHANGE REQUIRED}
850850

851851
.Create user with an encrypted password
852852
======
853-
Or you can create the user `Jake` in an active state, with an encrypted password (taken from the _data/scripts/databasename/restore_metadata.cypher_ of a database backup), and the requirement to not change the password by running:
853+
Or you can create the user `Jake` in an active state, with an encrypted password (taken from the _data/databases/databasename/tools/metadata_script.cypher_ of a database backup), and the requirement to not change the password by running:
854854
855855
[source,cypher,role=noplay]
856856
----
@@ -1006,7 +1006,7 @@ The `'password'` can either be a string value or a string parameter with default
10061006
The `PLAINTEXT` and `ENCRYPTED` keywords are optional and can be used to specify the format of the password, i.e. whether Neo4j needs to hash it or it has already been hashed.
10071007
By default, all passwords are encrypted (hashed) when stored in the Neo4j `system` database.
10081008
* The optional `PLAINTEXT` in `SET PLAINTEXT PASSWORD` has the same behavior as `SET PASSWORD`.
1009-
* The optional `ENCRYPTED` is used to recreate an existing user when the plaintext password is unknown, but the encrypted password is available in the _data/scripts/databasename/restore_metadata.cypher_ file of a database backup.
1009+
* The optional `ENCRYPTED` is used to recreate an existing user when the plaintext password is unknown, but the encrypted password is available in the _data/databases/databasename/tools/metadata_script.cypher_ file of a database backup.
10101010
See xref:backup-restore/restore-backup#_restore_users_and_roles_metadata[Restore users and roles metadata]. +
10111011
With `ENCRYPTED`, the password string is expected to be in the format of `<encryption-version>,<hash>,<salt>`, where, for example:
10121012
** `0` is the first version and refers to the `SHA-256` cryptographic hash function with iterations `1`.

modules/ROOT/pages/backup-restore/restore-backup.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -299,16 +299,16 @@ For more information, see xref:clustering/databases.adoc#cluster-seed[Designated
299299

300300
If you have backed up a database with the option `--include-metadata`, you can manually restore the users and roles metadata.
301301

302-
From the _<NEO4J_HOME>_ directory, you run the Cypher script _data/scripts/databasename/restore_metadata.cypher_, which the `neo4j-admin database restore` command outputs, using xref:cypher-shell.adoc[][Cypher Shell]:
302+
From the _<NEO4J_HOME>_ directory, you run the Cypher script _data/databases/databasename/tools/metadata_script.cypher_, which the `neo4j-admin database restore` command outputs, using xref:cypher-shell.adoc[][Cypher Shell]:
303303

304304
*Using `cat` (UNIX)*
305305
[source, shell, role=nocopy noplay]
306306
----
307-
cat data/scripts/databasename/restore_metadata.cypher | bin/cypher-shell -u user -p password -a ip_address:port -d system --param "database => 'databasename'"
307+
cat data/databases/databasename/tools/metadata_script.cypher | bin/cypher-shell -u user -p password -a ip_address:port -d system --param "database => 'databasename'"
308308
----
309309

310310
*Using `type` (Windows)*
311311
[source, shell, role=nocopy noplay]
312312
----
313-
type data\scripts\databasename\restore_metadata.cypher | bin\cypher-shell.bat -u user -p password -a ip_address:port -d system --param "database => 'databasename'"
313+
type data\databases\databasename\tools\metadata_script.cypher | bin\cypher-shell.bat -u user -p password -a ip_address:port -d system --param "database => 'databasename'"
314314
----

0 commit comments

Comments
 (0)