Hi Everyone,
I’m writing this blog to share the resolution of an issue I recently encountered in my project. Hopefully, it will help others facing a similar challenge.
Issue Details
Working Scenario:
We are using an Employee Self-Service (ESS) Web Dynpro application based on LPD_CUST configuration in an SAP S/4HANA 2023 Rise system (For ECC also it will work).
The application was working perfectly when our portal system and backend system were both using the HTTP protocol, with the connection established through a system alias in the portal.
When the Issue Started:
As per the SAP Rise team’s security guidelines, HTTP access to the S/4HANA system was disabled. Consequently, we had to switch our portal and load balancer configuration to use HTTPS instead, ensuring secure communication with the backend.
After implementing HTTPS, we tested the ESS application. While the Web Dynpro application worked fine in standalone mode, navigation within the portal (e.g., clicking “Create Leave Request”) stopped functioning.
No errors appeared in the browser console or network tab — the click simply produced no response from the server. PFA the Screen shot for your reference (ESS Leave Request Application Navigation issue.JPG) .
Analysis:
After reviewing multiple blogs and SAP community posts, I came across the following SAP Knowledge Base Article (KBA), which provided the key insight:
SAP KBA: 3369675 - FAQ: Enterprise Portal inner application navigation issues with Google Chrome Version starting 115/116 & Edge Version starting 118/119
According to this KBA, recent updates in Chrome and Edge introduced stricter browser policies affecting inner application navigation within the Enterprise Portal.
Resolution:
To resolve the issue, we updated the following parameter in the NWA (NetWeaver Administrator):
Current Value: PFA the Screen shot (Current Value of CustomResponseHeaders.JPG)
CustomResponseHeaders = {X-FRAME-OPTIONS=SAMEORIGIN}
Updated Value: PFA the Screen shot (Updated Value of CustomResponseHeaders.JPG)
CustomResponseHeaders = {Origin-Agent-Cluster=?0}
After applying this change we need to take application restart (All Application Server one by one).
Afte restart the parameter effected and ESS application navigation started working correctly.
Conclusion:
This issue was caused by recent browser security updates impacting portal navigation behavior. Adjusting the response header as per the SAP KBA resolves the issue effectively.
I hope this post helps anyone encountering a similar problem in their SAP environment.
Best regards,
Rohit Gera
Bluesky
