Last Modified: Apr 28, 2025
Affected Product(s):
APM-Clients APM
Known Affected Versions:
7.2.2, 7.2.2.1, 7.2.2.2, 7.2.3
Fixed In:
7.2.4, 7.2.3.1
Opened: May 18, 2022 Severity: 4-Minor
When Edge Client is redirected to an External Logon page it fails to properly render the External Logon page in the small pop-up window using the default rendering engine. The default rendering engine leads to multiple javascript errors and the page remains stuck.
The logon process is impacted due to javascript errors.
The Edge Client attempts to use the default rendering engine for logon.
1. Launch a command prompt with administrator privilege and run regedit 2. Navigate to: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION (NOTE: Fix for this bug creates rundll32.exe key in the above location when the logon page is popped, so this location is preferred over HKLM) (or) HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION 3. Right Click -> New -> DWORD (32-bit) Value => rundll32.exe 4. Double Click "rundll32.exe" and input: 2af8 (Hexadecimal) [it is same as 11000 (Decimal)]. Press "OK". 5. Exit Edge Client. Relaunch Edge Client. OR 1. On External Logon site: when external logon site responds with HTML codes, add an appropriate meta tag like the below at an appropriate location: <meta http-equiv="X-UA-Compatible" content="IE=edge">
Fixed the issue where Edge Client fails to render the external logon pages in some cases.