JOC Cockpit should support diacritics, e.g. Umlauts, in passwords

Current Situation

• When adding/modifying a local user account with JOC Cockpit and specifying a password that includes diacritical characters such as Umlauts, then the user cannot authenticate with JOC Cockpit.
• The same problem occurs with LDAP managed accounts that are stored in an Active Directory.
• The root cause for this behavior is a wrong authorization header that is sent by JOC during the login. The authorization header must be encoded with UTF-8 but is ISO-8859-1.
  • Example: The user test with the password ä is encoded to dGVzdDrk but must be encoded to dGVzdDrDpA==

Desired Behavior

• Diacritical characters should be supported with passwords.
• The authorization header should be encoded with UTF-8