Symptom
After successfully generating an OIDC Access Token, any Learning API call fails with the following error: “Failed to authenticate OIDC token.” (401 Unauthorized). The error details may also include “error.Action.Restricted”.
Environment
SAP SuccessFactors Learning
Reproducing the Issue
- Configure the OIDC application > Successfully generate an Access Token >
- Call a Learning API >
- Observe the “Failed to authenticate OIDC token.” (401 Unauthorized) error.
Cause
This error is related to the “Dependency” configured for the OIDC application in IAS. The dependency is currently pointing to the Learning system, but it should instead point to the Platform system.
Resolution
Dependencies pointing to the Learning system are intended only for scenarios involving OIDC Access Tokens for Learning-only users, which isn’t yet a supported capability.
To resolve it, either create a new dependency pointing to the Platform instance connected to the Learning system, or update the existing dependency as follows:
- IAS Admin > Applications & Resources > Select the OIDC application >
- "Trust" tab > Application APIs > Click "Dependencies" > "Actions" column > Click "Edit" (pencil icon) >
- "Application" field > Select the Platform instance connected to the Learning system > Click "Save".
See Also
- SAP Community - Learning token server deprecation (2027)
- SAP Help Portal - SAP SuccessFactors Learning OData APIs
Keywords
oidc, learning, lms, sfsf, api, call, error, fail, access, token, validation, authentication, Failed to authenticate OIDC token, 401, unauthorized, error.Action.Restricted , KBA , LOD-SF-LMS-ODA , Web Services OData , LOD-SF-LMS , Learning Management System , Problem
SAP Knowledge Base Article - Public