Symptom
You wish to know why an OAuth2 Access token is not generated when userId is bound to an API key but SAML Assertion is generated using username. When you try, the following error occurs:
Unable to generate token. User is not bound to the client application.
This will affect the users, who have different username and userId in the system
- who are using SAML offline tool to generate saml and then used binding api userId to api key
- CPI tool users, who are using user Binding
- Boomi users who have done UserId binding to API key
Read more...
Environment
SAP SuccessFactors API
Product
Keywords
Unable to generate token. User is not bound to the client application, SAML, OAuth, SAML, API, OAuth2, Access token, generated, userId, bound, API key, SAML Assertion, username, API-25938, API-23342 , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA-OAU , ODATA OAUTH Authentication , Product Enhancement
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.