Where do IAS and IPS fit in SAP SuccessFactors Learning?
IAS and IPS address different identity responsibilities in SuccessFactors Learning. Authentication, provisioning an identity and maintaining Learning user data are connected flows, but they are not the same operation.
Evidence CDecision horizon 6 monthsUpdated 09 Oct 2026Proof patterns 1
Editorial context for Where do IAS and IPS fit in SAP SuccessFactors Learning?
LT Horizon generated editorial illustration · not evidenceImage provenanceLT Horizon deterministic SVG generated from a source-reviewed, catalogue-aware editorial visual contract; explanatory context only, never evidence.View diagram at full size
Read diagram text
Comparison diagram with IAS on the left for authentication, sign-in, password recovery and identity experience; IPS on the right for creating, updating and deactivating Learning users. A separate center layer covers authoritative user data and Learning-record governance, leading to a population-by-population identity and provisioning matrix before configuration.
Authentication and identity provisioning
Identity Authentication verifies a sign-in and supports access to the relevant service. Identity Provisioning manages identity information exchanged between systems. SAP's Learning-only integration account includes provisioning identities from Learning to Identity Authentication.
That documented direction is important: an identity service should not be assumed to be the authoritative HR source or the mechanism that populates every Learning attribute. The appropriate source and provisioning flow depend on the population being served.
The Learning record has a separate purpose
Learning needs a user record and attributes for assignments, reporting and the learning lifecycle. Those data can remain relevant even when authentication is handled by Cloud Identity Services.
SAP's documentation treats Learning-only migration steps as additional to the suite Platform's workforce migration steps. Employee, external and Learning-only journeys therefore need to be understood in their own context rather than inferred from one successful login.
Sites and examples do not establish a universal topology
Learning Sites provide a population-facing route with registration and branding options. SAP documents that a site is separate from authentication, including conditional authentication behaviour.
The Endress+Hauser story establishes extended-enterprise use of Learning but does not disclose the customer's exact IAS/IPS topology. Together, the sources explain separate identity responsibilities and an external-user pattern. The guidance below applies those distinctions while retaining tenant-specific ownership of the actual data and access paths.
How to read this briefCheck the sources to see what is documented. Our recommendation explains what that means for your decision. Proof patterns add specific design or implementation examples and explain their limits.
LT Horizon DECISION BRIEF
Answer
IAS addresses authentication and identity experience; IPS addresses provisioning flows. Neither replaces the need to decide where authoritative user data originates or how Learning records are governed.
INVESTIGATE — produce a population-by-population identity and provisioning matrix before configuring IAS or IPS.
LT Horizon interpretation · Evidence confidence C
What changed
No migration deadline or universal requirement is asserted. LT Horizon verified SAP’s documented Learning and Cloud Identity Services integration context for Learning-only users.
Why it matters
Projects often collapse identity, authentication and Learning user provisioning into one question. They are different controls with different failure modes.
Use cases & proof
Where this holds up in practice
These examples show how a specific claim is supported by documentation or an implementation. Read their limits before applying them to your own environment.
Proof pattern · Evidence C
Learning-only users with SAP Cloud Identity Services
Scenario
A learning population uses SAP SuccessFactors Learning without relying on an Employee Central employee record for the same user journey.
Architecture pattern
Learning user population → SAP Cloud Identity Services identity/provisioning pattern → SAP SuccessFactors Learning, with source-of-truth and lifecycle controls explicitly defined.
Observed / documented outcome
SAP documents the Learning-only Cloud Identity Services pattern and Learning Sites for extended-enterprise access. A named Endress+Hauser customer story separately demonstrates real use of SuccessFactors Learning to train partners in an extended-enterprise model, with a dedicated onboarding solution around that population.
What this proves
Employee Central is not the only possible basis for every Learning user population. SAP documents Learning-only identity and access patterns, and named customer evidence shows SuccessFactors Learning being used operationally for partner populations outside the internal workforce.
What it does not prove
It does not prove that Endress+Hauser uses the exact IAS/IPS topology described in the official documentation, that all internal employee populations should bypass Employee Central, that identity services replace authoritative workforce data, or that one external-user pattern is suitable for every tenant.
Apply with these constraints
Define registration, authoritative data, identity tenancy, unique identifiers, provisioning direction, privacy, account recovery, deactivation, retention and support ownership by population. Confirm the supported identity flow for the specific tenant rather than inferring it from the customer case.
Last checked 18 Sept 2026 · Reviewed before publication.
Implementation implications
Prerequisites
Confirm user populations, source systems, identity tenancy, corporate identity-provider relationship, provisioning direction, unique identifiers and support ownership.
Architecture implications
Model authentication, identity provisioning and Learning user data as separate flows. Map where each user is created, authenticated, updated and deactivated.
Risks
Duplicate identities, mismatched identifiers, inaccessible accounts, unmanaged password journeys and unclear responsibility between HRIT, IAM and Learning teams.
Testing implications
Test authentication, provisioning, unique-ID matching, role/group assignment, deprovisioning, recovery and population-specific access routes.
Source register
What the evidence establishes
Endress+Hauser uses SuccessFactors Learning for partner training
SAP’s named customer story describes extended-enterprise training for partners and an onboarding application. It does not disclose the customer’s complete authentication or provisioning design, so it cannot establish a universal Learning-only architecture.
Availability: Named customer outcome hosted by SAP. It evidences real extended-enterprise use of SuccessFactors Learning but does not disclose the customer's IAS/IPS tenant topology, provisioning direction or exact Learning-only authentication design.
SAP documents distinct site URLs for groups of Learning-only users, including registration, branding and guest catalogue access. A site is separate from authentication: Identity Authentication controls how the user signs in.
Learning and SAP Cloud Identity Services integration overview
SAP identifies Identity Authentication as the login service for Learning-only users. Identity Provisioning orchestrates identity transfers between applications, including Learning-to-Identity Authentication provisioning; these responsibilities are separate from maintaining employee HR data.
SAP describes SuccessFactors Learning as a standalone product or part of its human capital management suite. This product description does not, by itself, establish that every implementation can dispense with platform, identity or data-provisioning dependencies.
Publication review is recorded in the evidence and correction history. Images illustrate the article; they are not evidence.
History and corrections
Article body revision 1 · added 09 Oct 2026. Explanatory text added to the published evidence snapshot; evidence confidence, availability and source verification dates are unchanged.
Published revisions are retained. Update dates change only after a change to the content or evidence.
Get occasional email updates when LT Horizon publishes new Intelligence and Horizon articles. Free to read, with no account required.
Our practical newsletter format brings one question, one idea and one exercise, alongside selected source-linked articles. Editions follow useful reviewed evidence.
