The OpenIDM custom authentication headers are unable to correctly handled unicode characters within either the username or password. This applies to authentication against the OpenIDM repository and via pass-through authentication.
This limitation is imposed by the restriction on HTTP header values only being allowed to contain ASCII characters and a lack of a well defined and widely supported escaping mechanism. Note that it is possible to use extended ASCII character codes (<256) via escaping as follows:
British Pound = '/xa3'
Although BasicAuth does work in certain circumstances (see
OPENIDM-1463) browsers do not reliably support unicode characters within BasicAuth headers and therefore this workaround is not a reliable solution.
See the following related to the topic: