Show TOC

Configuring Logout from Integrated SystemsLocate this document in the navigation structure

You may need to configure one or more logout rules and define a custom logout page to ensure logging out completely from all integrated systems.

Overview

When using other systems that are integrated with SAP Fiori launchpad, after logging out, an open browser window may still contain session cookies. A user who has access to the open browser window can access these systems without having to authenticate. The solution described in this topic ensures that session cookies of all systems are removed when logging out from SAP Fiori launchpad.

Scenarios Not Requiring Logout Configuration

For the following scenarios, logging out is performed completely and you do not need to perform the extra logout configuration described in this topic.

  • SAP Fiori launchpad front-end server.
  • Enterprise Search system (AS ABAP).
  • Systems used to load remote tile catalogs, such as SAP HANA KPI tiles for SAP Smart Business.
  • SAP Lumiraâ„¢ running in SAP Fiori launchpad.
    Note For releases of SAP Lumira prior to 1.18, it is necessary to perform the configuration as described in SAP Note 2010502 Information published on SAP site.
  • Systems that are accessed to start Web Dynpro ABAP or SAP GUI for HTML applications in SAP Fiori launchpad based on report launchpad customizing with specific application types (not plain URL) - either through SAP Web Dispatcher or directly on the system.
Scenarios Requiring Configuration to Ensure Complete Logout from All Systems

You need to configure one or more logout rules in SAP Web Dispatcher and define a custom logout page to ensure logging out completely from all systems for the following scenarios:

  • SAP Gateway systems (hub) that are not installed on the front-end server (other client, server, or system); these are used to connect to ABAP application back-end systems.
    Note To keep the complexity of the system landscape to a minimum, we advise having only one SAP Gateway server on the SAP Fiori front-end server.
  • SAP HANA or other systems accessed via REST or OData, for example, but not used to load remote catalogs.
    Note This does not include SAP Lumira scenarios, as mentioned above.