3658233 - Case Study: Fiori Application when launched Navigates Back to Fiori Launchpad Home Page

• Any Fiori Application when launched will have a URL Intent (or URL address) that will be used to launch the application
  • This said application will then be launched and stay within the URL context originally provided; however, sometimes via some networking protocol or routing, some redirects may occur which then may point the original intended URL path to the baseline Fiori Launchpad Home page like (https://<domain>:<port>/sap/bc/ui2/flp?<sap-client=X>&<sap-language=EN>#Shell-home or the equivalent browser URL for Fiori Launchpad Home page.
• Please note that this can happen in any Fiori Application context from UI5 to WebGUI path or others
• For the purpose of this Case Study, SAP will concentrate in a Fiori Application called:  "My Inbox", and may explain the reason why the browser URL on the intended target may route back to the Fiori Launchpad main home page, why is this so?
• First let us give a potential case study tied to routing (The Fiori example provided here is My Inbox but please note that it can happen to any Fiori application as this is a SECURITY TYPE of ISSUE):
  • Case 1:  What may work?
    • Intranet routing inside the network, may show that the Fiori Application like My Inbox (or any Fiori application) direct URL path may show that it works
    • In the Fiori application My Inbox perspective, this application works with several types of backend Task Providers like:
      • My Inbox
        
        • Get Data from Task Provider 1 ==> Task Processing ==> Backend Odata tied to Task 1
        • Get Data from Task Provider 2 ==> Task Processing ==> Backend Odata tied to Task 2
        • .. and so forth
      • Each of the Task Provider will be processed by the Task Processing service then ultimately be routed to the Backend Odata Service to serve the query
      • In My Inbox, each task will be served by certain buttons like:
        • Reject
        • Complete
        • Opent Task
        • and others
      • Each of these buttons will correspond to a workflow action that will be done and will try to access the needed backend
    • If most of the routing is internal only, then the prior logon that was done by the user to access in My Inbox is still in play so there will be no issues with going to the needed backend and most of the security has some persistence
  • Case 2:  What may NOT work?
    • In the Fiori application My Inbox, sometimes an email will be provided to a user to accept or reject certain task like Purchase Order or Purchase Requisition
      • My Inbox ==> Process ==> Work Process (This may send an email)
        
        • Microsoft Email
          • Users received an email in their device/laptop and they may have to click a URL link to get to this Task
          • At this point, this will be the start of the point of failure.
          • Any action by My Inbox will then not used the prior authentication and may have to go through some internal authentication and the key to seeing this is that a User has to enter some sort of Popup logon screen (could be the SAPGUI Logon or any Microsoft Logon screen like Azure or others)
          • At this point, the action of any Fiori application like My Inbox may route to the Fiori Launchpad Page or Home page as a results instead of staying within the context of the application
      • Why is this the case wherein the application was redirected back to the Fiori Launchpad Page or Home page?
      • This is the main error and can be experienced by not just one Fiori application like My Inbox, but it will be experience by any Fiori Launchpad Application?

• S/4HANA 2023 and other

FLP Home Page, Redirect to Fiori Launchpad, Application navigates to Fiori Launchpad, FLP Home, SSO Logon, Fiori Application SSO Popup, Fiori Microsoft Logon, FLP Azure Logon, My Inbox Task Logon Screen , KBA , BC-SEC-LGN-SML , SAML 2.0 for ABAP , CA-INB-FIO , Fiori UI for My Inbox Application , CA-FLP-ABA , SAP Fiori Launchpad ABAP Services , Problem