Symptoms

When a user has special characters in his/her password, like an umlaut (like "?", or "?"), password caching and SSO fails with the attached error (different codepages). The cause seems to be that SAP uses codepage 1100 (ISO-8859-1), but K2 Connect uses codepage 4103 (UTF-16 little endian).
SAP has a logon parameter CODEPAGE, which can be specified in the connection (See https://help.sap.com/saphelp_nwpi71/helpdata/en/45/a2716ae67b2e78e10000000a155369/frameset.htm).
Please let us know what is the correct way to fix this issue. We suppose that we need to add the codepage parameter in the destination configuration, but we want to make sure this is really correct.
 

Diagnoses

The issue has been logged as a bug in 4.6.11 and was associated with the following TFS items:
686519 - SSO/Login special character password issue on different encoding/codepages - CONVERSION_FAILURE
697862 - SSO/Login special character password issue on different encoding/codepages - CONVERSION_FAILURE

A codefix has been created and applied in the customer's environment.
 

Resolution

The codefix (TFS#686519) was applied in the customer's environments and it resolved the issue.