Description | This article describes how to configure FortiAuthenticator with the Twilio SMS gateway. |
Scope | FortiAuthenticator. |
Solution |
If the test SMS fails, check FortiAuthenticator and Twilio's logs: GUI -> Log Access -> Log Access -> Logs.
If the SMS does not make it to the end user, but the request arrives at Twilio, a clear error message should be seen in FortiAuthenticator Logs. Follow the instructions to fix it.
Example:
SMS gateway "TWILIO2" via HTTPS POST returns status code 400 (response: {"code": 21603, "message": "A 'From' or 'MessagingServiceSid' parameter is required to send a message", "more_info": "https://www.twilio.com/docs/errors/21603", "status": 400})
Test the code with Postman or a similar tool. If the request does not arrive at Twilio, check the settings, most likely FortiAuthenticator is incorrectly configured. Note that the SMS gateway feature relies on HTTP, unless the SMTP feature is used, and also relies on parameter+value pairs. The gateway will expect a parameter such as 'To' as an HTTP parameter, and the value on it would be the phone number. FortiAuthenticator will automatically fill the phone number by filling in the variable it supports. Placing the cursor inside the 'value' column (by clicking inside it with the mouse, for example) will show all available variables.
The variables as of now are as follows:
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.