Skip to content

Commit

Permalink
update instructions on how to recover admin user and password in a cl… (
Browse files Browse the repository at this point in the history
#1298)

…uster
  • Loading branch information
AlexicaWright authored Jan 3, 2024
1 parent 6f7a47f commit d4c6e34
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 14 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -57,14 +57,14 @@ $ bin/neo4j start
======
[.include-with-cluster]
======
. Stop the cluster (all Core servers and Read Replicas).
. Stop all members of the cluster:
+
[source, shell]
----
$ bin/neo4j stop
----
+
. On each Core server, open the _neo4j.conf_ file and modify the following settings:
. On each member, open the _neo4j.conf_ file and modify the following settings:
.. Set `dbms.security.auth_enabled` parameter to `false` to disable the authentication:
+
[source, properties]
Expand All @@ -82,7 +82,7 @@ This ensures that no one from outside can access the cluster during the recovery
server.bolt.listen_address:127.0.0.1
----
+
. Start all Core servers:
. Start all members of the cluster:
+
[source, shell]
----
Expand All @@ -98,7 +98,7 @@ You can use a client such as xref:tools/cypher-shell.adoc[Cypher Shell] or the N

[NOTE]
====
In a cluster deployment, you should complete the steps only on one of the Core servers.
In a cluster deployment, you should complete the steps only on one of the cluster members.
====

. Complete the steps in xref:authentication-authorization/password-and-user-recovery.adoc#disable-authentication[Disable authentication] as per your deployment.
Expand All @@ -112,7 +112,7 @@ $ bin/cypher-shell -d system
+
[NOTE]
====
label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-core>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your Core server.
label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-cluster-member>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your cluster member.
====
. Set a new password for the admin user.
In this example, the admin user is named `neo4j`.
Expand All @@ -136,7 +136,7 @@ You can use a client such as xref:tools/cypher-shell.adoc[Cypher Shell] or the N

[NOTE]
====
In a cluster deployment, you should complete the steps only on one of the Core servers.
In a cluster deployment, you should complete the steps only on one of the cluster members.
====

. Complete the steps in xref:authentication-authorization/password-and-user-recovery.adoc#disable-authentication[Disable authentication] as per your deployment.
Expand All @@ -150,7 +150,7 @@ $ bin/cypher-shell -d system
+
[NOTE]
====
label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-core>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your Core server.
label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-cluster-member>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your cluster member.
====
. Grant the admin user role to an existing user.
In this example, the user is named `neo4j`.
Expand All @@ -174,7 +174,7 @@ If you have removed the admin role from your system entirely, you can use a clie

[NOTE]
====
In a cluster deployment, you should complete the steps only on one of the Core servers.
In a cluster deployment, you should complete the steps only on one of the cluster members.
====

. Complete the steps in xref:authentication-authorization/password-and-user-recovery.adoc#disable-authentication[Disable authentication] as per your deployment.
Expand All @@ -188,7 +188,7 @@ $ bin/cypher-shell -d system
+
[NOTE]
====
label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-core>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your Core server.
label:Cluster[] If you have specified a non-default port for your `bolt` connector, add `-a neo4j://<your-cluster-member>:<non-default-bolt-port>` to the `cypher-shell` command to be able to connect to your cluster member.
====
. Recreate the admin role with its original capabilities.
+
Expand Down Expand Up @@ -244,15 +244,15 @@ $ bin/neo4j start
======
[.include-with-cluster]
======
. Stop the Core servers.
. Stop the cluster members.
+
[source, shell]
----
$ bin/neo4j stop
----
+
. Enable the authentication and restore each Core server to its original configuration (See xref:configuration/password-and-user-recovery.adoc#disable-authentication[Disable authentication]).
. Start the cluster (all Core servers and Read Replicas):
. Enable the authentication and restore each cluster member to its original configuration (See xref:configuration/password-and-user-recovery.adoc#disable-authentication[Disable authentication]).
. Start the cluster (all cluster members):
+
[source, shell]
----
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit d4c6e34

Please sign in to comment.