Blanks in user names should be saved in the shiro.ini file as %20

Current Situation

It is currently possible to use the Manage Accounts view to add a User Account with a Name containing a blank space which is then written into the shiro.ini file. This should not happen.

Desired Behaviour

The correct handling of User Account Names with blank spaces depends on the method of Authentication:

• For a User Account that is Authenticated with LDAP, each blank space or series of blank spaces should be replaced with the corresponding number of %20 instances.
  For example:
  • "max muster mann" (with 3 spaces between the words) => "max%20%20%20muster%20%20%20mann"
• For a User Account that is Authenticated with Shiro, the account name should not be allowed. A message such as "User names with blank spaces are not allowed with Shiro authentication" should be shown.

Note that:

• LDAP Users do not require passwords to be specified in the Manage Accounts view. This should be used a criteria to determine whether one or more blank spaces are to be replaced with %20 or whether the Account name is to be disallowed.