Introduction
As we know organizational end-users utilize the Enteprise Portal as a centralized means of access to business information, data and applications. On occassions scenarios may arise in which a third party SAAS may be accessed through user mapping and system access settings.
Such business processes and practices may be initially maintained through a URL iView. URL iViews retrieve Web-based content from a wide range of current and legacy sources; for example your organization intranet and internet Web sites. We refer to these Web-based information sources as Web pages .
Issues Between Client Side & Server Side Rendering
Access to external SAAS Providers should in theory work accordingly through HTTP GET requests and client-side fetching. There may however be security concerns with the HTTP Post requests via server side fetching and issues may be encountered subsequently.
A common noted occurrence here is that of a "HTTP 500" error exception highlight.
Why ?
Firstly from a high level perspective creating Web-based URL iViews that employ the "server-side fetch" method use the proxy settings defined on the portal server and this is standard behavior.
As per standard design URL iViews that employ the "client-side fetch" method rely on the proxy settings defined in the browser of each portal user across the landscape.
Also just to highlight here the server side fetch mode does not support URLs that are automatically redirected to another URL.
Defining a Proxy Server
Defining a Proxy Server for the Portal
As we know organizational end-users utilize the Enteprise Portal as a centralized means of access to business information, data and applications. On occassions scenarios may arise in which a third party SAAS may be accessed through user mapping and system access settings.
Such business processes and practices may be initially maintained through a URL iView. URL iViews retrieve Web-based content from a wide range of current and legacy sources; for example your organization intranet and internet Web sites. We refer to these Web-based information sources as Web pages .
Issues Between Client Side & Server Side Rendering
Access to external SAAS Providers should in theory work accordingly through HTTP GET requests and client-side fetching. There may however be security concerns with the HTTP Post requests via server side fetching and issues may be encountered subsequently.
A common noted occurrence here is that of a "HTTP 500" error exception highlight.
Why ?
Firstly from a high level perspective creating Web-based URL iViews that employ the "server-side fetch" method use the proxy settings defined on the portal server and this is standard behavior.
As per standard design URL iViews that employ the "client-side fetch" method rely on the proxy settings defined in the browser of each portal user across the landscape.
- You can validate the proxy settings maintained (on the browser) of your testing machine to validate this.
Also just to highlight here the server side fetch mode does not support URLs that are automatically redirected to another URL.
Defining a Proxy Server
Defining a Proxy Server for the Portal
- SAP Managed Tags:
