Skip to content

Commit c087c8c

Browse files
phil198Hunterness
authored andcommitted
Apply suggestions from code review
Co-authored-by: Therese Magnusson <[email protected]>
1 parent d461462 commit c087c8c

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

modules/ROOT/pages/authentication-authorization/manage-users.adoc

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -800,10 +800,11 @@ With `ENCRYPTED`, the password string is expected to be in the format of `<encry
800800
A home database will be resolved if it is either pointing to a database or a database alias.
801801
If no home database is set, the DBMS default database is used as the home database for the user.
802802
[role=label--new-5.24]
803-
* One or more `SET AUTH` clauses can be used to set xref:authentication-authorization/auth-providers.adoc[Auth Providers], which define authentication / authorization providers for the user. This might be used to configure external auth providers like LDAP or OIDC, but can also be used as an alternative way to set the native (password-based) auth settings like `SET PASSWORD` and `SET PASSWORD CHANGE REQUIRED`.
803+
* One or more `SET AUTH` clauses can be used to set xref:authentication-authorization/auth-providers.adoc[Auth Providers], which define authentication / authorization providers for the user.
804+
This might be used to configure external auth providers like LDAP or OIDC, but can also be used as an alternative way to set the native (password-based) auth settings like `SET PASSWORD` and `SET PASSWORD CHANGE REQUIRED`.
804805
Examples can be found below for `native`, xref:authentication-authorization/sso-integration.adoc#auth-sso-auth-providers[here] for OIDC and xref:authentication-authorization/ldap-integration.adoc#auth-ldap-auth-providers[here] for LDAP.
805806
* It is mandatory to specify at least either a `SET PASSWORD` or a `SET AUTH` clause because users must have at least one Auth Provider.
806-
* The `SET PASSWORD CHANGE [NOT] REQUIRED`, `SET STATUS`, `SET AUTH`, and `SET HOME DATABASE` clauses can be applied in any order.
807+
* The `SET` clauses can be applied in any order.
807808

808809
[NOTE]
809810
====
@@ -866,7 +867,9 @@ SET AUTH 'native' {
866867

867868
[NOTE, role=label--enterprise-edition]
868869
====
869-
The `SET STATUS {ACTIVE | SUSPENDED}`, `SET HOME DATABASE` parts of the commands are only available in Neo4j Enterprise Edition. The `SET AUTH` clause for external providers is only available in Neo4j Enterprise Edition. However, `SET AUTH 'native'` can be used in Neo4j Community Edition.
870+
The `SET STATUS {ACTIVE | SUSPENDED}`, `SET HOME DATABASE` parts of the commands are only available in Neo4j Enterprise Edition.
871+
The `SET AUTH` clause for external providers is only available in Neo4j Enterprise Edition.
872+
However, `SET AUTH 'native'` can be used in Neo4j Community Edition.
870873
====
871874

872875
The `CREATE USER` command is optionally idempotent, with the default behavior to throw an exception if the user already exists.
@@ -1019,7 +1022,7 @@ This results in the DBMS default database being used as the home database for th
10191022
[role=label--new-5.24]
10201023
* `REMOVE AUTH` is used to remove one or many xref:authentication-authorization/auth-providers.adoc[Auth Provider(s)] from a user. It cannot be used in a way that would mean a user has no Auth Providers.
10211024
* `REMOVE ALL AUTH` is used to remove all existing xref:authentication-authorization/auth-providers.adoc[Auth Providers] from a user. It must be used in conjunction with at least one `SET AUTH` clause in order to meet the requirement that a user always has at least one auth provider.
1022-
* The `SET PASSWORD CHANGE [NOT] REQUIRED`, `SET STATUS`, `SET AUTH`, and `SET HOME DATABASE` clauses can be applied in any order, as can their `REMOVE` counterparts where applicable. However, all `REMOVE` clauses must come before the first `SET` clause.
1025+
* All of the `SET` and `REMOVE` clauses can be applied in any order among themselves. However, all `REMOVE` clauses must come before the first `SET` clause.
10231026

10241027

10251028
.Modify the user `bob` with a new password and active status, and remove the requirement to change his password:
@@ -1084,7 +1087,9 @@ For example, leaving out the `CHANGE [NOT] REQUIRED` part of the query will leav
10841087

10851088
[NOTE, role=label--enterprise-edition]
10861089
====
1087-
The `SET STATUS {ACTIVE | SUSPENDED}`, `SET HOME DATABASE`, `REMOVE HOME DATABASE`, and `REMOVE AUTH` parts of the command are only available in Neo4j Enterprise Edition. The `SET AUTH` clause for external providers is only available in Neo4j Enterprise Edition. However, `SET AUTH 'native'` can be used in Neo4j Community Edition.
1090+
The `SET STATUS {ACTIVE | SUSPENDED}`, `SET HOME DATABASE`, `REMOVE HOME DATABASE`, and `REMOVE AUTH` parts of the command are only available in Neo4j Enterprise Edition.
1091+
The `SET AUTH` clause for external providers is only available in Neo4j Enterprise Edition.
1092+
However, `SET AUTH 'native'` can be used in Neo4j Community Edition.
10881093
====
10891094

10901095
The changes to the user will appear on the list provided by `SHOW USERS`:

0 commit comments

Comments
 (0)