Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 5326 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Special characters in password do not work with proxy basic user authentication

Markus S.
Hi,

I recognized that users which use special characters in there password like latin letters with diaresis and latin letter sharp s ( ä,ö,ü and ß ) are unable to authenticate against the proxy.

Now it seems that also the section sign ( § ) could not be used in a password.

Is there a way to configure authentication for all utf-8 characters?

Markus


This thread was automatically locked due to age.
  • 0
    I would not be surprised if all unicode and unusual characters are not allowed.  This is not a fault of the UTM, it is because Basic authentication is....  welll, basic.

    A quick search shows things like:
    ruby on rails - UTF-8 characters mangled in HTTP Basic Auth username - Stack Overflow
    Which includes this tidbit
    "Abandon all hope. Basic Authentication and Unicode don't mix.
    There is no standard(*) for how to encode non-ASCII characters into a Basic Authentication username[:P]assword token before base64ing it. Consequently every browser does something different"

    Please note that Basic Authentication sends usernames and passwords in cleartext.  It is NOT secure and is not recommended if security is a concern.

    AD SSO (which uses NTLM) supports all username/passwords characters that Windows supports.
Unfiltered HTML