Supporting application/x-www-form-urlencoded payload in custom sms provider.

[pandukakarunasena]

Describe the issue:

The current implementation does not support sending data in the application/x-www-form-urlencoded format. Instead, the SMS body template placeholders are replaced, assuming the final data object is a JSON object[1]. This causes failures in receiving SMS OTPs when the custom SMS provider requires data in application/x-www-form-urlencoded format. If only JSON is supported, the phrase "The content type of the API request. Accepted values are 'FORM' or 'JSON''" should be removed from the management console.

How to reproduce:

Configure a custom sms provider with content type FORM and use template as advised.

Expected behavior:

Configure a custom SMS provider to use the content type FORM( application/x-www-form-urlencoded) and follow the recommended template guidelines.

Environment information (Please complete the following information; remove any unnecessary fields) :

• Product Version: [e.g., IS 7.0.0]

---

[1] https://github.com/wso2-extensions/identity-local-auth-smsotp/blob/v1.0.8/components/org.wso2.carbon.identity.local.auth.smsotp.provider/src/main/java/org/wso2/carbon/identity/local/auth/smsotp/provider/impl/CustomProvider.java#L110C8-L112C74