Wallix, when the parameter is not set.
In previous commit, when parameter wallix-user-password was not provided
in configuration file, the password used to authenticated to Guacamole
would automatically be used for connection to Wallix. This commit change
this behavior and for now, the password will be prompted if the
parameter is not set. If automatic login is needed, the value
${GUAC_PASSWORD} must be set manually.
This commit add 2 new parameters wallix-user-password and
wallix-username-suffix, to allow formatting credentials before sending
them to Wallix in order to automate authentication. Now when a
connection is opened, the following crendentials will be used :
Username : <wallix-username-prefix>+<wallix-username-suffix>
Password : <wallix-user-password>
If wallix-username-suffix is not provided, the value ${GUAC_USERNAME} ,
which represent the username provided while login in to Guacamole will
be used. If wallix-user-password is not set, password will be asked
during connection otherwise, the provided password will be used for all
connections. Guacamole tokens can be used as value, so if you set this
parameter to ${GUAC_PASSWORD}, the password used to authenticate with
Guacamole will be used to connect to Wallix and allow automatic
authentication if both share the same authentication source.
Previous commit did not recognized users modification reliably and
synchronization was skipped. This commit fix this situation and make
sure that users modification in Wallix are reliably detected.
In order to make sure entities of same type, having the same name are
equals, these two methods have been override to make sure that Sets
contains only one object with a specific name.
