• Overview
  • Configuration

Related-apps

Twilio

Manage strong authentication by aligning Twilio Verify users with IT systems.

MFAIdentity management

Overview

Twilio Verify is a service that enables OTP-based phone number verification for secure user authentication. Integrating Twilio Verify with Active Directory using ADManager Plus allows organizations to automate user account provisioning and deprovisioning based on changes in Active Directory. This ensures that only valid, active AD users have access to Twilio’s verification infrastructure—helping maintain control over who can initiate or manage verification workflows.

 

Automated onboarding

Create user accounts in Twilio Verify when new users are added to AD, enabling them to send or manage verification requests.

 

Real-time access updates

Reflect AD role or group changes in Twilio Verify to ensure users retain only relevant access based on their responsibilities.

 

Secure deprovisioning

Automatically remove or disable users in Twilio Verify when their AD accounts are offboarded, preventing misuse of verification services.

 

How to configure Twilio Verify integration in ADManager Plus

Prerequisites:

  • Twilio Verify uses basic authentication credentials to authorize API requests.
  • Authentication credentials required: Account SID as the username and Auth Token as the password.

Privileges:

  • To import users (Inbound action): Ensure the account used for authorization has permission to read all user accounts.
  • To perform any action or query in Twilio Verify (Outbound Action): Ensure the account used for authorization has permission to perform the desired action.
Note: ADManager Plus comes with a pre-configured set of APIs that helps perform basic actions with the integration. If the action you require is not available, please gather the necessary API details from Twilio Verify's API documentation to configure under inbound or outbound webhooks to perform the required actions.

Authorization configuration

  • Log in to ADManager Plus and navigate to Directory/Application Settings.
  • Go to Application Integrations, then search and select Twilio Verify.
  • Toggle the Enable Twilio Verify Integration button on.
  • In the Twilio Verify Configuration page, click Authorization.
  • Enter the authentication credentials. Use Account SID as the username and Auth Token as the password.
  • Click Configure.

Inbound webhook configuration

Inbound webhook enables you to fetch user data from Twilio Verify to ADManager Plus. To configure an inbound webhook for Twilio Verify:

  • Under Inbound Webhook, click Twilio Verify Endpoint Configuration.
  • In the Endpoint Configuration tab, configure an endpoint using the + Add API endpoint button and filling in the required fields as per Twilio Verify's API references. Click here to learn how. Note:
    • Authorization Header is preconfigured as a header for authenticating API requests as configured during Authorization Configuration.
    • Macros: You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component.
    • Refer to Twilio Verify's API references and configure additional headers and parameters, if required.
  • Once done, click Test & Save. A response window will display all the requested parameters that can be fetched using the API call. Click Proceed. Note:
    • Refer to Twilio Verify's API references to know the Parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for Twilio Verify using the + Add API endpoint button. Click here to learn how.
  • Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in Twilio Verify. [ADManager Plus also lets you customize attribute format from Twilio Verify]
  • Click + Add New Configuration and perform the following:
    • Enter the Configuration Name and Description and select the Automation Category from the drop-down menu.
    • In the Select Endpoint field, select the desired endpoint and a Primary Key that is unique to a user (e.g. employeeIdentifier).
      Note: When multiple endpoints are configured, this attribute must hold the same value in all the endpoints.
    • In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective column in Twilio Verify.
    • If you would like to create a new custom format for this, click Mapping Attribute.
    • Click Save.
Note: The attribute mapping configured in this section can be selected as the data source during automation configuration to perform the desired action on the list of users received from the API response.

Outbound webhook configuration

Outbound webhook enables you to update the changes made in AD using ADManager Plus to Twilio Verify or fetch or forward required details from Twilio Verify and synchronize them with AD.

To configure an outbound webhook for Twilio Verify:

  • Under Outbound Webhook, click Twilio Verify Webhook Configuration.
  • Click + Add Webhook.
  • Enter a name and description for this webhook.
  • Decide on the action that has to be performed and refer to Twilio Verify's API references for the API details, such as the URL, headers and parameters.
  • Select the HTTP method that will enable you to perform the desired action on the endpoint from the drop-down menu.
  • Enter the endpoint URL.
  • Configure the Headers, Parameters, and Message Type in the appropriate format based on the API call that you would like to perform.
  • Click Test and Save.
  • A pop up window will then display a list of AD users and groups to test the configured API call. Select the desired user or group over which this API request has to be tested and click OK. This will make a real-time call to the endpoint URL, and the selected objects will be modified as per the configuration.
  • The webhook response and request details will then be displayed. Verify them for the expected API behavior and click Save.
Note: The webhooks configured in this section can be included in Orchestration Templates, which can be used in event-driven and scheduled automations. They can also be applied directly to desired users to perform a sequence of actions on them (under Management > Advanced Management > Orchestration).