Operational Defect Database
BugZero found this defect 563 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA16S000000WOqpSAG
Cannot connect to an IPSec VPN with credentials that include non-ASCII characters
Last update date:
11/3/2022
Affected products:
No affected products provided.
Affected releases:
Any/Unknown
Fixed releases:
All
Description:
Issue
Mobile VPN with IPSec users cannot connect to the VPN with Active Directory user names or passwords that include certain non-ASCII characters. The Firebox supports non-ASCII characters. This issue relates to character support in other software included in your VPN design: The IPSec Mobile VPN Client, which NCP provides, uses 8-bit Latin-1 (ISO 8859-1) encoding for user names and passwords. This encoding supports umlauts and most Western European characters. However, other characters might not be supported. The NCP client does not support UTF-8, which would allow non-ASCII characters to be encoded and supported.Your authentication server might not support non-ASCII characters or UTF-8. We recommend that you avoid non-ASCII characters, such as diacritical marks and symbols, in user names and passwords. For example, do not create user names and passwords that include umlauts (ë), the British pound sign (£), or other non-ASCII characters.
Workaround/Solution
Replace non-ASCII characters with ASCII characters in the user name and password.
