3262822 - Error - Unable to parse oauth token response due to Unexpected character ('<' (code 60))

When using OAuth from some Third Party vendors, you face issue "Unable to parse oauth token response due to Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (StringReader); line: 3, column: 2]; click to download server response"

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SuccessFactors HXM Suite

• Add an OAuth Configuration from a Third Party under Security Center > OAuth Configurations
• Run an integration in Integration Center using the above OAuth Configuration
• Receive error "Unable to parse oauth token response due to Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (StringReader); line: 3, column: 2]; click to download server response"

This was a known issue that used to happen because 'scope' is being used as a Custom Header Parameter while requesting access token from Third Party OAuth server. But, some of these Third Party server expects 'scope' as a Body Parameter and not as a Header parameter.

This was a product limitation that have been fixed on JIRA INT-14121 (internal only). As of now, you are able to configure where the 'scope' is used, it can either be used on the Header or on the Body:

oauth, third party, microsoft oauth server, security center, integration center, ic , KBA , LOD-SF-INT-ODATA-OAU , ODATA OAUTH Authentication , Product Enhancement