GUACAMOLE-1239: Correct regressions introduced by case sensitive checks for usernames. #1026
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This corrects the regressions introduced by #902 in implementing case-sensitive usernames, correcting the
@Parameter
annotations in a couple of places and moving thecaseSensitive
parameter up to the base mapper class instead of overriding theUserMapper
class. It also moves the warning for the case sensitivity check for MySQL and SQL Server to the Guice module class so that it is only shown once when the module is loaded and not repeatedly for each query (as discussed on the Jira issue).Note that I left the documentation for the
caseSensitive
parameter generic in the base class, and fairly ambiguous - if someone thinks I should put more verbage there around the fact that it currently only applies to usernames, I'm happy to do that, just trying to leave it as generic as possible sense it is in the base class.