Configure Infobip as MFA SMS Provider

You can send multi-factor authentication (MFA) text messages using Infobip. Infobip SMS is a messaging platform that enables Auth0 to deliver multi-factor verification via text messages. To learn more, see Infobip's SMS Overview.

The following steps will add text-message-based MFA to the login flow for the tenant in which you're working. We highly recommend testing this setup on a staging or development server before making the changes to your production login flow.

To configure a custom SMS provider for MFA using Infobip, you will:

  1. Create a Send Phone Message hook

    1. Configure hook secrets

    2. Add the Infobip call

    3. Test your hook implementation

  2. Activate the custom SMS factor

  3. Test the MFA flow

Optional: Troubleshoot

Prerequisites

Create Send Phone Message hook

You will need to create a Send Phone Message hook, which will hold the code and secrets of your custom implementation. You can only have one Send Phone Message hook active at a time.

Configure hook secret

Add the following hook secret with the key and corresponding value from the Infobip API Keys page.

INFOBIP_API_KEY

Add Infobip API call

To make the call to Infobip, add the appropriate code to the Hook. Copy the code block below and edit the Send Phone Message hook code to include it. This function will run each time a user requires MFA, calling AWS SNS to send a verification code via SMS.

/**
@param {string} recipient - phone number
@param {string} text - message body
@param {object} context - additional authorization context
@param {string} context.factor_type - 'first' or 'second'
@param {string} context.message_type - 'sms' or 'voice'
@param {string} context.action - 'enrollment' or 'authentication'
@param {string} context.language - language used by login flow
@param {string} context.code - one time password
@param {string} context.ip - ip address
@param {string} context.user_agent - user agent making the authentication request
@param {string} context.client_id - to send different messages depending on the client id
@param {string} context.name - to include it in the SMS message
@param {object} context.client_metadata - metadata from client
@param {object} context.user - To customize messages for the user
@param {function} cb - function (error, response)
*/
module.exports = function(recipient, text, context, cb) {

    const axios = require('axios').default;
    const API_KEY = context.webtask.secrets.API_KEY;;
    const BASE_URL = 'https://2622w.api.infobip.com';
    const instance = axios.create({
        baseURL: BASE_URL,
        headers: {
            'Authorization': 'App ' + API_KEY,
            'Accept': 'application/json',
            'Content-Type': 'application/json'
        },
    });
    instance({
        method: 'post',
        url: '/sms/2/text/advanced',
        data: {
            "messages": [
                {
                    "destinations": [
                        { "to": recipient }
                    ],
                    "text": text
                }
            ]
        }
    })
    .then((response) => {
        cb(null, {});
    })
    .catch((error) => {
        cb(error);
    });

};


Test hook implementation

Click the Run icon on the top right to test the hook. Edit the parameters to specify the phone number to receive the SMS, and click the Run button.

Activate custom SMS factor

To use the SMS factor, your tenant needs to have MFA enabled globally or required for specific contexts using rules. To learn how to enable the MFA feature, see:

The hook is now ready to send MFA codes. The last steps are to configure the SMS Factor to use the custom code and test the MFA flow.

  1. Go to Dashboard > Multifactor Auth and click the SMS factor box.

  2. In the modal that appears, select Custom for the SMS Delivery Provider, then make any adjustments you'd like to the templates. Click Save when complete, and close the modal.

  3. Enable the SMS factor using the toggle switch.

Test MFA flow

Trigger an MFA flow and verify that everything works as intended.

Troubleshoot

If you do not receive the text message, look at the hook logs. Look for a failed SMS log entry. To learn which event types to search, see the Log Event Type Code list, or you can use the Filter control to find MFA errors.

MFA SMS Provider Auth0 Log Errors

Make sure that:

  • The hook is active and the SMS configuration is set to use Custom.

  • You have configured the hook secrets.

  • The configured Hook Secrets are the same ones you created in the Infobip portal.

  • Your phone number is formatted using the E.164 format.

Learn more