Skip to content

Commit 2470667

Browse files
Fix group-role mapping for LDAP integration (#2329) (#2338)
Co-authored-by: Olivia Ytterbrink <[email protected]>
1 parent 31e3aa4 commit 2470667

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

modules/ROOT/pages/authentication-authorization/ldap-integration.adoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -108,8 +108,9 @@ dbms.security.authorization_providers=ldap,native
108108

109109
To access the user and role management procedures, you have to map the LDAP groups to the xref:authentication-authorization/built-in-roles.adoc[Neo4j built-in] and custom-defined roles.
110110
To do that, you need to know what privileges the Neo4j roles have, and based on these privileges, to create the mapping to the groups defined in the LDAP server.
111-
The map must be formatted as a semicolon separated list of key-value pairs, where the key is a comma-separated list of the LDAP group names and the value is a comma-separated list of the corresponding role names.
112-
For example, `group1=role1;group2=role2;group3=role3,role4,role5;group4,group5=role6`.
111+
The map must be formatted as a semicolon separated list of key-value pairs, where the key is a LDAP group name and the value is a comma-separated list of the corresponding role names.
112+
113+
For example, `group1=role1;group2=role2;group3=role3,role4,role5;group4=role6;group5=role6`.
113114

114115
.Example of LDAP groups to Neo4j roles mapping
115116
====

0 commit comments

Comments
 (0)