PUBLIC

Document Version: 2H 2023 – 2024-01-11

IT Landscape Requirements for SAP

SuccessFactors
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 SAP SuccessFactors IT Landscape Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Client-Side Requirements for SAP SuccessFactors HXM Suite. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1 Supported Desktop Browsers for SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Supported Mobile Browsers for SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Supported Workstation Operating Systems for SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 Browser Configuration Requirements for SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.5 Mobile Application Support for SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.6 Oracle Java Runtime Environment (JRE) for SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.7 Adobe Acrobat Reader for SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.8 Supported Document Types in SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.9 Accessibility Support in SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 Checking Your Network Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4 Allow Listing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1 Verify Akamai Allow Listing with a Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2 Verify SFAPI/OData Allow Listing with a Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3 Verify SFAPI/OData Allow Listing With CURL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.4 Allowlist Methods for Email from SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Requesting a Key for Domain Key Identified Mail (DKIM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Adding Listings for Sender Policy Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5 List of SAP SuccessFactors API Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 Integration Center Enterprise Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6 Time Synchronization Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7 Certificate Renewal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

8 Cookie Handling in SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

8.1 What Are Cookies?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.2 List of Cookies in SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

9 Standards for SAP SuccessFactors Learning Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

9.1 AICC and SCORM Support for SAP SuccessFactors Learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
9.2 Supported Virtual Meeting Software for SAP SuccessFactors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

10 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

IT Landscape Requirements for SAP SuccessFactors

2 PUBLIC Content
1 SAP SuccessFactors IT Landscape Checks

An SAP SuccessFactors IT landscape check is a set of tasks and checks that Information Technology (IT)
professionals use to make sure that SAP SuccessFactors works well in their organization's software landscape.

SAP SuccessFactors is part of your IT landscape: all of the software tools you use, in the cloud and within your
organization. As an IT professional, you keep all parts of your IT landscape integrated, secure, and so on. SAP
SuccessFactors IT landscape checks are a set of instructions that we want you to be aware of, so you can keep your
organiztion's software landscape healthy.

 Note

The leading practice checks from SAP SuccessFactors aren’t the only checks you run: your IT department likely
has its own checks.

IT Landscape Requirements for SAP SuccessFactors

SAP SuccessFactors IT Landscape Checks PUBLIC 3
2 Client-Side Requirements for SAP
SuccessFactors HXM Suite

To use SAP SuccessFactors HXM Suite, your users need common browsers, mobile devices, and plug-ins.

Most users experience SAP SuccessFactors through their mobile devices or through a web browser on their
workstations. In some specific cases, however, we do require additional systems and connectivity. We provide the
full list so that you can check user workstations and devices.

Supported Desktop Browsers for SAP SuccessFactors [page 4]

SAP SuccessFactors supports these desktop browsers.

Supported Mobile Browsers for SAP SuccessFactors [page 6]

SAP SuccessFactors supports these mobile browsers.

Supported Workstation Operating Systems for SAP SuccessFactors [page 7]

SAP SuccessFactors supports these workstation operating systems.

Browser Configuration Requirements for SAP SuccessFactors [page 8]

SAP SuccessFactors requires browsers to be configured with these attributes.

Mobile Application Support for SAP SuccessFactors [page 10]

SAP SuccessFactors Mobile app supports these configurations.

Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
SAP SuccessFactors requires JRE in these cases.

Adobe Acrobat Reader for SAP SuccessFactors [page 12]

SAP SuccessFactors requires Adobe Acrobat Reader in some cases.

Supported Document Types in SAP SuccessFactors [page 13]

SAP SuccessFactors supports these document types.

Accessibility Support in SAP SuccessFactors [page 13]

SAP SuccessFactors is committed to accessible software.

2.1 Supported Desktop Browsers for SAP SuccessFactors

SAP SuccessFactors supports these desktop browsers.

Supported Versions

We support the following desktop browsers:

• Google Chrome
• Microsoft Edge

IT Landscape Requirements for SAP SuccessFactors

4 PUBLIC Client-Side Requirements for SAP SuccessFactors HXM Suite
• Mozilla Firefox
• Safari by Apple

We support browser versions that are still supported by their respective vendors. If your browser version is no
longer supported by the vendor, it may not be supported by SAP SuccessFactors.

Google, Apple, and Mozilla release continuous updates to their Chrome, Safari, and Firefox browsers. We make
every effort to fully test and support the latest versions as they’re released. However, if defects are introduced in
these OEM-specific browsers, we can't guarantee fixes in all cases.

Additional Information

 Remember

We ended support for Internet Explorer 11 on November 19, 2021. Visit the SAP SuccessFactors Customer
Community blog Internet Explorer 11 Browser Deprecation – Innovation Alert for all the latest updates and
guidance.

 Note

For customers using SAP SuccessFactors Validated Learning:

You can continue to use Internet Explorer 11 specifically for the Question Editor (QE) functionality until the
1H 2022 release. Administrators who want to use the QE must log into the administration environment with
Internet Explorer in both browser mode and document compatibility mode. Using the developer tools (press
F12), set browser mode to Internet Explorer 7 and document mode to Internet Explorer 7 standards.

 Note

Stories in People Analytics work with the latest versions of Google Chrome and Microsoft Edge. For more
information, refer to System Requirements and Technical Prerequisites information in the SAP Analytics Cloud
Help guide.

For additional system requirements, see your desktop browser documentation.

Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

Related Information

Supported Mobile Browsers for SAP SuccessFactors [page 6]

Supported Workstation Operating Systems for SAP SuccessFactors [page 7]
Browser Configuration Requirements for SAP SuccessFactors [page 8]
Mobile Application Support for SAP SuccessFactors [page 10]
Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
Adobe Acrobat Reader for SAP SuccessFactors [page 12]

IT Landscape Requirements for SAP SuccessFactors

Client-Side Requirements for SAP SuccessFactors HXM Suite PUBLIC 5
Supported Document Types in SAP SuccessFactors [page 13]
Accessibility Support in SAP SuccessFactors [page 13]
System Requirements and Technical Prerequisites for SAP Analytics Cloud

2.2 Supported Mobile Browsers for SAP SuccessFactors

SAP SuccessFactors supports these mobile browsers.

Supported Versions

We support the following mobile browsers:

• Safari by Apple
• Google Chrome for Android
• Google Android default browser

We support mobile browser versions that are still supported by their respective vendors. If your mobile browser
version is no longer supported by the vendor, it may not be supported by SAP SuccessFactors.

Additional Information

If you want mobile access, please use the SAP SuccessFactors Mobile Application. Not all features and tasks are
supported on mobile devices.

When using the Safari browser to access the SAP SuccessFactors HXM Suite on an iOS device, the following
settings are required. (These settings are not required if you use the SAP SuccessFactors Mobile App.)

• Block Cookies Always Allow

You can try the setting Allow from Websites I Visit. However, if you encounter issues, use the setting Always
Allow.
• Block Pop-Ups Off

We don't support Stories in People Analytics on mobile browsers.

For optimal performance while accessing SAP SuccessFactors Learning on a mobile device, we recommend using
the native mobile apps. If you use a mobile browser to accessLearning, we recommend using a landscape-oriented
tablet for the best experience. We don't support SAP SuccessFactors Learning Administration on mobile browsers.

Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

IT Landscape Requirements for SAP SuccessFactors

6 PUBLIC Client-Side Requirements for SAP SuccessFactors HXM Suite
Related Information

Supported Desktop Browsers for SAP SuccessFactors [page 4]

Supported Workstation Operating Systems for SAP SuccessFactors [page 7]
Browser Configuration Requirements for SAP SuccessFactors [page 8]
Mobile Application Support for SAP SuccessFactors [page 10]
Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
Adobe Acrobat Reader for SAP SuccessFactors [page 12]
Supported Document Types in SAP SuccessFactors [page 13]
Accessibility Support in SAP SuccessFactors [page 13]

2.3 Supported Workstation Operating Systems for SAP

SuccessFactors

SAP SuccessFactors supports these workstation operating systems.

Supported Versions

We support the following workstation operating systems:

• Microsoft Windows
• Apple macOS

We support OS versions that are still supported by their respective vendors. If your workstation's OS version is
no longer supported by the vendor, it may not be supported by SAP SuccessFactors.

Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

Related Information

Supported Desktop Browsers for SAP SuccessFactors [page 4]

Supported Mobile Browsers for SAP SuccessFactors [page 6]
Browser Configuration Requirements for SAP SuccessFactors [page 8]
Mobile Application Support for SAP SuccessFactors [page 10]
Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
Adobe Acrobat Reader for SAP SuccessFactors [page 12]
Supported Document Types in SAP SuccessFactors [page 13]
Accessibility Support in SAP SuccessFactors [page 13]

IT Landscape Requirements for SAP SuccessFactors

Client-Side Requirements for SAP SuccessFactors HXM Suite PUBLIC 7
2.4 Browser Configuration Requirements for SAP
SuccessFactors

SAP SuccessFactors requires browsers to be configured with these attributes.

Supported Configuration

Client Configuration Setting Additional Information

Network bandwidth Recommended connection speed 300 - In general, HXM Suite requires no more
400 kbit/s bandwidth than is required to surf the
Internet. All application modules are de-
signed for speed and responsiveness
with minimal use of large graphic files.

Stories in People Analytics requires a

minimum bandwidth of 500-800 kbit/s
per user.

Screen resolution XGA 1024x768 (high color) or higher For Stories in People Analytics, the
Widescreen resolution requirement is
1366x766 or higher.

Minimum recommended cache size 250 MB SAP SuccessFactors is a Web 2.0 appli-
cation. We recommend allowing browser
caching because we use it heavily for
static content such as image files, CSS
files, and JavaScript files. If you clear
your cache, the browser does not per-
form as well until the deleted files are
downloaded again to the browser and
cached for use next time.

Newer web pages must be enabled.

HTTP 1.1 Enable

JavaScript Enable

Cookies Enable web browser session cookies for Third-party cookies need to be enabled
authentication purposes
when using certain modules, such as
SAP SuccessFactors Learning, Stories in
People Analytics, and Workforce Analyt-
ics.

Pop-up windows Allow pop-up windows from SAP Suc-

cessFactors domains

IT Landscape Requirements for SAP SuccessFactors

8 PUBLIC Client-Side Requirements for SAP SuccessFactors HXM Suite
Additional Information

SAP SuccessFactors Learning can be launched from a third party site but must be launched in its own window. For
example, you can launch Learning from your corporate portal, but it must launch into its own window.

For using Stories in People Analytics on Microsoft based Operating Systems, the recommended power option is the
"High Performance" mode for improved Javascript performance.

Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

Related Information

Supported Desktop Browsers for SAP SuccessFactors [page 4]

Supported Mobile Browsers for SAP SuccessFactors [page 6]
Supported Workstation Operating Systems for SAP SuccessFactors [page 7]
Mobile Application Support for SAP SuccessFactors [page 10]
Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
Adobe Acrobat Reader for SAP SuccessFactors [page 12]
Supported Document Types in SAP SuccessFactors [page 13]
Accessibility Support in SAP SuccessFactors [page 13]

IT Landscape Requirements for SAP SuccessFactors

Client-Side Requirements for SAP SuccessFactors HXM Suite PUBLIC 9
2.5 Mobile Application Support for SAP SuccessFactors

SAP SuccessFactors Mobile app supports these configurations.

Hardware/Software What's Supported Additional Information

Devices iOS: Android Notes:

• iPhone 8 and above • Due to the breadth of the Android

• iPad 5 and above device market and carrier and OEM
modifications to Android, SAP Suc-
• iPad Air 3 and above
cessFactors Mobile tests a subset
• iPad mini 5 and above
of the most popular devices. We up-
• iPad Pro date the list of supported devices

Android: each quarter.

• Unlisted devices should work if
See the Additional Information column
they meet the minimum OS require-
for important Android notes.
ments.
• Samsung Galaxy S10, S10+, S20 FE, • Some Android tablets meet these
S21, S21+, S21 FE, S21 Ultra, S22, requirements and will be able to run
S22+, S22 Ultra, S23 Ultra the SAP SuccessFactors Mobile app,
• Samsung Galaxy A03, A12, A13, A21, but they are not officially supported.
A22, A32, A33, A51, A52, A52s, A53,
A71, A73  Note
• Huawei P30 Pro Some Android device manufactur-
• Xiaomi Redmi 9, 10X ers include software that is typically
used to gain root access to the de-
• Xiaomi Redmi Note 8, Note 8 Pro vice, as part of their ROM image. If
and above the SAP SuccessFactors Mobile app
• Xiaomi Poco X3 Pro detects this suspicious software, the
user will not be able to activate on
• OnePlus Nord CE 2 Lite
that device.
• OPPO A54

Operating Systems • iOS 16.0 and above

• Android OS 9.0 and above

Transport layer security (TLS) TLS 1.2 Apple iOS 9.0 and later devices require
TLS 1.2 from the server.

Additional Information

The SAP SuccessFactors Mobile app is released every month, except for January. To ensure that all SAP
SuccessFactors Mobile app users can take advantage of data protection and privacy features, and the
latest security updates, features, and bug fixes, customers should ensure that employees' devices are set to
automatically upgrade (or have a process to upgrade employees' devices) to the most current release of the Mobile
app. Releases of the Mobile app are available by downloading the app through the Apple App Store and Google Play

IT Landscape Requirements for SAP SuccessFactors

10 PUBLIC Client-Side Requirements for SAP SuccessFactors HXM Suite
Store. For users in China, the Android app can be downloaded through the Tencent App Store. SAP SuccessFactors
Mobile provides support for only the current version of the app and the two previous versions. Support for older
versions may change at SAP’s sole discretion at any time.

Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

Related Information

Supported Desktop Browsers for SAP SuccessFactors [page 4]

Supported Mobile Browsers for SAP SuccessFactors [page 6]
Supported Workstation Operating Systems for SAP SuccessFactors [page 7]
Browser Configuration Requirements for SAP SuccessFactors [page 8]
Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
Adobe Acrobat Reader for SAP SuccessFactors [page 12]
Supported Document Types in SAP SuccessFactors [page 13]
Accessibility Support in SAP SuccessFactors [page 13]

2.6 Oracle Java Runtime Environment (JRE) for SAP

SuccessFactors

SAP SuccessFactors requires JRE in these cases.

Required cases for JRE

• 1.6 or higher to use video and audio recording

• 1.8 to use Plateau Report Designer (PRD) 4.4.1
• Customers who host their content outside of the SuccessFactors domain can elect to require JRE for content
tracking in a cross-domain solution.

Additional Information

To use general functionality, HXM Suite does not require you to install any plug-ins or JRE on end-user systems.

 Note

Due to recent changes in Java security policy and Oracle's introduction of the JRE security baseline concept,
you may have to upgrade your client JRE to the most recent version so that these JRE-dependent functions
work correctly.

IT Landscape Requirements for SAP SuccessFactors

Client-Side Requirements for SAP SuccessFactors HXM Suite PUBLIC 11
Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

Related Information

Supported Desktop Browsers for SAP SuccessFactors [page 4]

Supported Mobile Browsers for SAP SuccessFactors [page 6]
Supported Workstation Operating Systems for SAP SuccessFactors [page 7]
Browser Configuration Requirements for SAP SuccessFactors [page 8]
Mobile Application Support for SAP SuccessFactors [page 10]
Adobe Acrobat Reader for SAP SuccessFactors [page 12]
Supported Document Types in SAP SuccessFactors [page 13]
Accessibility Support in SAP SuccessFactors [page 13]

2.7 Adobe Acrobat Reader for SAP SuccessFactors

SAP SuccessFactors requires Adobe Acrobat Reader in some cases.

We require Adobe Acrobat Reader 11 or later to open .pdf document.

Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

Related Information

Supported Desktop Browsers for SAP SuccessFactors [page 4]

Supported Mobile Browsers for SAP SuccessFactors [page 6]
Supported Workstation Operating Systems for SAP SuccessFactors [page 7]
Browser Configuration Requirements for SAP SuccessFactors [page 8]
Mobile Application Support for SAP SuccessFactors [page 10]
Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
Supported Document Types in SAP SuccessFactors [page 13]
Accessibility Support in SAP SuccessFactors [page 13]

IT Landscape Requirements for SAP SuccessFactors

12 PUBLIC Client-Side Requirements for SAP SuccessFactors HXM Suite
2.8 Supported Document Types in SAP SuccessFactors

SAP SuccessFactors supports these document types.

Except as indicated below, SAP SuccessFactors supports the following document types: BMP, CSV, DOC, GIF, HTM,
HTML, JPEG, JPG, PDF, PNG, PPT, RTF, TXT, XLS, XML. In addition,SAP SuccessFactors Learning supports XLSX
and DOCX.

Analytics supports the document types shown in the following table.

Online Report De-

signer
Ad Hoc Report
(Ad Hoc Live Data Builder & Busi-
& Employee Cen- ness Intelligence
Ad Hoc Report Tiles & Dash- tral Advanced Re- and Reporting Tool Pixel Perfect Tal-
Builder boards porting) (BIRT) LMS & BIRT ent Cards

CSV, PDF, PPT, XLS, Online only CSV, DOC, DOCX, CSV, PDF, PPT, XLS, CSV, HTML, PDF PDF, PPT, PPTX,
XLSX PDF, PPT, XLS, XLSX, Word
XLSX

Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

Related Information

Supported Desktop Browsers for SAP SuccessFactors [page 4]

Supported Mobile Browsers for SAP SuccessFactors [page 6]
Supported Workstation Operating Systems for SAP SuccessFactors [page 7]
Browser Configuration Requirements for SAP SuccessFactors [page 8]
Mobile Application Support for SAP SuccessFactors [page 10]
Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
Adobe Acrobat Reader for SAP SuccessFactors [page 12]
Accessibility Support in SAP SuccessFactors [page 13]

2.9 Accessibility Support in SAP SuccessFactors

SAP SuccessFactors is committed to accessible software.

Our products are guided by the Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the harmonized EN
301 549 including WCAG 2.1 Level AA. Detailed documents, such as the Voluntary Product Accessibility Template
(VPAT), are available from your account executive upon request.

IT Landscape Requirements for SAP SuccessFactors

Client-Side Requirements for SAP SuccessFactors HXM Suite PUBLIC 13
You may need to provide client-side, third-party assistive technologies, such as the JAWS® screen reader, to be
used in conjunction with SAP SuccessFactors software. We use the screen reader JAWS® to test the interoperability
of our software with assistive technologies (AT), according to WCAG guidelines, but software operation isn’t
restricted to JAWS®. We follow recommendations of W3C and its related WCAG and HTML standards to realize
accessibility to the extent stated in VPAT documents.

 Note

For more information, refer to accessibility documentation: Accessibility in SAP SuccessFactors

Parent topic: Client-Side Requirements for SAP SuccessFactors HXM Suite [page 4]

Related Information

Supported Desktop Browsers for SAP SuccessFactors [page 4]

Supported Mobile Browsers for SAP SuccessFactors [page 6]
Supported Workstation Operating Systems for SAP SuccessFactors [page 7]
Browser Configuration Requirements for SAP SuccessFactors [page 8]
Mobile Application Support for SAP SuccessFactors [page 10]
Oracle Java Runtime Environment (JRE) for SAP SuccessFactors [page 11]
Adobe Acrobat Reader for SAP SuccessFactors [page 12]
Supported Document Types in SAP SuccessFactors [page 13]

IT Landscape Requirements for SAP SuccessFactors

14 PUBLIC Client-Side Requirements for SAP SuccessFactors HXM Suite
3 Checking Your Network Bandwidth

Determine whether your network supports the optimal application performance by using the SAP SuccessFactors
Diagnostics tool.

Context

In general, SAP SuccessFactors HXM Suite requires no more bandwidth than is required to surf the Internet. All
application modules are designed for speed and responsiveness with minimal use of large graphic files.

Procedure

1. Open the diagnostics tool by the URL: https://<domain>/diagnostic/main.

Use the same domain of the URL that you use to access the SAP SuccessFactors solutions.
2. Go to the Tests section of the tool and run the bandwidth test.

Results

The tool returns your network bandwidth. If it is below 300 Kbits per second, it is highlighted in red. When it is
below 300 Kbits per second, the performance of the application is compromised. To optimize the performance,
contact your IT support to increase the network bandwidth.

IT Landscape Requirements for SAP SuccessFactors

Checking Your Network Bandwidth PUBLIC 15
4 Allow Listing

4.1 Verify Akamai Allow Listing with a Browser

Click each of these URLs from within your corporate network to test if your allowlist and blocklist enable SAP
SuccessFactors to work with Akamai.

Procedure

1. Open a browser from within your corporate network.

2. Click all of the links below.

https://validate-akamai.successfactors.com/akamai/validateAkamai.html

https://validate-akamai.successfactors.eu/akamai/validateAkamai.html

https://validate-akamai.sapsf.eu/akamai/validateAkamai.html

https://validate-akamai.sapsf.com/akamai/validateAkamai.html

https://validate-akamai.sapsf.cn/akamai/validateAkamai.html

After clicking each of the links, you should see a success message that reads Akamai validation completed
successfully!

Next Steps

If you do not get a message that says Akamai validation completed successfully!, then the Akamai connection
wasn't successful. Check your allow and deny lists to make sure that you can reach the domains below. Work with
your IT infrastructure team to add them to your list of domains that employees are allowed to visit (the allowlist).

• successfactors.com
• sapsf.com
• successfactors.eu
• sapsf.eu

IT Landscape Requirements for SAP SuccessFactors

16 PUBLIC Allow Listing
4.2 Verify SFAPI/OData Allow Listing with a Browser

Click each of these URLs from within your corporate network to test if your allowlist and blocklist enable SAP
SuccessFactors API calls from within your network using your browsers.

Procedure

1. Look up the domain for your data center's API calls.

2. Open a browser from within your corporate network, and in the site address bar of the Browser, paste a URL in
the pattern https://test.<your Data Center Domain>/domain/validation.html.

For example, if you look up your data center domain and your domain is successfactors.com, then you
paste https://test.successfactors.com/domain/validation.html.
3. Press ENTER to go to the site.

If you’re able to reach the domain, you see a success message that reads Testing is successful.

Next Steps

If you don't get a message that says Testing is successful, then the API connection wasn't successful. Check your
allow and deny lists to make sure that you can reach the API Domain. Work with your IT infrastructure team to add
it to your list of domains that employees are allowed to go outbound from your network.

Related Information

List of SAP SuccessFactors API Servers [page 21]

4.3 Verify SFAPI/OData Allow Listing With CURL

If you are triggering API calls to SAP SuccessFactors from a third party, or outside of a browser, you can use CURL
to verify that you can connect.

Prerequisites

Download and install CURL, a common utility for making command-line HTTP calls.

IT Landscape Requirements for SAP SuccessFactors

Allow Listing PUBLIC 17
Procedure

1. On a terminal to use CURL at the location where your calls originate.

For example, if you are calling from a third party server, open a terminal on the server.
2. Type CURL https://test.<your API domain>/domain/validation.html.

For example, if your domain is successfactors.com, then type CURL https://

test.successfactors.com/domain/validation.html.
3. Press ENTER .

CURL returns a response. It is successful if you see Testing is successful.

Next Steps

If you don't get a message that says Testing is successful, then the API connection wasn't successful. Check your
allow and deny lists to make sure that you can reach the API Domain. Work with your IT infrastructure team to add
it to your list of domains that employees are allowed to go outbound from your network.

Related Information

List of SAP SuccessFactors API Servers [page 21]

4.4 Allowlist Methods for Email from SAP SuccessFactors

To prevent email spam, spoofing, social engineering, phishing attacks, and to make sure that your own spam filters
don't filter valid messages from SAP SuccessFactors, use an allowlist method for the email senders.

Use one of the following methods so that your email servers can distinguish valid email sent by SAP
SuccessFactors from email social engineering attacks like phishing and spoofing. These methods identify the
origins of SAP SuccessFactors email so that your system can trust them. If you don't use one of the methods we
describe, you might:

• Inadvertently filter out valid SAP SuccessFactors emails. Your spam filters or other security systems won't
recognize our email messages as valid. They could be blocked or go to quarantine depending on your
configuration.
• Receive email that looks like it’s coming from SAP SuccessFactors but is in fact spoofed by a third party
engineering an attack.

 Restriction

We no longer advocate for single sender as a leading practice for resolving spoofing issues. In some cases, if
you use single sender, your email can be blocked.

IT Landscape Requirements for SAP SuccessFactors

18 PUBLIC Allow Listing
Domain Key Identified Mail (DKIM)

Domain Key Identified Mail (DKIM) allows senders to associate a domain name with an email message to validate
its authenticity with a key. SAP SuccessFactors can configure DKIM for your system. We provide you with the public
key and manage the key.

Sender Policy Framework (SPF)

Sender Policy Framework (SPF) verifies that the sender IP Address is allowed to send email from a domain against
the Domain Name System (DNS). SAP SuccessFactors sends email from a set list of IP addresses. When you add
them to your SPF configuration, you verify that the SAP SuccessFactors is the true sender of email from SAP
SuccessFactors domains.

4.4.1 Requesting a Key for Domain Key Identified Mail (DKIM)

To use Domain Key Identified Mail (DKIM) with SAP SuccessFactors, you request a key from cloud services.

Prerequisites

Before you request the key, gather this information:

• Your SAP SuccessFactors Company ID

• Your datacenter
• The full list of domains used by your users (for example, @company.com)

Procedure

1. Create a ticket with component LOD-SF-PLT-SEC to request a DKIM key.

2. In the ticket, add the information that you gathered, and then submit it.

The SAP SuccessFactors team returns the key to you or seeks additional information or policy clarification.
3. Use the key in your DKIM TXT record.
4. Update the ticket to let SAP SuccessFactors know that you have added the key.

IT Landscape Requirements for SAP SuccessFactors

Allow Listing PUBLIC 19
4.4.2 Adding Listings for Sender Policy Framework

If you elect to use Sender Policy Framework (SPF) to prevent spam and spoofing from SAP SuccessFactors, you
must add a Domain Name System (DNS) listing that matches your data center.

Prerequisites

Before you can add the DNS listing for SPF, you must know your data center. If you don’t know your data center,
you can ask support.

Context

Sender Policy Framework (SPF) operates with Domain Name System (DNS). We’ve registered the IP addresses of
our email servers. You include that registry so that your system recognizes the IP addresses as valid senders.

As an alternative, use Domain Key Identified Mail (DKIM). DKIM is independent of data center numbers because it
uses a key in the message header. We manage the private key and provide you with the public key. If you move to a
new data center, we manage the key so that your service isn't interrupted.

 Restriction

We don’t support IP addresses in URLs as part of our reference architecture. Use domain names instead. If you
think you have a special case that requires IP addresses instead of domain names, contact Product Support.

Procedure

In your DNS, add the line include:_spf-dc<data center number>.sapsf.com where <data center
number> is the data center of your SAP SuccessFactors system.

For example, a company in data center 60 adds the following (where <other includes> are all the other include
statements for all other registered domains):

 Sample Code

v=spf <other includes> include:_spf-dc60.sapsf.com -all

Related Information

Allowlist Methods for Email from SAP SuccessFactors [page 18]

Requesting a Key for Domain Key Identified Mail (DKIM) [page 19]

IT Landscape Requirements for SAP SuccessFactors

20 PUBLIC Allow Listing
4.5 List of SAP SuccessFactors API Servers

Learn about the API servers of your company instance and how to construct the endpoint URLs.

Endpoint URL Patterns

 Restriction

We don’t support IP addresses in URLs as part of our reference architecture. Use domain names instead. If you
think you have a special case that requires IP addresses instead of domain names, contact Product Support.

Protocol URL Pattern Endpoint Example

OData v2 /odata/v2/ https://api17.sapsf.com/odata/v2/

OData v4 /odatav4/ https://api17.sapsf.com/odatav4/

REST /rest/ https://api17.sapsf.com/rest/

SFAPI /sfapi/v1/soap https://api17.sapsf.com/sfapi/v1/soap

WSDL /sfapi/v1/soap?wsdl https://api17.sapsf.com/sfapi/v1/soap?wsdl

API Servers

Here's a list of API servers and mTLS certificate servers for SAP SuccessFactors data centers. Use search and filter
to find the corresponding servers for your company.

To view the timezone information of an API server, go to your company login page or open your account on the
header bar after login, and choose Show version information.

mTLS Certifi-
Data Center Environment Platform Location API Server cate Server

DC2 (DC57) Production Google Cloud Eemshaven, The https:// https://

Platform Netherlands api2.successfactors.eu/ api2.cert
.successf
actors.eu

DC2 (DC57) Sales Demo Google Cloud Eemshaven, The https:// https://
Platform Netherlands apisalesdemo2.successfactor apisalesd
s.eu/ emo2.cert
.successf
actors.eu

IT Landscape Requirements for SAP SuccessFactors

Allow Listing PUBLIC 21
 mTLS Certifi-
Data Center Environment Platform Location API Server cate Server

DC2 (DC57) Preview Google Cloud Eemshaven, The https:// https://

Platform Netherlands api2preview.sapsf.eu/ api2previ
ew.cert.s
apsf.eu

DC4 (DC68) Production Azure Chandler, Arizona, https:// https://

US api4.successfactors.com/ api4.cert
.successf
actors.co
m

DC4 (DC68) Preview Azure Chandler, Arizona, https:// https://

US api4preview.sapsf.com/ api4previ
ew.cert.s
apsf.com

DC8 (DC70) Production Azure Ashburn, Virginia, https:// https://

US api8.successfactors.com/ api8.cert
.successf
actors.co
m

DC8 (DC70) Sales Demo Azure Ashburn, Virginia, https:// https://

US apisalesdemo8.successfactor api8sales
s.com/ .cert.suc
cessfacto
rs.com

DC8 (DC70) Preview Azure Ashburn, Virginia, https:// https://

US api8preview.sapsf.com/ api8previ
ew.cert.s
apsf.com

DC10 (DC66) Production Azure Sydney, Australia https:// https://

api10.successfactors.com/ api10.cer
t.success
factors.c
om

DC10 (DC66) Preview Azure Sydney, Australia https:// https://

api10preview.sapsf.com/ api10prev
iew.cert.
sapsf.com

DC12 (DC33) Production Rot, Germany https:// https://

api012.successfactors.eu/ api012.ce
rt.succes
sfactors.
eu

IT Landscape Requirements for SAP SuccessFactors

22 PUBLIC Allow Listing
 mTLS Certifi-
Data Center Environment Platform Location API Server cate Server

DC12 (DC33) Preview Rot, Germany https:// https://

api12preview.sapsf.eu/ api12prev
iew.cert.
sapsf.eu

DC15 (DC30) Production Shanghai, China https://api15.sapsf.cn/ https://

api15.cer
t.sapsf.c
n

DC15 (DC30) Preview Shanghai, China https:// https://

api15preview.sapsf.cn/ api15prev
iew.cert.
sapsf.cn

DC17 (DC60) Preview Azure Toronto, Canada https:// https://

api17preview.sapsf.com/ api17prev
iew.cert.
sapsf.com

DC17 (DC60) Production Azure Toronto, Canada https://api17.sapsf.com/ https://

api17.cer
t.sapsf.c
om

DC19 (DC62) Preview Azure Sao Paulo, Brazil https:// https://

api19preview.sapsf.com/ api19prev
iew.cert.
sapsf.com

DC19 (DC62) Production Azure Sao Paulo, Brazil https://api19.sapsf.com/ https://

api19.cer
t.sapsf.c
om

DC22 Preview Dubai, UAE https:// https://

api22preview.sapsf.com/ api22prev
iew.cert.
sapsf.com

DC22 Production Dubai, UAE https://api22.sapsf.com/ https://

api22.cer
t.sapsf.c
om

DC23 Preview Riyadh, Saudi Ara- https:// https://

bia api23preview.sapsf.com/ api23prev
iew.cert.
sapsf.com

IT Landscape Requirements for SAP SuccessFactors

Allow Listing PUBLIC 23
 mTLS Certifi-
Data Center Environment Platform Location API Server cate Server

DC23 Production Riyadh, Saudi Ara- https://api23.sapsf.com/ https://

bia api23.cer
t.sapsf.c
om

DC40 Sales Demo Azure https:// https://

api40sales.sapsf.com api40sale
s.cert.sa
psf.com

DC41 Preview Azure US East https:// https://

api41preview.sapsf.com api41prev
iew.cert.
sapsf.com

DC41 Production Azure US East https://api41.sapsf.com https://

api41.cer
t.sapsf.c
om

DC44 (DC52) Preview Google Cloud Singapore https:// https://

Platform api44preview.sapsf.com/ api44prev
iew.cert.
sapsf.com

DC44 (DC52) Production Google Cloud Singapore https://api44.sapsf.com/ https://

Platform api44.cer
t.sapsf.c
om

DC47 Preview Canada Central https:// https://

(Microsoft Azure) api47preview.sapsf.com/ api47prev
iew.cert.
sapsf.com

DC47 Production Canada Central https://api47.sapsf.com/ https://

(Microsoft Azure) api47.cer
t.sapsf.c
om

DC50 Preview Google Cloud Aisa Northeast, To- https:// https://

Platform kyo (Google Cloud api50preview.sapsf.com api50prev
Platform) iew.cert.
sapsf.com

DC50 Production Google Cloud Aisa Northeast, To- https://api50.sapsf.com https://

Platform kyo (Google Cloud api50.cer
Platform) t.sapsf.c
om

IT Landscape Requirements for SAP SuccessFactors

24 PUBLIC Allow Listing
 mTLS Certifi-
Data Center Environment Platform Location API Server cate Server

DC55 Preview Google Cloud Europe West 3 https:// https://

Platform api55preview.sapsf.eu/ api55prev
iew.cert.
sapsf.eu

DC55 Production Google Cloud Europe West 3 https://api55.sapsf.eu/ https://

Platform api55.cer
t.sapsf.e
u

DC4 (DC68) Sales Demo Azure US East 2 https:// https://

api68sales.successfactors.c api68sale
om s.cert.su
ccessfact
ors.com/

DC74 Preview Azure Zurich, Switzer- https:// https://

land api74preview.sapsf.eu api74prev
iew.cert.
sapsf.eu

DC74 Production Azure Zurich, Switzer- https://api74.sapsf.eu https://

land api74.cer
t.sapsf.e
u

IT Landscape Requirements for SAP SuccessFactors

Allow Listing PUBLIC 25
5 Integration Center Enterprise Check

Assure that Integration Center URLs follow policy.

When using Integration Center, we have a set of policies that define URL usage - and usage of integration center in
general. Integration center is a hub of your enterprise with SAP SuccessFactors.

5.1 Source Settings For Your Inbound Integration

You can enter the File Server Settings, File Name and Folder Settings, and Advanced Settings on the Source Settings
page for the input source of the integration. These settings are required for your integration to run successfully.

File Server Settings

Field Description

SFTP Server Host Address Enter the Domain name/internet address and port of the SFTP
server.

IT Landscape Requirements for SAP SuccessFactors

26 PUBLIC Integration Center Enterprise Check
 Field Description

Port For new integrations, you can't edit the SFTP port value. The
port value is set to 22 by default.

For existing integrations, you can change the existing port

value only to 22. This value will be set as default and can’t
be changed.

During an integration definition import, if the existing port

value is a different value, then the port value will be changed
and defaulted to 22.

SFTP User Name Enter the User name for the SFTP account.

 Note
You can use the period '.' character, the underscore '_'
character, and the hyphen '-' character to create your
SFTP User Name.

SFTP Password Enter the password for the SFTP account. This field supports
alphanumeric characters that are case sensitive. This field
does not support special characters (@,#,$%,^,&*).

Authentication Key From this dropdown you can select any previously generated
SSH key or the No key Authentication option. This key is used
for authentication while writing to the Destination. If you want
to generate a new SSH key, click Generate SSH Key option
which navigates you to the page where new SSH keys are gen-
erated.

IT Landscape Requirements for SAP SuccessFactors

Integration Center Enterprise Check PUBLIC 27
File Name and Folder Settings

Field Description

File Name Prefix Enter the name of the template to be used as the file name.
This name must be the same as the file in SFTP location.

You can process multiple files by adding wild cards (? *) to the

file name (s) that need to be processed.

For example:

If the File Name Prefix is Person_Data_*, it means that all files

in the SFTP location, of file name starting with Person_Data_
will be processed sequentially. File names, Person_Data_USA,
Person_Data_UK and so on will be processed.

If the File Name Prefix is Person_Data_?, it means that all files

in the SFTP location, of file name starting with Person_Data_
and ending with only one character will be processed sequen-
tially. File names, Person_Data_1, Person_Data_2 and so on will
be processed. In this case file name Person_Data_10 will not be
processed since it ends with two characters.

 Note
1. Make sure that the case used in the extension of
the SFTP File Name Prefix is consistent with the File
Extension field. For example, if you select the File
Extension as csv, then the extension in the File Name
Prefix should be .csv.
In case you type in any other extension, it should
match the case of the actual file extension in the SFTP
directory.
For example, if you enter CSV in the File Extension
field, then the extension in the SFTP File Name Prefix
should be .CSV.
2. Integration Center does not support blank space
and any other special character other than '_' (under-
score) in the file name.

File Extension Select or enter an extension of the file, excluding the period.
This extension must be the same as the extension of the file in
SFTP location.

 Note
If the outbound file is encrypted and saved with the ex-
tension csv, then in inbound integration, you need to en-
ter csv.pgp in the File Extension field. This will fetch the
csv.pgp file from SFTP location. Also, make sure to provide
the Decryption key in the Advanced Settings section with
the file extension as csv.pgp.

IT Landscape Requirements for SAP SuccessFactors

28 PUBLIC Integration Center Enterprise Check
 Field Description

File Folder Enter the folder name from which the files have to be picked.

Processing Folder Enter the folder name to which the file is moved to after it is
read or processed. Note that write privileges to the folder are
required.

 Note
The processing folder is mandatory if the File Name Prefix
field contains wildcard characters.

Advanced Settings

Field Description

Enable Diagnostics Select this checkbox to save the source data of your integra-
tion in JSON format as a zip file to specified SFTP destination
folder, after executing the integration.

 Note
Selecting this option may affect performance.

Authentication Key Select the authentication key from the dropdown to get au-
thentication so that you can write to the destination and imple-
ment single sign-on by the system administrators or power
users.

File Decryption Select the decryption key from the dropdown to decrypt the
file when reading from the source.

After entering the valid entries, click Next. You will now be on the Scheduling page. See Scheduling your Integration
section for more details.

After you schedule the integration, click Next. You will now be on the Review and Run page. See About Review and
Run section for more details.

IT Landscape Requirements for SAP SuccessFactors

Integration Center Enterprise Check PUBLIC 29
6 Time Synchronization Check

The time synchronization check assures that SAP SuccessFactors is synchronizing to a standard service so that all
times in your enterprise are aligned.

In modern computer networks time synchronization is critical because every aspect of managing, securing,
planning, and debugging a network involves determining when events happen. Time also provides the only frame of
reference between all devices on the network. Without synchronized time, accurately correlating log files between
these devices is difficult, even impossible.

• It is necessary to consider clock synchronization of the cloud service customer’s systems with cloud
service provider’s systems, which run the cloud services used by the cloud service customer. Without such
synchronization, it can be difficult to reconcile events on the cloud service customer’s systems with events on
the cloud service provider’s systems.
• Tracking security breaches, network usage, or problems affecting a large number of components can be nearly
impossible if timestamps in logs are inaccurate. Time is often the critical factor that allows an event on one
network node to be mapped to a corresponding event on another.
• To reduce confusion in shared filesystems, it is important for the modification times to be consistent,
regardless of what machine the filesystems are on.
• Billing services and similar applications must know the time accurately.

Network Time Protocol

Network Time Protocol (NTP) is a protocol used to synchronize computer clock times in a network. It belongs to
and is one of the oldest parts of the TCP/IP protocol suite. The term NTP applies to both the protocol and the
client-server programs that run on computers.

Stratum Level

Network Time Protocol is a hierarchical protocol and is divided into stratum which define the distance from the
reference clock. A reference clock source that relays UTC (Coordinated Universal Time) time and has little or no
delay is known as a stratum-0 device.

IT Landscape Requirements for SAP SuccessFactors

30 PUBLIC Time Synchronization Check
6.1 NTP Services for Time Synchronization

Depending on where your SAP SuccessFactors system is hosted, it can synchronize time from one of these
speciific NTP services.

SAP Converged Cloud NTP Service

The SAP Converged Cloud NTP Service gets the time from the regional ntp.org pools. For example, for the ap-
au-1 region, 0-3.au.pool.ntp.org is used, and for the eu-de-1 region, 0-3.de.pool.ntp.org is used.

Hyperscaler NTP Service

If your SAP SuccessFactors system is hosted on a hyperscaler platform, you can synchronize the clock of your local
IT system to one of the below NTP services, depending on your configuration.

Hyperscaler Name

Microsoft Azure time.microsoft.akadns.net

Google Cloud Platform (GCP) metadata.google.internal

IT Landscape Requirements for SAP SuccessFactors

Time Synchronization Check PUBLIC 31
7 Certificate Renewal

If you receive certificate renewal notification and if you’re using a SAP SuccessFactors integration with SAP or
Non-SAP application through APIs (SFAPI/OData API/Adhoc API), then renew the certificates to assure continued
service.

Your internal IT resources conduct certificate renewals. Certificates are used for the SSL/TLS handshake for
secure system protocols before allowing connection to or from the system. SAP SuccessFactors requires an SSL
handshake for any system to connect.

• Update the SAP SuccessFactors Domain certificate for API endpoint URL.
• Check the list of potential certificate information. 2533915

Certificate Renewal Timing

Renew your certificate as soon as possible. You can maintain both the old certificate and the new one at the same
time on your middleware storage so that you don’t have down time at the transition. After the transition, you can
remove the old certificate. You can read about both the timing of the certificates and the certificates themselves in
2533915 . Take note of the following milestones in the policy:

• When SSL Certificate Renewal Notifications are published before the certificate expiration date.
• When we initiate the deployment process before the certificate expiration date.
• When the certificate is available before expiration.
• When you receive a final notification before the deployment of the certificate.

Who Is Impacted by Certificate Renewal

You’re impacted by certificate renewal if the following are true:

• You’re using our APIs (SFAPI/Odata API/Adhoc API) and have an integration scenario in your SAP
SuccessFactors instance.
• You’re using middleware for your integration.
• The SAP SuccessFactors API domain for which the certificate is being renewed (*.successfactors.eu) is same
as the domain you’re using to access/connect to SAP SuccessFactors API server using API URL as the
endpoint URL.

 Note

If you use SAP Business Technology Platform, if you already installed the SAP SuccessFactors root certificate
in your tenant, then you aren't impacted.

IT Landscape Requirements for SAP SuccessFactors

32 PUBLIC Certificate Renewal
Responsibilities for Certificate Uploads

You’re responsible for certificate upload, even if you’re using middleware supported by SAP.

Single-Sign On

This certificate renewal is for API integrations and doesn’t affect Single-Sign On (SSO).

Certificate Renewal and SAP SuccessFactors Learning

If the certificate renewal is for the *.successfactors.com/eu domain, then SAP SuccessFactors Learning isn't
impacted.

If the certificate renewal is for *.plateau.com then SAP SuccessFactors Learning is impacted.

Related Information

List of SAP SuccessFactors API Servers [page 21]

IT Landscape Requirements for SAP SuccessFactors

Certificate Renewal PUBLIC 33
8 Cookie Handling in SAP SuccessFactors

In SAP SuccessFactors, cookies are created in different modules for different usages and purposes. Find out what
cookies are available for each solution in the SAP SuccessFactors HXM Suite.

Cookies in SAP SuccessFactors Platform

SAP SuccessFactors Platform cookies are placed for every use of an SAP SuccessFactors Platform module.
Additional cookies can be set if a module has features that are built on a different application server environment.
In case of integration with other SAP cloud solutions or SAP solution extensions provided by third-party vendors,
additional cookies might be required by these solutions. If a third-party cookie is present, it's indicated in the
Purpose and Usage column in the cookie list.

For more information about first-party and third-party cookies, see the Related Information section.

Cookies in SAP SuccessFactors Learning

SAP SuccessFactors Learning is a loosely coupled module provided from a different application server
environment. Therefore, Learning manages a set of separate cookies.

Cookies in SAP SuccessFactors Recruiting

In SAP SuccessFactors Recruiting, additional cookies are used in career sites built with Career Site Builder.

Cookies in SAP SuccessFactors Onboarding

SAP SuccessFactors Onboarding is provided from a different application server environment. Therefore,
Onboarding manages a set of separate cookies.

Cookies in SAP SuccessFactors Workforce Analytics

SAP SuccessFactors Workforce Analytics is provided from a different application server environment. Therefore,
Workforce Analytics manages a set of separate cookies.

IT Landscape Requirements for SAP SuccessFactors

34 PUBLIC Cookie Handling in SAP SuccessFactors
Cookies in SAP SuccessFactors Employee Central Payroll

SAP SuccessFactors Employee Central Payroll integrates with SAP systems. Additional cookies are placed when a
user connects to an SAP ABAP system.

Cookies in SAP SuccessFactors People Analytics

SAP SuccessFactors People Analytics consumes services provided by other applications. Therefore, additional
cookies are placed when such services are invoked.

What Are Cookies? [page 35]

Cookies are small files placed on your device (computer, tablet or smartphone). When you access a
website, a cookie is placed on your device and it will send information to the party that placed the cookie.
This topic explains different types of cookies and the attributes that define them.

List of Cookies in SAP SuccessFactors [page 36]

This table lists all available cookies in SAP SuccessFactors applications.

8.1 What Are Cookies?

Cookies are small files placed on your device (computer, tablet or smartphone). When you access a website, a
cookie is placed on your device and it will send information to the party that placed the cookie. This topic explains
different types of cookies and the attributes that define them.

Session and persistent cookies

Our websites may place session and persistent cookies on your device. The difference between a session and a
persistent cookie relates to the length of time the cookie lasts. Session cookies are cookies that typically last for
as long as you are using your browser, or browser session. When you end your browser session, the cookie expires.
Persistent cookies, as the name implies, are persistent and will last after you close your browser. This allows for
quicker and often more convenient access to our websites.

Cookie security

Our web servers make sure that sensitive cookies are sent securely and free from unintended access and scripts by
setting the HttpOnly and Secure attributes.

• The HttpOnly attribute guarantees that cookies can't be accessed from scripts on the client side.
• The Secure attribute ensures that cookies can only be sent through secure channels, such as https.

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 35
If a cookie contains personal information and needs to be stored at the client side, the information is always
encrypted and users are reminded about the data privacy.

Cookie domain

The SameSite attribute allows web servers to specify whether a cookie can be used across different domains. The
possible values are:

• None: The cookie can be sent across domains.

• Strict: The cookie can only be sent to the same domain from which it's created.
• Lax (default): The cookie can be sent when the user navigates to the cookies origin domain.

First-party and third-party cookies

SAP websites have first-party cookies and SAP sometimes allows third parties to place cookies on your device. The
difference between a first-party cookie and a third-party cookie relates to who places the cookie on your device.
First-party cookies are cookies that are specific to the website that created them. These cookies enable SAP to
operate an efficient service and to track patterns of user behavior to SAP websites.

Third-party cookies are placed on your device by a third party (that is, not by SAP). While SAP might allow third
parties to access SAP websites to place a third-party cookie on your device, SAP does not retain control over the
information supplied by the cookies, nor does SAP retain access to this information. This information is controlled
wholly by that third party according to the respective privacy policy of the third party. These cookies may change as
the third parties make changes to their applications without notifying SAP.

Parent topic: Cookie Handling in SAP SuccessFactors [page 34]

Related Information

List of Cookies in SAP SuccessFactors [page 36]

8.2 List of Cookies in SAP SuccessFactors

This table lists all available cookies in SAP SuccessFactors applications.

Some columns are hidden by default. Choose Show/hide columns to display them.

IT Landscape Requirements for SAP SuccessFactors

36 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

HXM Session Yes Yes None No Internal traffic routing. When a Browser
route
Suite
user vis- session
its a
page.

HXM
JSESSI Session Yes Yes None No Used to keep the login infor- When a Browser
Suite
ONID mation. browser session
session
starts.

HXM
ECJSES Session Yes Yes None No Used to keep the login infor- When a Browser
Suite
SIONID mation like JSESSIONID, user session
except this cookie is for Em- uses an
ployee Central. Em-
ployee
Central
function-
ality.

HXM
zsessi Session Yes Yes None No Cross application session When a Browser
Suite
onid management. browser session
session
starts.

HXM
BIGipS Session No No None No Internal traffic routing. When a Browser
Suite
erver browser session
 Note session

This cookie is depre- starts.

cated by route.

HXM
Optier Persis- No No No Troubleshooting and analy- Created 30 sec-
Suite
RQUUID tent sis. for every onds
page re-
sponse.

HXM
cookie Session Yes Yes No Used for clickjacking filter. When a Browser
Suite
_click browser session
The cookie keeps a security
jack_t session
token for clickjacking pre-
oken starts.
vention.

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 37
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

HXM When a
loginM Configu- Yes Yes None No Authentication. PWD:
Suite user logs
ethodC rable The cookie indicates in.
browser
ookieK session
whether the login method is
ey SSO or PWD. SSO: 2
years

HXM
deepli Session Yes Yes No Deep link redirection. When a Browser
Suite
nkCook user di- session
ieKey rectly ac- or after
cesses a the redi-
page rection
through for au-
a deep thentica-
link tion oc-
where curs
authenti-
cation is
required
for the
page.

The
cookie is
removed
after the
redirec-
tion for
authenti-
cation
occurs.

HXM
assert Persis- Yes Yes None No Authentication. Created 2 years
Suite
ingPar tent The cookie is used to keep
when
tyCook SAML
the SAML asserting party
ieKey SSO is
name. The value is provided
used.
by customer. Normally, it
is a domain name used to
identify the party.

IT Landscape Requirements for SAP SuccessFactors

38 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

HXM
ms_coo Session No No No Used for Media Service. When a Browser
Suite
kie_se Media session
This cookie is used to de-
t Service
tect if a browser allows
widget is
third-party cookies when a
ren-
widget is rendered in iFrame
dered.
mode. The value is boolean.

HXM
bizxCo Persis- Yes Yes No To remember the company Created 1 year
Suite
mpanyI tent ID of the current login. when a
d valid
company
is pro-
vided by
the user.

HXM
bizxTh Session Yes Yes No To remember the logged- Created Browser
Suite
emeId in user's preferred theme when a session
ID, whose corresponding user logs
theme data contains logo in or
information. When the user changes
logs out or loses the login the
session in a browser ses- theme.
sion (such as a browser
window), the server knows
what the user's preferred
theme is.

HXM Persis- No No No Used for trouble shooting Created 1 minute

<URL
Suite
path tent and analysis. for every
of page re-

page>- sponse.

markFr
omServ
er

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 39
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

HXM
perflo Session No No No Used for trouble shooting When the Browser
Suite
g- and analysis. user session
versio adds the

n query
parame-
ter ?
perflo
g-
versio
n to the
URL.

Learning
BIGipS Session No Used for internal traffic Set by Browser
erverP routing. the VIP in session
_<labe the Ops

l>- land-
scape.
<port>

Learning
DEEP_U Session No To support deep link to pa- When a Browser
RL ges with SSO. user di- session
rectly ac-
Expires
cesses a
immedi-
page
ately
through
a deep
link
where
authenti-
cation is
required
for the
page.

The
cookie is
only valid
for the
redirec-
tion and
expires
immedi-
ately.

IT Landscape Requirements for SAP SuccessFactors

40 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Learning
JSESSI Session Yes Yes No Used for session manage- When a Browser
ONID ment. user vis- session
its the
Learning
site.

Learning
SKIP_L Session No Used for maintenance man- When a Browser
MS_MAI agement. user vis- session
NT_NOT its the

IFY Learning
site dur-
ing the
mainte-
nance
period.

Learning
SITE_I Session No To keep track of the current When Browser
D Learning external site ID. user session
uses the
Learning
external
site func-
tionality.

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 41
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Learning PSA_CP Session No To keep track of current When a Browser

NT_TYP launched course informa- user session
E_ID tion. launches
PSA_CP a con-
These cookies are intended
NT_ID tent.
for external content integra-
PSA_CP
tion.
NT_REV
_DATE Data provided for external
PSA_CP content.
NT_REV
Component type ID
_NUMBE
( PSA_CPNT_TYPE_ID )
R
Component ID
PSA_ST ( PSA_CPNT_ID )
UD_CPN
Component revision date
T_ID
( PSA_CPNT_REV_DATE )
PSA_ST Component revision num-
UD_CPN ber
T_MOD_ ( PSA_CPNT_REV_NUMBE
ID R)
Content object stu-
dent component ID
( PSA_STUD_CPNT_ID )
Content object student
component module ID
( PSA_STUD_CPNT_MOD_
ID )

Learning PSA_ST Session Yes Data provided for external Configu- Browser
UD_ID content. rable session
PSA_CU
The login student ID By de-
RRENT_
( PSA_STUD_ID ) fault,
STUD_I
D The current student ID these

PSA_ST ( PSA_CURRENT_STUD_I cookies

D) are not
UD_NAM
set.
E The user name who
PSA_WE launched the course
BROOT ( PSA_STUD_NAME )
The content root directory
( PSA_WEBROOT )

IT Landscape Requirements for SAP SuccessFactors

42 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Learning
loginM Session No To keep track of the cur- When a Browser
odeCoo rent login mode, whether it user logs session
kie is native login or integrated in.
login.

Learning
TENANT Session No Akamai authentication When Browser
_AUTH_ cookie for iContent hosted user session
COOKIE courses. launches
the iCon-
tent
courses.

Learning Session No To keep track of the login When a Browser

LT
user logs
role, whether it's an admin session
in.
or a user.

Recruit- Session No A standard cookie used for When a Browser

route
ing user vis-
session stickiness between session
its the
the organization's public ca-
career
reer site generated by Ca- site.
reer Site Builder, and pages
generated by SAP Success-
Factors Recruiting, such as
Candidate Profile.

The cookie is required and

can't be disabled.

Recruit- No Used by Akamai to send the When a

career Session Browser
ing user vis-
SiteCo request to the correct data session
its the
center.
mpanyI career
d The cookie is required. If site.

disabled, users can no lon-

ger access the site.

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 43
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Recruit- Persis- No No No Career Site Builder cookie. When a 30 years

rmk12
ing
tent user ac-
(Legacy) This cookie is part
knowl-
of the Legacy Site Banner
edges
settings, and is used only
the
when you have a legacy site
cookie
banner enabled.
policy by
A number that indicates either
whether the user has ac- viewing
knowledged the cookies the
policy banner. If the cookie cookie
isn’t set, then the banner policy or
may be presented. If they dismiss-
cookie is set and its value ing the
is 1, the banner may be sup- banner.
pressed. This cookie per-
sists across user sessions,
no matter which type of
cookies are enabled site-
wide.

Users can disable this

cookie through browsers
or computer configurations.
Once disabled, the cookie
banner will always be
present.

Recruit-
JSESSI Session Yes Yes No Career Site Builder cookie. When a Browser
ing
ONID user vis- session
Single cookie placed on the
its a Ca-
users device during their
reer Site
session so the server can
Builder
identify the user.
site.
This cookie replaces the
RMK0, RMK1, and RMK4
cookies.

This cookie is required for

login.

IT Landscape Requirements for SAP SuccessFactors

44 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Recruit- Load bal- Session No Career Site Builder cookie. When a Browser
ing new user
ancer session
Cookie for session sticki- visits a
cookies.
ness preventing a user from Career
The load bouncing from one instance Site
Builder
balancer to another. Typically issued
site.
cookie by F5.
names
differ in
each
data cen-
ter and
are only
present
in the
Preview
environ-
ment.

Here are
a few ex-
amples:

PERSIS
T (Rack-
space)
cookie
_j2w
(DC10,
DC12)
BIGipS
erver~
partit
ion-
saas_p
rod-
<DC
number
>_stag
ing_lb
-<rand
om
key>
(DC17,
DC19,

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 45
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

and all
new DCs
online af-
ter
DC19)

Recruit- fbsr_[ Third-party cookies set by When a

ing id] Facebook in Career Site user
datr Builder. uses the
locale Face-
c_user  Note book
fr Present only if the third- widget.
xs party applications are
csm configured.
s
lu For details, go to Cookies
wd and other storage technolo-
gies .

Recruit- Persis- No Third-party cookie in Career Created 2 years

_ga
ing
tent Site Builder set by Google by Goo-
Universal Analytics to dis- gle.
tinguish users.

 Note
Present only if the third-
party applications are
configured.

For details, go to Google

Analytics Cookie Usage on
Websites .

IT Landscape Requirements for SAP SuccessFactors

46 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Recruit- Session No Third-party cookie in Career Created 1 minute

_gat
ing
Site Builder set by Google by Goo-
Universal Analytics to dis- gle.
tinguish users.

 Note
Present only if the third-
party applications are
configured.

For details, go to Google

Analytics Cookie Usage on
Websites .

Recruit- linked Session No Third-party cookie in Career Initially Browser

ing in_oau created
Site Builder set by LinkedIn session
th_[id when a
as an OAuth token.
] new user
visits a
 Note Career
Present only if the third- Site
Builder
party applications are
career
configured.
site that
uses the
For details, go to Cookie Pol- LinkedIn
icy . JS API.
Updated
by
LInked in
through-
out the
user's
session.

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 47
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Recruit- linked Session No Third-party cookie in Career When a Browser

ing in_oau user
Site Builder set by LinkedIn session
uses the
th_[id as an OAuth token.
LinkedIn
]_crc
widget.
lidc  Note
RT
Present only if the third-
lang party applications are
bcooki configured.
e
li_at For details, go to Cookie Pol-
mst icy .
bscook
ie
IN_HAS
H
isit
UserMa
tchHis
tory
Analyt
icsSyn
cHisto
ry
li_sug
r

IT Landscape Requirements for SAP SuccessFactors

48 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Recruit- Third- Third-party cookies in Ca- When a

ing
party reer Site Builder created by Career
cookies AddThis. Site
from Builder
AddThis  Note widget is
widgets Present only if the third- used.

Example party applications are

cookie configured.
names:
You can disable these cook-
_atuvc
ies in Social Share Tab in
_atuvs
Career Site Builder Global
na_tc Settings.
ssc
ssh
uvc
sshs
uid
ouid
na_id
loc

Recruit- Session Yes Yes No Third-party cookie set by When a Browser

NID
ing
Google. user logs session
in to the
Used to save user preferen- 6
External
ces and other information. months
career
mini-
See Google Analytics site.
mum de-
Cookie Usage on Web-
pending
sites for more informa-
on the
tion.
cookie
choice of
a user in
browser.

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 49
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Recruit- No
1P_JAR Session Yes Yes Third-party cookie set by When a Browser
ing
Google. user logs session
in to the
Used to save user preferen- 30 days
External
ces and other information. depend-
career
ing on
See Google Analytics site.
the
Cookie Usage on Web-
cookie
sites for more informa-
choice of
tion.
a user in
browser.

Recruit- Session Yes Yes No Third-party cookie set by When a Browser

DV
ing
Google. user logs session
in to the
Used to save user preferen- 7 days
External
ces and other information. depend-
career
ing on
See Google Analytics site.
the
Cookie Usage on Web-
cookie
sites for more informa-
choice of
tion.
a user in
browser.

Recruit- No
CONSEN Session Yes Yes Third-party cookie set by When a Browser
ing
T Google. user logs session
in to the
Used to save user preferen- 2 years
External
ces and other information. depend-
career
ing on
See Google Analytics site.
the
Cookie Usage on Web-
cookie
sites for more informa-
choice of
tion.
a user in
browser.

Onboard- Session Yes Yes None No Standard ASP.NET cookie When Browser
Sessio
ing user logs
nId for application server ses- session
into the
sion management.
Onboard-
ing site.

Onboard- Session Yes Yes None No Standard ASP.NET cookie When Browser
.ASPXR
ing user logs
OLES used to cache role names. session
into the
Onboard-
ing site.

IT Landscape Requirements for SAP SuccessFactors

50 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Onboard- Session Yes Yes None No Standard form authentica- When Browser
QASF_S
ing user logs
F tion ticket cookie. session
into the
Onboard-
ing site.

Onboard- Session Yes Yes None No Stores the last logged-in ac- When Browser
LAST_A
ing user logs
CCOUNT count name. session
into the
_SFQA Onboard-
ing site.

Onboard- Session Yes Yes None No Used to make sure When Browser
_REDIR
ing user logs
ECTCOO sessionId cookie is al- session
into the
KIE_ ways new when user logs in. Onboard-
ing site.

Onboard- Session Yes Yes None Yes Stores encrypted User- When Browser
LOGIN_
ing user logs
DETAIL Name, ProxyUserName, Lo- session
into the
cale, and referrer URL infor-
S Onboard-
mation from HXM Suite. ing site.

Onboard- Persis- No Stores the logout URL of When 1 day

EP_Sig
ing
nOut tent the Onboarding application. user logs
This information is used to into Em-
propagate logout from ap- ployee
plication when user logs out Portal.
from Employee Portal.

Onboard- Persis- Yes Yes None No Standard Sharepoint cookie When 5 days
FedAut
ing
h tent in Employee Portal. It con- user logs
tains a reference to the into Em-
SAML token that Share- ployee
Point stores in its token Portal.
cache. The SAML token
contains the claims issued
to the user by any external
identity and federation pro-
viders, and by the internal
SharePoint security token
service (STS).

Onboard- Session No Standard Sharepoint cookie Browser

WSS_Fu
ing
llScre in Employee Portal. session
enMode

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 51
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Onboard- Session No Standard Sharepoint cookie Browser

stsSyn
ing
cIconP in Employee Portal. session
ath

Onboard- Session No Standard Sharepoint cookie Browser

stsSyn
ing
cAppNa in Employee Portal. session
me

Work- Session No Used for Workforce Analyt- When a Browser

I3LOGI
force An-
N ics login. user logs session
alytics
into
Work-
force An-
alytics.

Work- Session No Session context for Work- When a Browser

ASP.NE
force An-
T_Sess force Analytics. user session
alytics
ionId opens a
Work-
force An-
alytics
URL.

Work- Session No Load balancer node for When a Browser

BIGipS
force An-
erverP Workforce Analytics. user session
alytics
_serve opens a

r-80 Work-
force An-
alytics
URL.

Work- Session No Stop replay attacks for When a Browser

__TICK
force An-
ET__ Workforce Analytics. user logs session
alytics
into
Work-
force An-
alytics.

IT Landscape Requirements for SAP SuccessFactors

52 PUBLIC Cookie Handling in SAP SuccessFactors
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

Em-
SAP_SE Session Yes Yes None No Security session logon When a Browser
ployee
SSIONI ticket. user logs session
Central
in.
Payroll D_<Sys
See 1899896 for more
tem_id information.
>_<sys
tem_cl
ient>

Em-
MYSAPS Session Yes Yes None No SAP proprietary login ticket When a Browser
ployee
SO2 for authentication. user logs session
Central
in.
Payroll

Em-
cookie Persis- Yes Yes No Used for user login session When a 3 mi-
ployee
_payro tent stickiness. user nutes
Central
opens
Payroll ll
the Em-
ployee
Central
Payroll
URL.

Em- Session Yes None No Persists login language and When a Browser
sap-
ployee
userco login client during session. user logs session
Central
in.
Payroll ntext

People Session Yes Yes No For People Analytics inte- When a Browser
SAC-
Analytics
OEM- gration. user cre- session
AUTHTO ates, ed-

KEN its, or
runs a
Story re-
port in
Report
Center.

IT Landscape Requirements for SAP SuccessFactors

Cookie Handling in SAP SuccessFactors PUBLIC 53
 Con-
tains
Per-
Prod-
uct/ Persis- Same- sonal When
Module Cookie tence HttpOnly Secure Site Data Purpose and Usage Set Lifespan

People Session Yes Yes No For People Analytics inte- When a Browser
SAC-
Analytics
OEM- gration. user cre- session
CSRFTO ates, ed-

KEN its, or
runs a
Story re-
port in
Report
Center.

People Session Yes Yes No BIRT server session man- When a Browser
JSESSI
Analytics
ONID agement. user runs session
(BIRT a Table
Server) report in
Report
Center.

Parent topic: Cookie Handling in SAP SuccessFactors [page 34]

Related Information

What Are Cookies? [page 35]

IT Landscape Requirements for SAP SuccessFactors

54 PUBLIC Cookie Handling in SAP SuccessFactors
9 Standards for SAP SuccessFactors
Learning Integration

If you use SAP SuccessFactors Learning and you integrate with structured content providers or online meeting
software, review our standards for the content and integration.

With SAP SuccessFactors Learning, you can take advantage of structured content (like SCORM) and integrate with
online meeting software to hold virtual, in-person training.

• If you work with a third-party vendor for structured content, they should provide the structured content in a
recent standard that we support.
• If you plan to integrate with online meeting software and take advantage of the SAP SuccessFactors Learning
Virtual Learning System (VLS), select a supported vendor.

9.1 AICC and SCORM Support for SAP SuccessFactors

Learning

SAP SuccessFactors Learning supports these versions of structured online leaning content.

• AICC
• SCORM 1.2
• SCORM 2004 2nd Edition
• SCORM 2004 4th Edition

9.2 Supported Virtual Meeting Software for SAP

SuccessFactors

SAP SuccessFactors supports these virtual meeting rooms for virtual classrooms.

Supported Virtual Meeting Software

For cloud software, we support the most recent software available during our testing cycle. However, cloud vendors
ensure that APIs are backwards compatible with earlier versions of their cloud software. This means that Learning
and cloud software integration tested with one version shouldn’t break when a new version of the cloud software is
released.

• Microsoft Teams (cloud, Microsoft Graph REST API v1.0)

IT Landscape Requirements for SAP SuccessFactors

Standards for SAP SuccessFactors Learning Integration PUBLIC 55
• Zoom Meeting 2.0 (cloud only)
• Zoom Webinar 2.0 (cloud only)
• Cisco Webex Training Center WBS40 (cloud only)
• Cisco Webex Meeting Center WBS40 (cloud only)
• Adobe Connect Meetings 11 (cloud only)
• Microsoft Lync 2013 (on-premise)
• Microsoft Skype for Business Server 2016 (on-premise)

 Note

For Adobe meeting room software, we support Adobe Connect Meetings, not Seminars or Webinars.

For Cisco Webex, we support Cisco Webex Site Administration and Cisco Webex Control Hub.

Microsoft Teams webinars and Zoom scheduled programs aren't supported.

Additional Information

Virtual meeting software provides a space for virtual classrooms in SAP SuccessFactors Learning. Users can join
the virtual meeting room to interact with an instructor and classmates. The clients install in a standard way, as if
users clicked a meeting invitation link in an email message.

IT Landscape Requirements for SAP SuccessFactors

56 PUBLIC Standards for SAP SuccessFactors Learning Integration
10 Change History

Learn about changes to the documentation for configuring IT landscapes.

2H 2023

Type of Change Description More Info

Changed We have moved the Change History to SAP SuccessFactors IT Landscape

the end of the guide. Checks [page 3]

1H 2023

Type of Change Description More Info

September 15, 2023

Changed We removed the mention of Safari by Ap- Supported Desktop Browsers for SAP
ple as a supported browser for Story Re- SuccessFactors [page 4]
ports.

June 16, 2023

Changed We removed a note that says Microsoft Supported Desktop Browsers for SAP
Edge isn’t tested for Workforce Analytics, SuccessFactors [page 4]
Strategic Workforce Planning, and Online
Report Designer.

April 28, 2023

None We did not update this document.

IT Landscape Requirements for SAP SuccessFactors

Change History PUBLIC 57
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

IT Landscape Requirements for SAP SuccessFactors

58 PUBLIC Important Disclaimers and Legal Information
IT Landscape Requirements for SAP SuccessFactors
Important Disclaimers and Legal Information PUBLIC 59
www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN