Skip to content

Update steps on how to recover pswd (#1802) #1837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 27, 2024
Merged

Update steps on how to recover pswd (#1802) #1837

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 9 additions & 16 deletions modules/ROOT/pages/authentication-authorization/password-and-user-recovery.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,28 +25,20 @@ bin/neo4j stop
----
dbms.security.auth_enabled=false
----
+
[NOTE]
====
It is recommended to block network connections during the recovery phase, so users can connect to Neo4j only via `localhost`.
This can be achieved by either:

* Temporarily commenting out the `server.default_listen_address` parameter:
+
[source, properties]
----
#server.default_listen_address=<your_configuration>
----

or

* Providing the specific localhost value:
. Block network connections during the recovery phase, so users can connect to Neo4j only via `localhost`.
This can be achieved by temporarily commenting out the `server.default_listen_address` parameter and providing the specific localhost value:
+
[source, properties]
----
server.default_listen_address=127.0.0.1
----
+
[NOTE]
====
Ensure, you have blocked all network connections for any individual services configured to listen to `listen_addresses`.
====
+
. Start Neo4j:
+
[source, shell]
Expand All @@ -72,11 +64,12 @@ dbms.security.auth_enabled=false
----
+
.. Disable the HTTP and HTTPS network connections and restrict the `bolt` connector to use only `localhost`.
Set `server.http.enabled` to `false`.
This ensures that no one from outside can access the cluster during the recovery period.
+
[source, properties]
----
#server.http.enabled=true
server.http.enabled=false
#server.https.enabled=true
server.bolt.listen_address:127.0.0.1
----
Expand Down