Only users with grant
server.securitycan see this section
To understand how Security works, please refer to the Security page.
The configuration of security is stored in the
By using the Enterprise edition the configuration of the security can be changed at runtime, via REST APIs or using the Studio EE extension.
For a detailed documentation of Security config check the new Security Feature page.
To understand how Auditing works, please refer to the Auditing page.
By default all the auditing logs are saved as documents of class
OAuditingLog in the internal database
OSystem. If your account has enough privileges, you can directly query the auditing log. Example on retrieving last 20 logs:
select from OAuditingLog order by @rid desc limit 20.
However, Studio provides a panel to filter the Auditing Log messages on a specific server without using SQL.
Studio Auditing panel helps you also on Auditing configuration of servers, avoiding to edit the
auditing-config.json file under the database folder.