On Mon, Sep 2, 2019 at 8:39 AM Melroy Rodrigues <[email protected]> wrote:
> It does not tell me the specifics, do I need giuacd and the war to record > session and also what's the war context root so I can get to the war and > see what's inside. > In general you always need both guacd and the WAR file, regardless of whether you are doing session recording or not - guacd runs the translation between the Guacamole protocol and the various remote desktop protocols (SSH, RDP, VNC, etc.), and the WAR file (Guacamole Client) translates between HTTP(S)/WS(S) and the Guacamole Protocol. The WAR context depends on how you deploy the WAR, but there's really not anything you should need to dig into there in order to deal with the recordings. It isn't that you can't dig into it - you're certainly welcome to - you're just not going to gain any additional information relevant to session recordings by doing so. As far recording the sessions, the section on the VNC parameters has the following information: Parameter nameDescription *recording-path* The directory in which screen recording files should be created. *If a graphical recording needs to be created, then this parameter is required.* Specifying this parameter enables graphical screen recording. If this parameter is omitted, no graphical recording will be created. *create-recording-path* If set to "true", the directory specified by the *recording-path* parameter will automatically be created if it does not yet exist. Only the final directory in the path will be created - if other directories earlier in the path do not exist, automatic creation will fail, and an error will be logged. *This parameter is optional.* By default, the directory specified by the *recording-path* parameter will not automatically be created, and attempts to create recordings within a non-existent directory will be logged as errors. This parameter only has an effect if graphical recording is enabled. If the *recording-path* is not specified, graphical session recording will be disabled, and this parameter will be ignored. *recording-name* The filename to use for any created recordings. *This parameter is optional.* If omitted, the value "recording" will be used instead. This parameter only has an effect if graphical recording is enabled. If the *recording-path* is not specified, graphical session recording will be disabled, and this parameter will be ignored. *recording-exclude-output* If set to "true", graphical output and other data normally streamed from server to client will be excluded from the recording, producing a recording which contains only user input events. *This parameter is optional.* If omitted, graphical output will be included in the recording. This parameter only has an effect if graphical recording is enabled. If the *recording-path* is not specified, graphical session recording will be disabled, and this parameter will be ignored. *recording-exclude-mouse* If set to "true", user mouse events will be excluded from the recording, producing a recording which lacks a visible mouse cursor. *This parameter is optional.* If omitted, mouse events will be included in the recording. This parameter only has an effect if graphical recording is enabled. If the *recording-path* is not specified, graphical session recording will be disabled, and this parameter will be ignored. *recording-include-keys* If set to "true", user key events will be included in the recording. The recording can subsequently be passed through the *guaclog* utility to produce a human-readable interpretation of the keys pressed during the session. *This parameter is optional.* If omitted, key events will be not included in the recording. This parameter only has an effect if graphical recording is enabled. If the *recording-path* is not specified, graphical session recording will be disabled, and this parameter will be ignored. The details provided with each of these parameters explains how recording is enabled (by specifying the recording-path parameter) and how these parameters impact the recording - what's recorded, what it's called, where it's stored, etc. The recording is done by guacd, under the user account running guacd, and stored on the system where guacd is running. However, this is done on a per-connection basis with the parameters provided with the connection (see the manual). Again, there's no reason you'd need to get access to or unpack the WAR file in order to handle session recordings. -Nick >
