Critical. LDAP cannot read non-English characters after upgrade to Xanadu Patch 7Issue After upgrading to Xanadu Patch 7, MID Server integrations (LDAP, REST, etc.) fail to correctly interpret non-English characters. This issue affects all integrations processed through MID Servers that previously functioned correctly without any additional encoding configuration.SymptomsNon-English characters (e.g., special or accented letters) appear corrupted or incorrectly encoded.Issues occur specifically after applying Xanadu Patch 7.Issue impacts all MID Server-based integrations uniformly.Direct REST API calls without MID Server involvement process encoding correctly, demonstrating issue specificity to MID Server processing. Example Symptom: The LDAP import from Active Directory displays correct encoding before applying Patch 7 and incorrect encoding after applying the patch (e.g., corrupted given names, surnames, etc.).FactsIssue started post-upgrade to ServiceNow Xanadu Patch 7.MID Servers inherit default Java encoding from the underlying OS unless explicitly configured.Prior to Patch 7, MID Servers operated correctly without explicit JVM encoding settings.After Patch 7, an explicit encoding configuration (-Dfile.encoding=UTF-8) is required as a workaround for integrations to function correctly.ReleaseServiceNow Xanadu Patch 7Release Notes: Xanadu Patch 7 Release Notes https://www.servicenow.com/docs/bundle/xanadu-release-notes/page/release-notes/quality/xanadu-patch-7.htmlCauseXanadu Patch 7 introduced changes to internal MID Server parser and character encoding handling.MID Servers are now unable to process non-English characters correctly without explicitly specifying Java wrapper encoding settings.Root cause linked to underlying Java and parser changes in MID Server processing introduced by Patch 7 (reference PRB1840424 and related KB1772428 for background context).ResolutionCurrently, the official recommended workaround is to explicitly enforce UTF-8 encoding in the MID Server's Java wrapper configuration as per KB0952420: Steps: Stop the affected MID Server service.Edit the MID Server configuration file (wrapper-override.conf) located at:<MID_Server_Home>/conf/wrapper-override.confAdd the following line explicitly:wrapper.java.additional.<N>=-Dfile.encoding=UTF-8Replace <N> with the next available wrapper parameter number.Restart the MID Server service. Note: Ensure thorough testing post-implementation to confirm issue resolution. Permanent Fix & Documentation Update (Planned) The ServiceNow development and documentation teams are aware and actively reviewing this issue for a permanent fix.A dedicated PRB (Problem Record) and Known Error Article are pending release to track and address this encoding handling change.Official documentation will reflect this mandatory JVM setting in future releases (Zurich or later Xanadu patches)Related LinksKB0952420 (Workaround Reference): KB0952420KB1772428 (Background Reference): KB1772428Release Notes Xanadu Patch 7: Xanadu Patch 7 Release Notes