Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

Trust configuration tells an application which identity provider to accept. The identity provider verifies a user; the provider’s origin helps distinguish where that identity comes from.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Security separates verifying an identity from granting permission to perform business actions. A role groups relevant access, while restrictions define the allowed data and activities.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP BTP login works for one user type only? Check trust scope and origin
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP BTP platform and business-user trust; origin examples are specifically SAP BTP XS Advanced UAA in Cloud Foundry. Kyma, ABAP, database and service-specific authentication require their own documentation.

Reviewed relevant official SAP indexed documentation excerpts on 14 November 2026. Examples, identifiers, amounts and expected observations are illustrative; no customer SAP execution was performed. Official indexed excerpts reviewed; no live BTP tenant, sign-in, provisioning job or trust change. Connector-specific origin examples do not establish universal BTP defaults; tool support and environment configuration must be checked locally.

A MANUFACTURING EXAMPLE

Compare employee login contexts for a factory app

Compare the same sign-in path

Working login: BTP cockpit administrator. Failing login: Business application user. Identity provider: Confirm intended provider. Origin scope: Confirm relevant identity
What to notice: A working cockpit login does not exercise every application authentication path.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Working login
BTP cockpit administrator
Failing login
Business application user
Identity provider
Confirm intended provider
Origin scope
Confirm relevant identity
Words you’ll meet in this guide
Authentication
Checking who an identity belongs to.
Authorization
Permission for an action on particular data.
PFCG
The classic ABAP Role Maintenance transaction for organizing roles.
Role
A grouping of intended tasks and associated permissions.
Authorization object
A grouping of related permission fields checked by relevant SAP application logic.
ABAP
SAP’s programming language for business applications.
BTP
SAP Business Technology Platform: cloud services for applications, data and integration.
HANA
SAP’s database platform.
HTTP
The request-and-response protocol used by web applications and APIs.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Application entry → Trusted identity provider → Recognized identity. Conceptual diagram for SAP BTP login works for one user type only? Check trust scope and origin.
Apply the idea: A manufacturer's user can sign in through one identity context but cannot reach the same BTP application through another.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Compare employee login contexts for a factory app

    A manufacturer's user can sign in through one identity context but cannot reach the same BTP application through another.

  2. Start with the failing sign-in route

    A successful SAP BTP cockpit login proves that one platform sign-in path worked for that identity.

  3. Scope and prerequisites for this investigation

    The main case concerns SAP BTP platform and business-user trust, with origin examples specifically grounded in SAP BTP XS Advanced UAA in Cloud Foundry.

  4. Map platform and business-user trust separately

    SAP describes platform identity-provider trust at global-account level, applying to the relevant lower account and environment levels.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.