Defender SMS Token

Question

Hello,

We are currently integrating Defender MFA with our SMS service provider to enable SMS token delivery.

During the configuration, we encountered some limitations and need clarification regarding the supported API call formats Defender accepts under the Mobile Provider settings.

We noticed that Defender provides a default POST data structure for 2sms, as shown below:

<?xml version="1.0" encoding="UTF-8"?>
<Request xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xsi:noNamespaceSchemaLocation="">schema.2sms.com/.../0410_RequestSendMessage.xsd" Version="1.0">
  <Identification>
    <UserID>[USERID]</UserID>
    <Password>[PASSWORD]</Password>
  </Identification>
  <Service>
    <ServiceName>SendMessage</ServiceName>
    <ServiceDetail>
      <SingleMessage>
        <Destination>[PHONE]</Destination>
        <Text>Your Defender one-time password is [DATA]</Text>
      </SingleMessage>
    </ServiceDetail>
  </Service>
</Request>

It appears that this is an XML-based POST, likely sent as a RESTful XML body.

Our SMS provider, however, only supports a SOAP-based integration, and we have a fully working SOAP request in SoapUI.

but we are unsure whether Defender MFA can be configured to send SOAP requests like the one above.

Our questions are:

Does Defender support sending full SOAP requests as POST data to an external SMS provider?
Are there any examples or documentation for integrating custom SOAP-based SMS APIs with Defender MFA?

Tawfiq.Ahmad · Accepted Answer

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!

Defender SMS Token

Top Replies