[
https://issues.apache.org/jira/browse/GUACAMOLE-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715108#comment-17715108
]
Mike Jumper commented on GUACAMOLE-1224:
----------------------------------------
As discussed at
https://github.com/apache/guacamole-client/pull/840#discussion_r1174010688, the
changes as currently implemented should be modified such that {{UPDATE}},
{{REMOVE}}, etc. failure events are fired _in addition to_ {{GET}} so that logs
can have proper context. They currently will log only the {{GET}} attempt if an
update/remove cannot be performed due to the object not existing.
> Provide audit log for system modifications
> ------------------------------------------
>
> Key: GUACAMOLE-1224
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1224
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-client
> Reporter: leo las
> Assignee: Mike Jumper
> Priority: Minor
>
> Guacamole Client could potentially log system modification events, including:
> * User administration (create, delete, update, and password events)
> * Connection administration (create, delete, update)
> These events could at least be logged into Tomcat somewhere, or potentially
> tracked within a separate table in the database.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
