This section describes how to integrate  MessageMedia SMS Gateway  with RSA Authentication Manager for On Demand Token code delivery.
When a user authenticates to an agent using his/her username and on-demand PIN, the RSA Authentication Manager sends the on-demand tokencode and mobile number to MessageMedia using the HTTP or HTTPS protocol. MessageMedia then delivers the on-demand tokencode to the user’s mobile device via Short Message Service (SMS.) The authentication process is completed when the user enters the on-demand tokencode into the agent’s prompt for next tokencode.

SMS HTTP Plug-In Configuration

RSA Authentication Manager can be configured to integrate a supported Short Message Service (SMS) provider using HTTP, HTTPS, or XML-over-HTTP to deliver on-demand tokencodes to a user’s mobile phone.

Important: HTTP connections are not secure. Sensitive information, such as a tokencode, may be exposed. For secure connections, configure HTTPS.
Before configuring the HTTP Plug-In, you must locate the configuration parameters and base URL. Contact your SMS provider for this information. You must include the following elements within your provider’s parameters to retrieve data from the corresponding fields. 

SMS HTTP Plug-In is configured in the RSA Authentication Manager’s Security Console. The configuration page has three sections:

• Tokencode Delivery by SMS
• SMS Provider Configuration 
• SMS HTTP Proxy Configuration (optional) 

Tokencode Delivery by SMS

1. Mark the Delivery by SMS checkbox to enable the delivery of On-Demand Tokencodes using SMS service.
2. Select the User Attribute to Provide SMS Destination from the drop-down menu.(Optional) Select the Default country code from the drop-down menu.
3. Select HTTP from the SMS Plug-In drop-down menu.

SMS Provider Configuration

1. Copy the following line into Base URL field. 

https://xml.messagemedia.com/
               Note: For best results, make sure your Internet firewalls permit the 
              following destination MessageMedia IPs from your RSA Authentication 
              Manager(s): 103.226.247.1 through 103.226.247.254, and 54.79.50.63.

2. Click Import Certificate to browse to and install an SMS certificate if you are configuring your base for HTTPS.

Note: If you experience SSL connection issues when connecting with HTTPS, obtain the certificate using the Mozilla Firefox Web browser. Export the certificate as “X.509 Certificate with chain (PEM)”, and set the extension to .pem.

3. Select XML from the HTTP Method drop-down menu.
4. Copy the following string in to the Parameters field.

  <?xml version="1.0" encoding="utf-8"?>
  <sendMessages xmlns="http://xml.m4u.com.au/2009">
   <authentication>
    <userId>$cfg.user</userId>
    <password>$cfg.password</password>
   </authentication>
    <requestBody>
     <messages>
      <message format="SMS" sequenceNumber="1">
       <recipients>
        <recipient uid="1">msg.address</recipient>
       </recipients>
       <deliveryReport>true</deliveryReport>
       <content>$msg.message</content>
      </message>
     </messages>
    </requestBody>
  </sendMessages>

5. Enter Account User Name for the SMS Provider.
6. Enter Account Password for the SMS Provider.
7. Copy the following line in to the Success Response Code field.
          sent="1"
8. Copy the following line in to the Response Format field.
          sent="1"

SMS HTTP Proxy Configuration (optional)

1. Enter the configuration settings for your HTTP Proxy server if you are using one.

2. Click Update to save the SMS Configuration.