Search the FirstSpirit Knowledge Base
we detected: the feature 'transactionhistory and revisionsecurity' (of objects within the access.stores.*) does not work for server- & projectconfigurations.
With personalized accounts, you are only able to figure out, who made changes with complicated 'backup' files and DEBUG logs (which is disabled in productive environments by recommendation).
If you do not have a DEBUG loglevel, you have no chance to figure out who changed what.
This may hit and violate compliance & security policies, especially in combination to the 'Admin'- user...
This feature request targets to solve that issue, to make all changes visibile and history-safe in a 'real persistent repository' for ALL configurations, also to the server and its projects
this Feature Request was delivered in FirstSpirit 2018-08:
To ensure that FirstSpirit Servers operate securely and without any problems, audit functions have been added to the logging feature, enabling suspicious activities to be traced and assigned in order to prevent permissions being misused. Audit logging is disabled by default, but can be enabled as required with
little effort. The following activities can be tracked: