SAP SuccessFactors Spoke - OAuth Setup & Migration - Pre-Tokyo, Tokyo and beyond.

[ajaymalik83]

SAP SuccessFactors is sunsetting the HTTP Basic Authentication (Basic Auth) to access APIs in SAP SuccessFactors by November 2023. In lieu of Basic Auth, a more secure OAuth 2.0 authentication method has been selected by SAP SuccessFactors to use its APIs. As a result, the SAP SuccessFactors Spoke developed by Bristlecone Inc. has also been updated to enable access to SuccessFactors’ APIs using OAuth 2.0.  

Version 4.x.x of the SAP SuccessFactors Spoke will support access to SuccessFactors’ APIs via OAuth 2.0. Existing customers of the SAP SuccessFatcors Spoke will have to upgrade to this new version of the Spoke in order to continue using the capabilities of the SAP SuccessFactors Spoke in ServiceNow. 

In order to allow a seamless experience to the customers of the SAP SuccessFactors Spoke for this upgrade, Bristlecone has created an end-to-end demo with detailed steps on 

• Migration from the current version 3.x.x of the Spoke to the new version supporting OAuth i.e. v4.x.x 
• Configuration required across ServiceNow family release versions prior to Tokyo (such as Rome, San Diego) and family release versions starting from Tokyo (such as Tokyo, Utah). 

Jump right in to see the demos: 

• SAP SuccessFactors Spoke – OAuth Setup & Migration – Pre-Tokyo

https://youtu.be/HWVPaRcr3gsLet

• SAP SuccessFactors Spoke –OAuth Setup & Migration – Tokyo

https://youtu.be/6qAnORw_D34

[Jordan McCann]

Where do we find the update sets for pre-Tokyo?

[Gaurav Gupta3]

Hi Ajay, 

I am working on retrieving the data from SF to Servicenow worker profiles staging table.

Thank you for sharing the document and videos.

All is exactly configured as told in the video, however when I try to create oAuth 2.0 credentials, for SOAP connection, however when click on Get Auth Token (related list), it ends up with error "OAuth flow failed. Verify the configurations and try again. Error detail:invalid_request, Missing parameters: access_token"   

Any idea what exactly, I should be looking here for and where?

 Regards

Gaurav Gupta

[Hardik Benani]

Did anyone ever got this working, there seems to be a major flaw here?  Below documentation states OAuth auth is not supported via MidServer. This means the spoke is of no use 80% of time.

SuccessFactors type application are very sensitive and the network should be internal, so having no mid-server support for Auth is strage. Wonder if anyone had this working via MidServer? 

https://docs.servicenow.com/bundle/utah-api-reference/page/integrate/outbound-rest/concept/c_Outboun... 

[Ram_n Botelho]

Hi, I'm having same problems with this connection:

Log is returning: "OAuth authentication failed for client_credentials grant type flow"

Error Message on "oauth_saml2_bearer_input" page is returning: 

"OAuth flow failed. Verify the configurations and try again. Error detail:invalid_request, Missing parameters: access_token"

[PDawg]

Hi Guys, 

We have encountered the same issue recently and below step has helped us in solving this error:

1. Verify API key in the assertion attribute is the same as the client ID in your application registry.

from:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1639183

Hope this helps!