Hi Everyone,
I’m writing this blog to share the resolution of an issue I recently encountered in my project. I hope this post helps anyone facing a similar challenge.
Issue Overview
Working Scenario:
We are using SAP Enterprise Portal (with the HTTP protocol) to fetch work items from an SAP S/4HANA 2023 Rise system. The same approach also works with SAP ECC.
The application was functioning perfectly when both the portal and the backend systems were communicating over HTTP, with the connection established through a system alias in the portal.
When the Issue Started
As per SAP Rise security guidelines, direct HTTP access to the S/4HANA system was disabled. Consequently, we switched both our portal and load balancer configurations to use HTTPS to ensure secure communication with the backend.
After implementing HTTPS, we tested the UWL (Universal Worklist) functionality. However, instead of loading the work items, the page appeared blank, and the browser console displayed a mixed content error — this happened because the portal (served via HTTPS) was attempting to load the UWL iView using HTTP.
(Please refer to the attached browser console screenshot for reference.) (Mix Content error in Browser Console for UWL in HTTPS.JPG)
Analysis
After reviewing several blogs and SAP Community posts, I found an SAP Knowledge Base Article (KBA) that provided the crucial insight:
SAP KBA: 1927272 - How to configure proxy mapping for external access through reverse proxy server
According to this KBA, we needed to update the ProxyMappings parameter in the NetWeaver Administrator (NWA) of the SAP Enterprise Portal.
Resolution
To resolve the issue, we made the following configuration change in the NWA:
Previous Value:
ProxyMappings: <Blank>
Updated Value: PFA (Updated Value of ProxyMappings.JPG)
ProxyMappings: 52000=(Host:<Host Name>,Port:443,Scheme:https,Override:true)
After applying this change, we restarted all application servers (one by one) to ensure the new settings took effect.
Once the restart was complete, the ESS application navigation and UWL functionality started working correctly.
Conclusion
The issue occurred due to recent browser security updates affecting how mixed content is handled in portal navigation. By adjusting the ProxyMappings parameter as per SAP KBA 1927272, we were able to resolve the problem successfully.
I hope this solution helps others who encounter similar HTTPS-related issues in their SAP environment.
Best regards,
Rohit Gera
Bluesky
