Following files had unnessery trailing whitespaces.
guacamole/src/main/webapp/translations/ca.json
guacamole/src/main/webapp/translations/en.json
guacamole/src/main/webapp/translations/pt.json
guacamole/src/main/webapp/translations/zh.json
If the protocol name and parameters are retrieved from Connection-
specific endpoints, then the protocol-specific context needed for
Guacamole instructions like "argv" and "required" will only be
available for Connections (not ConnectionGroups or ActiveConnections).
Add translation files for the webapp and the following extensions:
- guacamole-auth-cas
- guacamole-auth-duo
- guacamole-auth-jdbc
- guacamole-auth-openid
- guacamole-auth-quickconnect
- guacamole-auth-saml
- guacamole-auth-totp
The modifications add translation file for the webapp and the following extensions:
- guacamole-auth-cas
- guacamole-auth-duo
- guacamole-auth-jdbc
- guacamole-auth-openid
- guacamole-auth-quickconnect
- guacamole-auth-radius
- guacamole-auth-saml
- guacamole-auth-totp
Modify the guac-manifest file of the different translated extensions and place translations in alphabetical order
If expected fields are deleted rather than reset to empty, those fields
will not be resubmitted in future requests, resulting in the content of
those requests not accurately representing true client-side login state.
For example, if a user receives an insufficient credentials error due to
their password expiring, failing to provide any new password should
result in at least the following fields:
1. Their original username (part of the initial login attempt)
2. Their original password (part of the initial login attempt)
3. Their new password (empty)
If fields are incorrectly reset to null, those fields will not be
submitted, resulting instead in a request containing only:
1. Their original username (part of the initial login attempt)
2. Their original password (part of the initial login attempt)
which is indistinguishable from a normal login attempt.
By definition, a client error is not an internal error, but an
intentional refusal of the server to handle a malformed or otherwise
invalid request. These should not be handled in the same way as server
errors which unexpectedly block processing of a request and should be
corrected by an administrator.
In the case of GUACAMOLE-1152, client errors should not be ignored even
if failures are explicitly configured as tolerated for the associated
authentication provider.
