Defender SMS Token

Hi,

1. Yes Defender uses the SOAP protocol and XML to transfer data.

2. The 2sms example is the only one defined in the Defender Policy POST Data, we suggest consulting with Professional Service team for implementation assistance.

Thanks!

in addition to above, does it support application/JSON calls as well?

SOAP is an XML-based protocol and does not use application/JSON calls

So we can say that the supported XML-based protocols are SOAP and RESTful, right?
or only SOAP based?

Defender has two ways to utilize SMS tokens:

1. Using Defender SMS Provider option which supports sending POST data via SOAP protocol in XML format 

- This option does not support REST API methods.

2. Using OneLogin SMS provider option which supports other SMS service providers as per Admin guide here:

https://docs.oneidentity.com/bundle/Defender-Desktop-Login_admin-guide_6.6/page/Managing_SMS_Token.htm

- OneLogin does support other sms providers with custom SMS configuration as mentioned here:

https://onelogin.service-now.com/support?id=kb_article&sys_id=57deffe11ba3b15074e164e9bc4bcb00&kb_category=48d569fcdbd45340d5505eea4b96191a

Thanks!

Hi Tawfiq,

We are currently troubleshooting an issue with the One Identity Defender SMS OTP integration using a SOAP-based connection to our SMS gateway. Despite multiple successful tests from the same server hosting Defender—using external testing tools that triggered visible responses on the SMS gateway—no response is observed when the call is initiated directly by Defender.

From the Defender side, we can see in the DSS logs that the SMS OTP is marked as sent. However, there are no corresponding logs or traces of the request reaching the SMS gateway.

Here is an example of a working call tested on SOAPUI and inserted to POST Data in the SMS token configuration:

URL: api.smsglobal.com/.../soapserver.php

<soapenv:Envelope xmlns:xsi="">www.w3.org/.../XMLSchema-instance"
xmlns:xsd="">www.w3.org/.../XMLSchema"
xmlns:soapenv="">schemas.xmlsoap.org/.../"
xmlns:urn="urn:MobileWorks">
<soapenv:Header/>
<soapenv:Body>
<urn:apiSendSms soapenv:encodingStyle="">schemas.xmlsoap.org/.../">
<ticket xsi:type="xsd:string">XXXXXXX</ticket>
<sms_from xsi:type="xsd:string">XXXX</sms_from>
<sms_to xsi:type="xsd:string">XXXXXX</sms_to>
<msg_content xsi:type="xsd:string">Your OTP is [DATA]</msg_content>
<msg_type xsi:type="xsd:string">Text</msg_type>
<unicode xsi:type="xsd:string">0</unicode>
<schedule xsi:type="xsd:string"></schedule>
</urn:apiSendSms>
</soapenv:Body>
</soapenv:Envelope>

To assist with further troubleshooting, could you kindly provide an example of a working SOAP call (including request format and required headers) that is known to be compatible with Defender's SMS OTP feature?

Your support on this matter would be greatly appreciated.

Hi Tawfiq,

We are currently troubleshooting an issue with the One Identity Defender SMS OTP integration using a SOAP-based connection to our SMS gateway. Despite multiple successful tests from the same server hosting Defender—using external testing tools that triggered visible responses on the SMS gateway—no response is observed when the call is initiated directly by Defender.

From the Defender side, we can see in the DSS logs that the SMS OTP is marked as sent. However, there are no corresponding logs or traces of the request reaching the SMS gateway.

Here is an example of a working call tested on SOAPUI and inserted to POST Data in the SMS token configuration:

URL: api.smsglobal.com/.../soapserver.php

<soapenv:Envelope xmlns:xsi="">www.w3.org/.../XMLSchema-instance"
xmlns:xsd="">www.w3.org/.../XMLSchema"
xmlns:soapenv="">schemas.xmlsoap.org/.../"
xmlns:urn="urn:MobileWorks">
<soapenv:Header/>
<soapenv:Body>
<urn:apiSendSms soapenv:encodingStyle="">schemas.xmlsoap.org/.../">
<ticket xsi:type="xsd:string">XXXXXXX</ticket>
<sms_from xsi:type="xsd:string">XXXX</sms_from>
<sms_to xsi:type="xsd:string">XXXXXX</sms_to>
<msg_content xsi:type="xsd:string">Your OTP is [DATA]</msg_content>
<msg_type xsi:type="xsd:string">Text</msg_type>
<unicode xsi:type="xsd:string">0</unicode>
<schedule xsi:type="xsd:string"></schedule>
</urn:apiSendSms>
</soapenv:Body>
</soapenv:Envelope>

To assist with further troubleshooting, could you kindly provide an example of a working SOAP call (including request format and required headers) that is known to be compatible with Defender's SMS OTP feature?

Your support on this matter would be greatly appreciated.

SMS providers may have different requirements and I see that SMS Global SOAP API requires to use a apiValidateLogin where you would need to use a token for subsequent API calls but this is not compatible with Defender.

You may try the HTTP API instead in this case to see if that works better, for example use:

URL:
api.smsglobal.com/http-api.php

POST DATA:
?action=sendsms&user=[USERID]&password=[PASSWORD]&from=Test&to=[PHONE]&text=[DATA]

Thanks!