User and role management

1. User Management

Users can be created and managed using a set of Cypher administration commands executed against the system database.

When connected to the DBMS over bolt, administration commands are automatically routed to the system database.

Table 1. User management command syntax
Command Description Required privilege Community Edition Enterprise Edition
SHOW USERS
    [YIELD field1[, field2] [ORDER BY field1 [, field2]] [SKIP n] [LIMIT n]]
    [WHERE expression]

List all users.

SHOW USER

+

+

SHOW USER [name] PRIVILEGES

List the privileges granted to a user.

SHOW PRIVILEGE and SHOW USER

-

+

CREATE USER name [IF NOT EXISTS]
  SET PASSWORD password
  [[SET PASSWORD] CHANGE [NOT] REQUIRED]
  [SET STATUS {ACTIVE | SUSPENDED}]

Create a new user.

CREATE USER

+

+

CREATE OR REPLACE USER name
  SET PASSWORD password
  [[SET PASSWORD] CHANGE [NOT] REQUIRED]
  [SET STATUS {ACTIVE | SUSPENDED}]

Create a new user.

CREATE USER and DROP USER

+

+

ALTER USER name SET {
PASSWORD password
            [[SET PASSWORD] CHANGE [NOT] REQUIRED]
            [SET STATUS {ACTIVE | SUSPENDED} ] |
PASSWORD CHANGE [NOT] REQUIRED
            [SET STATUS {ACTIVE | SUSPENDED}] |
STATUS {ACTIVE | SUSPENDED}

Modify the settings for an existing user.

SET PASSWORD and/or SET USER STATUS

+

+

ALTER CURRENT USER SET PASSWORD FROM original TO password

Change the current user’s password.

None

+

+

DROP USER name [IF EXISTS]

Remove an existing user.

DROP USER

+

+

1.1. Listing users

Available users can be seen using SHOW USERS which will produce a table of users with four columns:

Table 2. List users output
Column Description Community Edition Enterprise Edition

user

User name

+

+

roles

Roles granted to the user.

-

+

passwordChangeRequired

If true, the user must change their password at the next login.

+

+

suspended

If true, the user is currently suspended (cannot log in).

-

+

Query
SHOW USERS
Table 3. Result
user roles passwordChangeRequired suspended

"neo4j"

["admin","PUBLIC"]

true

false

1 row

When first starting a Neo4j DBMS, there is always a single default user neo4j with administrative privileges. It is possible to set the initial password using neo4j-admin set-initial-password, otherwise it is necessary to change the password after first login.

The SHOW USER name PRIVILEGES command is described in Listing privileges.

1.2. Creating users

Users can be created using CREATE USER.

Command syntax
CREATE [OR REPLACE] USER name [IF NOT EXISTS]
      SET PASSWORD password
      [[SET PASSWORD] CHANGE [NOT] REQUIRED]
      [SET STATUS {ACTIVE | SUSPENDED}]

If the optional SET PASSWORD CHANGE [NOT] REQUIRED is omitted then the default is CHANGE REQUIRED. The default for SET STATUS is ACTIVE. The password can either be a string value or a string parameter.

For example, we can create the user jake in a suspended state and the requirement to change his password.

Query
CREATE USER jake
SET PASSWORD 'abc' CHANGE REQUIRED
SET STATUS SUSPENDED

0 rows, System updates: 1

The SET STATUS {ACTIVE | SUSPENDED} part of the command is only available in Enterprise Edition.

The created user will appear on the list provided by SHOW USERS.

Query
SHOW USERS YIELD user, suspended, passwordChangeRequired, roles
WHERE user = 'jake'

In this example we also:

  • Reorder the columns using a YIELD clause

  • Filter the results using a WHERE clause to show only the new user

Table 4. Result
user suspended passwordChangeRequired roles

"jake"

true

true

["PUBLIC"]

1 row

In Neo4j Community Edition there are no roles, but all users have implied administrator privileges. In Neo4j Enterprise Edition all users are automatically assigned the PUBLIC role, giving them a base set of privileges.

The CREATE USER command is optionally idempotent, with the default behavior to throw an exception if the user already exists. Appending IF NOT EXISTS to the command will ensure that no exception is thrown and nothing happens should the user already exist. Adding OR REPLACE to the command will result in any existing user being deleted and a new one created.

Query
CREATE USER jake IF NOT EXISTS SET PASSWORD 'xyz'

0 rows

Query
CREATE OR REPLACE USER jake
SET PASSWORD 'xyz'

0 rows, System updates: 2

This is equivalent to running DROP USER jake IF EXISTS followed by CREATE USER jake SET PASSWORD 'xyz'.

The IF NOT EXISTS and OR REPLACE parts of this command cannot be used together.

1.3. Modifying users

Users can be modified using ALTER USER.

Command syntax
ALTER USER name SET {
      PASSWORD password
            [[SET PASSWORD] CHANGE [NOT] REQUIRED]
            [SET STATUS {ACTIVE | SUSPENDED} ] |
      PASSWORD CHANGE [NOT] REQUIRED
            [SET STATUS {ACTIVE | SUSPENDED}] |
      STATUS {ACTIVE | SUSPENDED}
}

The password can either be a string value or a string parameter, and is not allowed to be identical to the old password.

For example, we can modify the user jake with a new password and active status as well as remove the requirement to change his password.

Query
ALTER USER jake
SET PASSWORD 'abc123' CHANGE NOT REQUIRED
SET STATUS ACTIVE

0 rows, System updates: 1

When altering a user it is only necessary to specify the changes required. For example, leaving out the CHANGE [NOT] REQUIRED part of the query will leave that unchanged.

The SET STATUS {ACTIVE | SUSPENDED} part of the command is only available in Enterprise Edition.

The changes to the user will appear on the list provided by SHOW USERS.

Query
SHOW USERS
Table 5. Result
user roles passwordChangeRequired suspended

"jake"

["PUBLIC"]

false

false

"neo4j"

["admin","PUBLIC"]

true

false

2 rows

1.4. Changing the current user’s password

Users can change their own password using ALTER CURRENT USER SET PASSWORD. The old password is required in addition to the new one, and either or both can be a string value or a string parameter. When a user executes this command it will change their password as well as set the CHANGE NOT REQUIRED flag.

Query
ALTER CURRENT USER
SET PASSWORD FROM 'abc123' TO '123xyz'

0 rows, System updates: 1

This command only works for a logged in user and cannot be run with auth disabled.

1.5. Deleting users

Users can be deleted using DROP USER.

Query
DROP USER jake

0 rows, System updates: 1

Deleting a user will not automatically terminate associated connections, sessions, transactions, or queries.

When a user has been deleted, it will no longer appear on the list provided by SHOW USERS.

Query
SHOW USERS
Table 6. Result
user roles passwordChangeRequired suspended

"neo4j"

["admin","PUBLIC"]

true

false

1 row

This command is optionally idempotent, with the default behavior to throw an exception if the user does not exists. Appending IF EXISTS to the command will ensure that no exception is thrown and nothing happens should the user not exist.

Query
DROP USER jake IF EXISTS

0 rows

2. Role Management

Roles can be created and managed using a set of Cypher administration commands executed against the system database.

When connected to the DBMS over bolt, administration commands are automatically routed to the system database.

Table 7. Role management command syntax
Command Description Required privilege
SHOW [ALL|POPULATED] ROLES
    [YIELD field1[, field2] [ORDER BY field1 [, field2]] [SKIP n] [LIMIT n]]
    [WHERE expression]

List roles.

SHOW ROLE

SHOW [ALL|POPULATED] ROLES WITH USERS
    [YIELD field1[, field2] [ORDER BY field1 [, field2]] [SKIP n] [LIMIT n]]
    [WHERE expression]

List roles and users assigned to them.

SHOW ROLE and SHOW USER

SHOW ROLE name PRIVILEGES

List the privileges granted to a role.

SHOW ROLE PRIVILEGES

CREATE ROLE name [IF NOT EXISTS] [AS COPY OF name]

Create a new role.

CREATE ROLE

CREATE OR REPLACE ROLE name [AS COPY OF name]

Create a new role.

CREATE ROLE and DROP ROLE

DROP ROLE name [IF EXISTS]

Remove a role.

DROP ROLE

GRANT ROLE name[, ...] TO user[, ...]

Assign roles to users.

ASSIGN ROLE

2.1. The PUBLIC role

There exists a special built-in role, PUBLIC, which is assigned to all users. This role cannot be dropped or revoked from any user, but its privileges may be modified. By default, it is assigned the ACCESS privilege on the default database.

In contrast to the PUBLIC role, the other built-in roles can be granted, revoked, dropped and re-created.

2.2. Listing roles

Available roles can be seen using SHOW ROLES.

Query
SHOW ROLES

This is the same command as SHOW ALL ROLES. When first starting a Neo4j DBMS there are a number of built-in roles:

  • PUBLIC - a role that all users have granted, by default it gives access to the default database

  • reader - can perform traverse and read operations on all databases except system.

  • editor - can perform traverse, read, and write operations on all databases except system, but cannot make new labels or relationship types.

  • publisher - can do the same as editor, but also create new labels and relationship types.

  • architect - can do the same as publisher as well as create and manage indexes and constraints.

  • admin - can do the same as all the above, as well as manage databases, users, roles, and privileges.

More information about the built-in roles can be found in Operations Manual → Built-in roles

Table 8. Result
role

"PUBLIC"

"admin"

"architect"

"editor"

"publisher"

"reader"

6 rows

There are multiple versions of this command, the default being SHOW ALL ROLES. To only show roles that are assigned to users, the command is SHOW POPULATED ROLES. To see which users are assigned to roles WITH USERS can be appended to the commands. This will give one result row for each user, so if a role is assigned to two users then it will show up twice in the result.

Query
SHOW POPULATED ROLES
WITH USERS

The table of results will show information about the role and what database it belongs to.

Table 9. Result
role member

"PUBLIC"

"neo4j"

"PUBLIC"

"jake"

"PUBLIC"

"user1"

"PUBLIC"

"user2"

"PUBLIC"

"user3"

"admin"

"neo4j"

6 rows

It is also possible to filter and sort the results by using YIELD, ORDER BY and WHERE.

Query
SHOW ROLES YIELD role
ORDER BY role
WHERE role ENDS WITH 'r'

In this example:

  • The results have been filtered to only return the roles ending in 'r'.

  • The results are ordered by the 'action' column using ORDER BY.

It is also possible to use SKIP and LIMIT to paginate the results.

Table 10. Result
role

"editor"

"publisher"

"reader"

3 rows

The SHOW ROLE name PRIVILEGES command is found in Listing privileges.

2.3. Creating roles

Roles can be created using CREATE ROLE.

Query
CREATE ROLE myrole

0 rows, System updates: 1

A role can also be copied, keeping its privileges, using CREATE ROLE AS COPY OF.

Query
CREATE ROLE mysecondrole AS COPY OF myrole

0 rows, System updates: 1

The created roles will appear on the list provided by SHOW ROLES.

Query
SHOW ROLES
Table 11. Result
role

"PUBLIC"

"admin"

"architect"

"editor"

"myrole"

"mysecondrole"

"publisher"

"reader"

8 rows

These command versions are optionally idempotent, with the default behavior to throw an exception if the role already exists. Appending IF NOT EXISTS to the command will ensure that no exception is thrown and nothing happens should the role already exist. Adding OR REPLACE to the command will result in any existing role being deleted and a new one created.

Query
CREATE ROLE myrole IF NOT EXISTS

0 rows

Query
CREATE OR REPLACE ROLE myrole

0 rows, System updates: 2

This is equivalent to running DROP ROLE myrole IF EXISTS followed by CREATE ROLE myrole.

The IF NOT EXISTS and OR REPLACE parts of this command cannot be used together.

2.4. Deleting roles

Roles can be deleted using DROP ROLE command.

Query
DROP ROLE mysecondrole

0 rows, System updates: 1

When a role has been deleted, it will no longer appear on the list provided by SHOW ROLES.

Query
SHOW ROLES
Table 12. Result
role

"PUBLIC"

"admin"

"architect"

"editor"

"publisher"

"reader"

6 rows

This command is optionally idempotent, with the default behavior to throw an exception if the role does not exists. Appending IF EXISTS to the command will ensure that no exception is thrown and nothing happens should the role not exist.

Query
DROP ROLE mysecondrole IF EXISTS

0 rows

2.5. Assigning roles to users

Users can be given access rights by assigning them roles using GRANT ROLE.

Query
GRANT ROLE myrole TO jake

0 rows, System updates: 1

The roles assigned to each user can be seen in the list provided by SHOW USERS.

Query
SHOW USERS
Table 13. Result
user roles passwordChangeRequired suspended

"jake"

["myrole","PUBLIC"]

false

false

"neo4j"

["admin","PUBLIC"]

true

false

"user1"

["PUBLIC"]

true

false

"user2"

["PUBLIC"]

true

false

"user3"

["PUBLIC"]

true

false

5 rows

It is possible to assign multiple roles to multiple users in one command.

Query
GRANT ROLES role1, role2 TO user1, user2, user3

0 rows, System updates: 6

Query
SHOW USERS
Table 14. Result
user roles passwordChangeRequired suspended

"jake"

["myrole","PUBLIC"]

false

false

"neo4j"

["admin","PUBLIC"]

true

false

"user1"

["role1","role2","PUBLIC"]

true

false

"user2"

["role1","role2","PUBLIC"]

true

false

"user3"

["role1","role2","PUBLIC"]

true

false

5 rows

2.6. Revoking roles from users

Users can lose access rights by revoking roles from them using REVOKE ROLE.

Query
REVOKE ROLE myrole FROM jake

0 rows, System updates: 1

The roles revoked from users can no longer be seen in the list provided by SHOW USERS.

Query
SHOW USERS
Table 15. Result
user roles passwordChangeRequired suspended

"jake"

["PUBLIC"]

false

false

"neo4j"

["admin","PUBLIC"]

true

false

"user1"

["role1","role2","PUBLIC"]

true

false

"user2"

["role1","role2","PUBLIC"]

true

false

"user3"

["role1","role2","PUBLIC"]

true

false

5 rows

It is possible to revoke multiple roles from multiple users in one command.

Query
REVOKE ROLES role1, role2 FROM user1, user2, user3

0 rows, System updates: 6