An application is associated with a consumer of Identity Authentication as an identity provider. This consumer could be for example an SAP cloud solution, a third-party application, SAP BTP subaccount, or the SAP Cloud Identity Services administration console.
The application holds the configuration information about trust, authentication, access, and branding of the given consumer. SAP and customers create applications in SAP Cloud Identity Services administration console. The following table describes the different types of applications, who is in charge of them and whether they are configurable or not:
|
Created By |
Application Type |
Application Display Name |
Specifics |
|---|---|---|---|
|
SAP |
Bundled Applications |
For example: S4HANA Cloud - <s4-tenant-type> |
SAP creates bundled applications and is in charge of their configuration. |
|
System Applications |
Administration Console |
SAP creates and preconfigures the administration console as a system application. |
|
|
User Profile |
SAP creates and preconfigures the profile page with some personal information. |
||
|
Subscribed Applications |
For example: SAP BTP <subaccount display name> |
Subscribed applications are associated with an SAP BTP subaccount or an application registered there. These applications are automatically created for you. You can't create or delete them. |
|
|
Customer |
Charged Applications |
For example: Microsoft Entra ID |
Charged applications are created by customers for third-party (non-SAP) solutions. Customers are in charge of the configuration and are charged for integrating applications with Identity Authentication. |
|
Bundled Applications |
For example: SAP Concur |
Apart from SAP, bundled applications can also be created by customers. This applies for SAP cloud applications that do not bundle the delivery and preconfiguration of the SAP Cloud Identity Services. |
Applications are sometimes referred to as SAML 2.0 applications or OpenID Connect applications depending on the configured protocol. The SAML 2.0 standard defines applications as service providers, while OpenID Connect (OIDC) defines them as relying parties.
For more information, see Application Types and Configuring Applications.
Related Information