If you are an SAP SuccessFactors customer with an interest in reporting and analytics, you're probably aware that SAP Cloud Identity Services, which includes IAS and IPS, is a pre-requisite to implement Report Stories (or 'Stories in People Analytics'). Whilst these terms are commonly used within wider IT work streams, they are less common in traditional SuccessFactors projects and so can cause confusion.
In this blog we answer common questions on Cloud Identity Services for SAP SuccessFactors customers. For other FAQs about Report Stories or Workforce Analytics, please check out their FAQ pages.
What do SuccessFactors customers need to know about SAP Cloud Identity Services?
Think of Cloud Identity Services as single-sign-on (SSO) for SAP applications. It is really that simple--to connect to other SAP applications, you use Cloud Identity Services, much like how many organizations use a corporate identity provider (IdP) like Okta or Azure.
Diagram made by and sourced from SAP
What terms do SuccessFactors customers need to know about SAP Cloud Identity Services?
Here are some of the more commonly used Cloud Identity service terms that you need to know:
- SAP Cloud Identity Services: A group of services for user authentication and provisioning.
- Identity Directory: A single user repository.
- Identity Provisioning Service (IPS): Used to provision users, or sync them from the source to a target. For our typical use case, this source is SuccessFactors and the target is the Identity Directory.
- Identity Authentication Service (IAS): Used to authenticate users. For our use case, IAS is used to authenticate users to SuccessFactors and Stories in People Analytics. And in the future, other SAP applications.
Do SuccessFactors customers need to replace Okta, Azure or Single Sign On applications with Cloud Identity Services?
This is not an issue. Your corporate IdP configuration can be updated to communicate with IAS. Then users will connect to SuccessFactors via Okta, Azure, or your IdP just as they do today.
How hard is it to implement Cloud Identity Services for SuccessFactors?
Authentication concepts and configuration are often unfamiliar to HR teams and there is a fair amount of complexity with these implementations. That said, the 3n Strategy team have the right skills and expertise and have completed Cloud Identity Services and Stories in People Analytics implementations for numerous customers.
Can users keep their existing SuccessFactors password when implementing Cloud Identity Services?
This process does not need to be disruptive to your end users--IAS can be configured so that user's existing SuccessFactors password is reused.
How does managing passwords change when using Cloud Identity Services for SuccessFactors?
After implementation you will manage passwords in IAS instead of SuccessFactors. Or if you have a corporate IdP, user management would continue in that system.
What do SuccessFactors customers need to do on an ongoing basis to keep Cloud Identity Services running smoothly?
Once Cloud Identity Services are implemented, they typically run on their own. A recurring job syncs new hires into IAS so they can login, and removes terminated employees so their logins are disabled. Email alerts can be set up so administrators can quickly act if there is an issue.
Do SAP SuccessFactors customers have to implement Cloud Identity Services now? When will it be required to do so?
If you want to take advantage of the modern reporting features of Stories yes, you need to implement Cloud Identity Services now. It is also required for Internal Career Site and SAP Work Zone for HR. Finally, it will be required for all SuccessFactors customers at a future date.
Can 3n Strategy help us implement Cloud Identity Services?
We offer a full complement of services required to activate and be successful with Report Stories, including implementing IAS and Cloud Identity Services. Please get in touch to find out more.