SAP Fiori Launchpad Deployment Options

We will tackle the things about SAP Fiori Launchpad deployment options. Also, let us learn the importance of these Launchpad deployment options.

What Is SAP Fiori Launchpad Deployment Option?

SAP Fiori Launchpad deployment option is a way in which you can install SAP Fiori Launchpad. There are four main SAP Fiori Launchpad deployment options, and these are as follows:

Driving Business Value Through UC - Sap-ebook-banner
  • Single-Sign-On (SSO) or Standalone Single-Sign-On (SSO)
  • Embedded Single-Sign-On (SSO)
  • Standalone Embedded Single-Sign-On (SSO)
  • High Availability Single-Sign-On (SSO)

These four different SAP Fiori Launchpad deployment options can be explained in a better way. Let us go through them one by one.

Single-Sign-On (SSO) or Standalone Single-Sign-On (SSO): 

The first option is SSO. This single sign-on (SSO), it will allow the users to log in to the company’s enterprise application using their existing credentials from the same user interface. 

For example, if a user logs in to the SAP portal using his SAP credentials. Then he can use SAP Fiori Launchpad with the same login.

But there will be no integration between the two applications. This option can be used independently without any other options.

That is, it does not require any other parts for its use. It can be used as a single option only and it cannot be used as an embedded option. It allows users to access SAP Fiori Launchpad with their existing credentials. 

Even if they are not assigned to the solution owner of SAP Fiori Launchpad.

Embedded Single-Sign-On (SSO): 

It is a similar version of SSO, but it requires an additional configuration from the administrator. It requires “Single Sign-On Authentication” feature integration. 

With this feature, users will not have to log in twice for accessing different applications. But they will only need to log in once to access both applications. 

Both applications will share the same user ID and password. This option is also called embedded SSO because this option allows users to access both applications.

So SAP Portal and SAP Fiori LaunchPad with just one single sign-on session. That is, they will share the same user ID and password while logging into both worlds. 

If a user logs into his account from the SAP portal, then he will be able to log into SAP Fiori Launchpad as well. Both of them will share one single ID and password.

This embedded option is also known as Single-Sign-On (SSO) or Standalone Embedded Single-Sign-On (SSO). It can also be used as a standalone option without any other options.

Standalone Embedded Single-Sign-On (SSO):

This option is a combination of the first and second options. This option is also known as standalone embedded single-sign-on (SSO). 

It combines SSO and embedded SSO to form a single option. With this option, users will not have to log in twice for accessing different applications. 

They will only need to log in once to access both applications. Both applications will share the same user ID and password. 

So this option is also called embedded SSO because this option allows users to access both applications. If a user logs into his account from the SAP portal, then he will be able to log into SAP Fiori Launchpad as well. 

Both of them will share one single ID and password. It can also be used as a standalone option without any other options. But in that case, it will require hierarchical administrator permissions, or it cannot be used as an embedded option. 

It cannot be used to integrate with SAP Portal as well as SAP Business Suite. 

High Availability Single-Sign-On (SSO): 

It is the most scalable version of this deployment options list. This option is also known as high availability single-sign-on (SSO). We can use this deployment option in large enterprises where there are several hundred users or more than that. 

It combines SSO or embedded SSO with “Single Sign-On Authentication” feature integration. With this feature, we can use SSO for accessing SAP Fiori Launchpad as well as SAP Portal with just one single sign-on session. 

That is, they will share the same user ID and password while logging into both worlds. If a user logs into his account from the SAP portal.

Then he will be able to log into SAP Fiori Launchpad as well. Both of them will share one single ID and password.