Update modules/ROOT/pages/tutorial/tutorial-sso-configuration.adoc

renetapopova · phil198 · web-flow · commit 9ffa1391e444 · 2024-09-24T10:21:42.000+01:00
Co-authored-by: Phil Wright &lt;95368282+phil198@users.noreply.github.com&gt;
diff --git a/modules/ROOT/pages/tutorial/tutorial-sso-configuration.adoc b/modules/ROOT/pages/tutorial/tutorial-sso-configuration.adoc
@@ -137,7 +137,7 @@ dbms.security.oidc.okta.config=token_type_principal=id_token;token_type_authenti
 image::sso-configuration-tutorials/okta-sign-on-tab.svg[title="Okta's sign-on tab"]
 +
 . label:new[Introduced in 5.24] (Optional) If you want control the authentication and authorization on a user level, configure xref:configuration/configuration-settings.adoc#config_dbms.security.require_local_user[`dbms.security.require_local_user`] to `true` in the _neo4j.conf_ file.
-This setting mandates that users representing the corresponding auth provider must exist in the database before they can authenticate and authorize.
+This setting mandates that users with the relevant auth provider attached to them must exist in the database before they can authenticate and authorize with that auth provider.
 For information on how to create users in this mode, see xref:authentication-authorization/manage-users.adoc#access-control-create-users[Creating users].
 +
 For example, to create the user `jake` who can authenticate using `native` or `okta`, and authorize using Okta (as configured in step 3), you can use the following Cypher query:

Original file line number	Diff line number	Diff line change
`@@ -137,7 +137,7 @@ dbms.security.oidc.okta.config=token_type_principal=id_token;token_type_authenti`
`137`	`137`	`image::sso-configuration-tutorials/okta-sign-on-tab.svg[title="Okta's sign-on tab"]`
`138`	`138`	`+`
`139`	`139`	. label:new[Introduced in 5.24] (Optional) If you want control the authentication and authorization on a user level, configure xref:configuration/configuration-settings.adoc#config_dbms.security.require_local_user[`dbms.security.require_local_user`] to `true` in the _neo4j.conf_ file.
`140`		`-This setting mandates that users representing the corresponding auth provider must exist in the database before they can authenticate and authorize.`
	`140`	`+This setting mandates that users with the relevant auth provider attached to them must exist in the database before they can authenticate and authorize with that auth provider.`
`141`	`141`	`For information on how to create users in this mode, see xref:authentication-authorization/manage-users.adoc#access-control-create-users[Creating users].`
`142`	`142`	`+`
`143`	`143`	For example, to create the user `jake` who can authenticate using `native` or `okta`, and authorize using Okta (as configured in step 3), you can use the following Cypher query: