Skip to content

Commit 9f5cd53

Browse files
Fix group to role mapping section (#1699) (#1707)
Related to: neo-technology/neo4j#26072 Cherry-picked from #1699 Co-authored-by: Lasse Heemann <lasse.heemann@neo4j.com>
1 parent 80f59a3 commit 9f5cd53

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -166,20 +166,20 @@ The simplest approach is to create identity provider groups with the same names
166166
If you decide to go this way, no mapping configuration is necessary.
167167
Assuming, however, that identity provider groups do not directly map 1:1 to the desired Neo4j roles, it is necessary to map the identity provider groups to the xref:authentication-authorization/built-in-roles.adoc[Neo4j built-in] and custom-defined roles.
168168
To do that, you need to know what privileges the Neo4j roles have, and based on these privileges, create the mapping to the groups defined in the identity provider.
169-
The map must be formatted as a semicolon-separated list of key-value pairs, where the key is a comma-separated list of the identity provider group names and the value is a comma-separated list of the corresponding role names.
170-
For example, `group1=role1;group2=role2;group3=role3,role4,role5;group4,group5=role6`.
169+
The map must be formatted as a semicolon-separated list of key-value pairs, where the key is the identity provider group name and the value is a comma-separated list of the corresponding role names.
170+
For example, `group1=role1;group2=role2;group3=role3,role4,role5;group4=role6;group5=role6`.
171171

172172
.Example of identity provider groups to Neo4j roles mapping
173173
====
174174
[source, role=noheader]
175175
----
176176
dbms.security.oidc.mysso.authorization.group_to_role_mapping=\
177-
neo4j_readonly = reader; \ #<1>
178-
neo4j_rw = editor,publisher; \ #<2>
179-
neo4j_rw,neo4j_create = publisher; \ #<3>
180-
neo4j_create,neo4j_schema = architect; \
181-
neo4j_dba = admin; \
182-
neo4j_exec = rolename #<4>
177+
neo4j_readonly = reader; \ #<1>
178+
neo4j_rw = editor,publisher; \ #<2>
179+
neo4j_rw = publisher; \ #<3>
180+
neo4j_create = publisher; \
181+
neo4j_dba = admin; \
182+
neo4j_exec = rolename #<4>
183183
----
184184
185185
<1> Mapping of an identity provider group to a Neo4j built-in role.

0 commit comments

Comments
 (0)