Web process crash due to html5 RDP using FQDN host and NLA or RDP encryption with wrong or empty credentials
This article describes an issue where Web process crashes due to Html5 RDP using FQDN host and NLA or RDP encryption with wrong or empty credentials.
Problem or Goal
This problem can occur irrespective of whether the PCS is configured with FIPS enabled or FIPS disabled. This issue is triggered only if connecting to an RDP server defined as a FQDN hostname and easily reproduces when bookmark does not have any credentials configured.
When the user is prompted, entering the wrong credentials (username and/or password) will crash the web server. This issue can also occur when the username is already populated and the wrong password is entered.
Note: It was observed that even if username is populated in the html5 admin-created bookmark, the prompt does not display the username in the credential intermediation page and displays blank. Typing the proper username and wrong password can also trigger a bug.
This a bug and to be released noted in PCS 9.1R9.1 as "For advanced HTML5 sessions if the FQDN is not resolved web process may terminate and restart".
Note: Even though the Standard HMTL5 session is used, the issue can occur due to DNS.
The issue will be resolved in PCS Software Version 9.1R9.1 with an estimated release date around 3rd week or 4th week of November. The only workaround is use IP-based RDP host or enter the hostnames in the PCS hosts file instead of relying on DNS resolution.