Hello Experts,We are in a process of implementing OAuth(client credentials based) authentication to API proxies using the JWT verify policy in SAP API Management as described in this post. We used EntraID as IdP. We have been able to successfully imp...
Hello Experts, I need some help in understanding the SAML Assertion based OAuth authentication set up between SAP API Management (SAP APIM) and SuccessFactors (SF) system. I followed this blog post to set this up.With an exception that I used "https:...
Dear Experts,I have a SOAP to SOAP scenario in SAP CPI. The target web service expects the request with SOAP envelope along with wsse:Security headers. This is built in the source system and sent to CPI as it is. The request coming to CPI looks somet...
Hello All,I have a doubt regarding the cache policies and how they can be used for caching the OAuth token. I am working on an API to connect to SuccessFactors and I am using OAuth as the Authentication. Here is the high level overview/ sequence of p...
Hello Everyone,
I am trying to connect to OData API (FODepartment) in SuccessFactors(SF) from SAP API Management. While making the calls to SF, I am getting HTTP 400 Error:
Error: We are sorry but the request could not be understood by the serve...
Hi @vinayak_adkoli ,Thank you for your response. Much appreciated!As I mentioned, I replaced /oauth/idp with /oauth/token as highlighted in this post. Since with policy template described in the old blog, the SAML assertion is being generated within ...
Hi vijaykonam As you pointed you, the issue was indeed caused by empty Content-Type header. I have removed the code from policy which was adding the header so that it is taken dynamicaly. The issue is resolved now. Thanks!
Hi Vijay, I have selected None as I am using OAuth via Bearer assertion in policies. Besides, I am not sure that authentication is the problem here as I can see status as connected in Debug logs. Any other suggestions..?