You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/authentication-authorization/sso-integration.adoc
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,20 +166,20 @@ The simplest approach is to create identity provider groups with the same names
166
166
If you decide to go this way, no mapping configuration is necessary.
167
167
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.
168
168
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`.
171
171
172
172
.Example of identity provider groups to Neo4j roles mapping
0 commit comments