From acf1d31fe005d64f600af28fa27091518c6dbe6c Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Tue, 20 Jan 2026 09:55:42 +0000 Subject: [PATCH 1/3] Update LMS SAP guide with Platform Token Server Auth refinements - Add note that Platform Token Server auth is write-only - Include Learning Content Provider step in authentication flow - Change "Connecting with StackOne" to "Connecting Your Account" - Add complete Authentication Flow 3 section with all required steps Co-authored-by: Max Strivens --- connection-guides/lms/sapsuccessfactors.mdx | 183 +++++++++++++++++++- 1 file changed, 182 insertions(+), 1 deletion(-) diff --git a/connection-guides/lms/sapsuccessfactors.mdx b/connection-guides/lms/sapsuccessfactors.mdx index cf45863..a55892b 100644 --- a/connection-guides/lms/sapsuccessfactors.mdx +++ b/connection-guides/lms/sapsuccessfactors.mdx @@ -14,6 +14,7 @@ flow you follow will depend on your use case. - If you are working with an external LXB/LMS to pull data into your SAP instance, you will need to follow the Authentication Flow 1. - If you are working with an external content provider to pull external content into your SAP instance, you will need to follow the Authentication Flow 2. +- If you need to write data to your SAP instance using Platform Token Server Authentication, you will need to follow the Authentication Flow 3. # Authentication Flow 1: Linking your SAP instance library to an external LXB/LMS to pull data @@ -499,7 +500,187 @@ The SSO configuration should use the following approach: -## Linking your Account +# Authentication Flow 3: Platform Token Server Authentication (Write-Only) + + + This authentication method is **write-only** and is used when you need to write data to your SAP SuccessFactors instance using OAuth2 with X.509 certificates. + + +## Locating API Server + + + + SAP uses multiple API server addresses. You will need to look up the API server that corresponds to your tenant domain on this [table](https://help.sap.com/docs/SAP_SUCCESSFACTORS_PLATFORM/d599f15995d348a1b45ba5603e2aba9b/af2b8d5437494b12be88fe374eba75b6.html) under the `API Server` column. + + For example, if your domain was `https://pmsalesdemo8.successfactors.com/` you would search for `salesdemo8` in the table. + + + API Server Example + + + Copy the value in the `API Server` column (remove the final forward-slash `/`). In this example, the value would be `https://apisalesdemo8.successfactors.com`. + + Use this value as the `API Server` value when connecting SAP SuccessFactors to StackOne. + + + +## Finding the Learning Server URL + + + + Log into SAP SuccessFactors. + + + Type Learning Administration in the search bar and select the Learning Administration module. + + + Look in the browser address bar for the URL and save the address. + + Learning Server Example + + In this case: https://sfcpart000906.scdemo.successfactors.com/ is the access point. + + Use this value as the `Learning Domain URL` value when connecting SAP SuccessFactors to StackOne. + + + +## Finding Username + + + + Login to SAP SuccessFactors. + + + + Select your profile image in the upper right-hand corner of the screen. + + Your username is the value in parenthesis. Copy this value and note it as your `Username`. + + + Username Location + + + + +## Finding Company ID + + + + Within the same dropdown from the previous step, select the Show version information option. + + + + Within the modal that appears, you will see `Company ID`. Copy and note down this value. + + + Company ID + + + + +## Registering a new Client Application + + + + In the upper right search bar, search for Manage OAuth2 Client Applications and select the option under Actions. + + + Manage OAuth2 Client Applications + + + + + Select Register Client Application. + + + + Enter an Application Name, e.g. `StackOne`. + + Enter an Application URL. Note: This can be any URL and is not used in this integration. + + + Register Client Application + + + + +## Generating X.509 Certificate + + + + Press the Generate X.509 Certificate button. + + Enter any Common Name(CN) for the certificate, e.g. `StackOne OAuth2`. + + + Generate X.509 Certificate + + + + + Press Generate. + + Copy the value inside the X.509 Certificate section. + + + Copy X.509 Certificate + + + + +## Downloading Private Key + + + + Press the Download button. + + ❗Caution: The downloaded file contains your private key. This should be handled securely, and this local file should be deleted after your account has been linked. + + + + Select and copy the long string of characters between -----BEGIN ENCRYPTED PRIVATE KEY----- and -----END ENCRYPTED PRIVATE KEY----- + + This value is your Private Key. Please keep it safe! + + + +## Finding API Key + + + + Your API Key is displayed on the Manage OAuth2 Client Applications screen above your X.509 Certificate. + + + API Key + + + + +## Locating Learning Content Provider + + + + Identify the Learning Content Provider name that you configured in the OCN property file (as described in Authentication Flow 2). This provider name will be used when connecting the account. + + + +## Connecting Your Account + + + + Upon reaching the Link Account page, enter the gathered details and proceed by clicking the `Connect` button. + + + Link Account + + + + + +Note: The integration may take up to 15 minutes to initially authenticate once the account has been connected. In the meantime, requests will return a 401: Unauthorized response. + + +## Linking your Account (Flows 1 & 2) From 1e652e60cb019fa316bd4daff397a193adb9776c Mon Sep 17 00:00:00 2001 From: Max Strivens <74908625+mstrivens@users.noreply.github.com> Date: Tue, 20 Jan 2026 10:10:24 +0000 Subject: [PATCH 2/3] Update connection-guides/lms/sapsuccessfactors.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- connection-guides/lms/sapsuccessfactors.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/connection-guides/lms/sapsuccessfactors.mdx b/connection-guides/lms/sapsuccessfactors.mdx index a55892b..b2bab4a 100644 --- a/connection-guides/lms/sapsuccessfactors.mdx +++ b/connection-guides/lms/sapsuccessfactors.mdx @@ -660,7 +660,10 @@ The SSO configuration should use the following approach: - Identify the Learning Content Provider name that you configured in the OCN property file (as described in Authentication Flow 2). This provider name will be used when connecting the account. + Identify the Learning Content Provider name that will be used when connecting the account: + + - If you previously configured OCN in Authentication Flow 2, use the provider name from your OCN property file. + - If you have not configured OCN (for example, you are only using Authentication Flow 3), use the provider name as it appears in SAP SuccessFactors Learning or as provided by your content provider. From e9dca842a74edc5cc9a014892829c9ba56b8f07e Mon Sep 17 00:00:00 2001 From: Max Strivens <74908625+mstrivens@users.noreply.github.com> Date: Tue, 20 Jan 2026 10:10:45 +0000 Subject: [PATCH 3/3] Update connection-guides/lms/sapsuccessfactors.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- connection-guides/lms/sapsuccessfactors.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/connection-guides/lms/sapsuccessfactors.mdx b/connection-guides/lms/sapsuccessfactors.mdx index b2bab4a..a1fd159 100644 --- a/connection-guides/lms/sapsuccessfactors.mdx +++ b/connection-guides/lms/sapsuccessfactors.mdx @@ -524,7 +524,7 @@ The SSO configuration should use the following approach: -## Finding the Learning Server URL +### Finding the Learning Server URL