Microsoft Edge ( 64 bit) browser update makes SAP portal go blank – Permanent solution

We recently had a Microsoft update and after that our users were not able to open some documents in SAP portal screens. Upon checking we found that the issue is only with Microsoft Edge 64 bit and Chrome. Firefox and Microsoft Edge 32 bit is working fine.

Following is a permanent solution which administrator has to do in order to solve the issue. This requires a downtime. When you dont have downtime, I have published another blog for temperory solution

The solution is based on three SAP notes

1. 3369675 – FAQ Enterprise Portal inner application navigation issues with Google Chrome
2. 3159245 – Google Chrome disables domain relaxation starting M109
3. 3154411 – WDA: After a Chrome update, it is no longer possible to navigate or send events in a SAP Portal or NWBC

There are three places where the changes are needed

• Change in NWA
• Change in the SAP webdispatcher profile.
• Change in ABAP program

a) Change in NWA

Set a Custom Response Headers to custom value {Origin-Agent-Cluster=?0} in the HTTP provider.  The steps with screenshot is clearly defined in point 8 of the SAP note 3369675 – FAQ: Enterprise Portal inner application navigation issues with Google Chrome Version starting 115/116 & Edge Version starting 118/119

And then restart Java

b) Change in the SAP webdispatcher profile.

Set a modrule file icm/HTTP/mod_X in SAP webdispatcher profile
Maintain the header in the modrule file.
Steps are clearly mentioned in point 11 in the same note above SAP note 3369675 – FAQ: Enterprise Portal inner application navigation issues with Google Chrome Version starting 115/116 & Edge Version starting 118/119

And restart SAP Webdispatcher

c) Change in ABAP program

Based on your version of SAP Basis or SAP GUI component apply the code change
SAP note 3154411 – WDA: After a Chrome update, it is no longer possible to navigate or send events in a SAP Portal or NWBC

More information on the issue below
Deprecating document.domain setter. #564
what-does-document-domain-document-domain-do
Chrome disables modifying `document.domain` – Chrome for Developers