Database users
Database users are managed by Neo4j and need to be updated by you via Cypher from your application or from GDB Explorer. When using Read-Replicas any change to a database user will automatically propagate to all Replica nodes.
Creating a first user
Upon database creation, Neo4j will create a user with a temporary password. The default user and password are neo4j/neo4j. When you first launch GDB Explorer, please enter the neo4j user and temporary neo4j password.
You’ll be prompted to the next window where you’ll need to change the temporary password. When changing the password, please make sure you choose a secure password and store it safely.
If the password can no longer be retrieved or is lost, the authentication can be disabled like this, and then you can change users password, create new user, or whatever you decide is the best course of action.
Managing users
You can manage database users in two ways: by running Cypher administration commands yourself, or through GDB Explorer’s Database User management view, which lets you create, edit and delete users without writing any Cypher.
If you’d rather use Cypher, refer to the Neo4j documentation for the commands matching your database version.
Read-only users
We offer a feature called Read-only users, allowing you to reduce the risk of accidental modifications to the database by limiting user access to read-only operations. Additionally, it allows you to minimize the potential impact of user errors or system malfunctions on critical data.
To locate this info, navigate to the Connect tab of your database management view.
If you prepend “RO_” to your username it will automatically have only read privileges. All writes performed by the user will fail automatically. To create a read-only user or to change an existing one, update the username via Cypher from your application, or rename it using GDB Explorer’s Database User management view.
After this setting is changed, please make sure to login again with the RO_xxx user.