Update the definition of the authenticatedUser entry (#3099) (#3164)

Author: NataliaIvakina

modules/ROOT/pages/monitoring/logging.adoc

@@ -782,11 +782,11 @@ The following information is available in the JSON format:
 This field is optional and thus will not be populated for all security events.
 
 | executingUser
-| The name of the user triggering the security event.
+| The username of the user triggering the security event.
 Either same as `authenticatedUser` or an impersonated user.
 
 | authenticatedUser
-| The name of the user who authenticated and is connected to the security event.
+| The username of the user who authenticated and is connected to the security event.
 
 | message
 | The log message.
@@ -1301,11 +1301,14 @@ Included when xref:configuration/configuration-settings.adoc#config_db.logs.quer
 | The database name on which the query is run. This field will be `<none>` if the query cannot be parsed and routed to a database.
 
 | executingUser
-| The name of the user executing the query.
+| The username of the user executing the query.
 Either same as `authenticatedUser` or an impersonated user.
 
-| authenticatedUser
-| The name of the user who authenticated and is executing the query.
+| authenticatedUser footnote:[When SSO is enabled, the username is determined by the xref:configuration/configuration-settings.adoc#config_dbms.security.oidc.-provider-.claims.username[`dbms.security.oidc.<provider>.claims.username`] setting.
+If LDAP is configured, Neo4j determines the username string using one of two settings: xref:configuration/configuration-settings.adoc#config_dbms.security.ldap.authentication.user_dn_template[`dbms.security.ldap.authentication.user_dn_template`] or xref:configuration/configuration-settings.adoc#config_dbms.security.ldap.authentication.attribute[`dbms.security.ldap.authentication.attribute`].
+For both OIDC and LDAP, if local user mapping is required (`dbms.security.require_local_user=true`), the log records the mapped local username instead of the external identity string.
+If authentication is controlled on a user level via Cypher statements, the username is defined directly inside the `system` database using native user creation queries: `CREATE USER 'name'`.]
+| The username used to authenticate the session, whether managed natively by Neo4j or externally via an identity provider like LDAP or OIDC/SSO.
 
 | query
 | The query text.