Skip to content

Commit a2f126d

Browse files
Fix the path and name of metadata_script.cypher (neo4j#2266)
1 parent 0ba9b1c commit a2f126d

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
@@ -784,7 +784,7 @@ The `'password'` can either be a string value or a string parameter with default
784784
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.
785785
By default, all passwords are encrypted (hashed) when stored in the Neo4j `system` database.
786786
* The optional `PLAINTEXT` in `SET PLAINTEXT PASSWORD` has the same behavior as `SET PASSWORD`.
787-
* 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.
787+
* 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.
788788
See xref:backup-restore/restore-backup#_restore_users_and_roles_metadata[Restore users and roles metadata]. +
789789
With `ENCRYPTED`, the password string is expected to be in the format of `<encryption-version>,<hash>,<salt>`, where, for example:
790790
** `0` is the first version and refers to the `SHA-256` cryptographic hash function with iterations `1`.
@@ -853,7 +853,7 @@ SET AUTH 'native' {SET PASSWORD 'abcd1234' SET PASSWORD CHANGE REQUIRED}
853853

854854
.Create user with an encrypted password
855855
======
856-
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:
856+
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:
857857
858858
[source,cypher,role=noplay]
859859
----
@@ -1012,7 +1012,7 @@ The `'password'` can either be a string value or a string parameter with default
10121012
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.
10131013
By default, all passwords are encrypted (hashed) when stored in the Neo4j `system` database.
10141014
* The optional `PLAINTEXT` in `SET PLAINTEXT PASSWORD` has the same behavior as `SET PASSWORD`.
1015-
* 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.
1015+
* 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.
10161016
See xref:backup-restore/restore-backup#_restore_users_and_roles_metadata[Restore users and roles metadata]. +
10171017
With `ENCRYPTED`, the password string is expected to be in the format of `<encryption-version>,<hash>,<salt>`, where, for example:
10181018
** `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
@@ -296,16 +296,16 @@ For more information, see xref:clustering/databases.adoc#cluster-seed[Designated
296296

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

299-
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:tools/cypher-shell.adoc[Cypher Shell]:
299+
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]:
300300

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

307307
*Using `type` (Windows)*
308308
[source, shell, role=nocopy noplay]
309309
----
310-
type data\scripts\databasename\restore_metadata.cypher | bin\cypher-shell.bat -u user -p password -a ip_address:port -d system --param "database => 'databasename'"
310+
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'"
311311
----

0 commit comments

Comments
 (0)