Content-Type "application/x-www-form-urlencoded" Not Supported in HTTP Request Action (Workflows)

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hello,

As SuccessFactors is deprecating Basic Authentication, we are transitioning to OAuth 2.0 for API access. However, we are encountering an issue when attempting to implement this in SailPoint Identity Security Cloud (ISC) Workflows.

SuccessFactors’ OAuth token endpoint requires the Content-Type: application/x-www-form-urlencoded, but the HTTP Request action in ISC Workflows does not support this content type explicitly. The only available content type, labeled as “Form”, does not behave as expected—it does not encode the body in the required x-www-form-urlencoded format.

We attempted to manually add a header specifying "Content-Type": "application/x-www-form-urlencoded", but the API call still fails.

After researching similar issues in the SailPoint Developer Community, it seems this is a known limitation in the current Workflow HTTP request implementation.

Is there any recommended workaround or best practice for this situation when integrating with SuccessFactors?

Thank you,
Youssef

2

Hi,

Any workaround found for this issue? We are also facing issue in HTTP Request in workflow when we need to add x-www-form-urlencoded content-type.

Thanks

3

Hello @shruthichethan,

The support suggested to open an idea, but i found no technical solution unfortunately.

You can votre here : Support for Content-Type | SailPoint Ideas Portal

BR,

Youssef

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.