RootAuth supports SMS verification code delivery for mainland China phone numbers. After configuration, SMS messages for sign-up, login, password reset, and SMS-based MFA are sent according to the SMS service settings of the current application.
Path: Log in to the RootAuth console → open the target application → click Configuration in the top navigation bar → Branding → SMS → select Domestic SMS Service
1. Before You Start
Before configuring domestic SMS, make sure you have prepared the following:
- Decide whether to use RootAuth built-in SMS or a custom SMS provider.
- If you use a custom provider, prepare the provider credentials, SMS signature, and template IDs.
- If SMS Verification MFA is enabled, also prepare the template ID for login secondary verification.
- Prepare a mainland China phone number for sending a test SMS.
2. Select a Service Type
On the Domestic SMS Service tab, choose the SMS provider from Service type. Built-in SMS is selected by default.
| Service type | Description |
|---|---|
| Built-in SMS | Use RootAuth built-in SMS. No provider credentials are required. |
| Alibaba Cloud SMS | Use your own Alibaba Cloud SMS service to send domestic SMS messages. |
| Tencent Cloud SMS | Use your own Tencent Cloud SMS service to send domestic SMS messages. |
| Ucloud SMS | Use your own Ucloud SMS service to send domestic SMS messages. |
3. Configure Built-in SMS
If you select Built-in SMS, no additional fields are required. RootAuth sends domestic verification codes through its built-in SMS service.
You can use either action:
- Click Save to save the current configuration.
- Click Save and Send Test SMS to save the configuration and open the test SMS dialog.
When sending a domestic test SMS, RootAuth validates the phone number format. Use this test to confirm that the selected template and delivery path work as expected.
4. Configure Alibaba Cloud SMS
If you select Alibaba Cloud SMS, fill in the following fields:
| Field | Required | Description |
|---|---|---|
| AccessKey ID | Yes | The AccessKey ID of your Alibaba Cloud account. |
| AccessKey Secret | Yes | The AccessKey Secret of your Alibaba Cloud account. |
| Validity period | Yes | Verification code validity period, in minutes. Keep it consistent with the SMS template. |
| Signature | Yes | An approved SMS signature. |
| Sign-up verification template ID | Yes | Template ID used for sign-up verification codes. |
| Login verification template ID | Yes | Template ID used for login verification codes. |
| Password reset verification template ID | Yes | Template ID used for password reset verification codes. |
| Login secondary verification template ID | Required in some cases | Required if SMS MFA was enabled before configuring the custom provider. |

5. Configure Tencent Cloud SMS
If you select Tencent Cloud SMS, fill in the following fields:
| Field | Required | Description |
|---|---|---|
| SdkAppId | Yes | The SdkAppId of your Tencent Cloud SMS application. |
| SecretKey | Yes | The SecretKey of your Tencent Cloud account. |
| SecretId | Yes | The SecretId of your Tencent Cloud account. |
| Region ID | Yes | Select the SMS service region, such as North China, South China, or East China. |
| Validity period | Yes | Verification code validity period, in minutes. Keep it consistent with the SMS template. |
| Signature | Yes | SMS signature text, not the signature ID. |
| Sign-up verification template ID | Yes | Template ID used for sign-up verification codes. |
| Login verification template ID | Yes | Template ID used for login verification codes. |
| Password reset verification template ID | Yes | Template ID used for password reset verification codes. |
| Login secondary verification template ID | Required in some cases | Required if SMS MFA was enabled before configuring the custom provider. |
6. Configure Ucloud SMS
If you select Ucloud SMS, fill in the following fields:
| Field | Required | Description |
|---|---|---|
| PublicKey | Yes | The public key of your Ucloud account. |
| PrivateKey | Yes | The private key of your Ucloud account. |
| Validity period | Yes | Verification code validity period, in minutes. Keep it consistent with the SMS template. |
| Signature | Yes | SMS signature text, not the signature ID. |
| ProjectId | No | The ID of a specific project under the current account. |
| Sign-up verification template ID | Yes | Template ID used for sign-up verification codes. |
| Login verification template ID | Yes | Template ID used for login verification codes. |
| Password reset verification template ID | Yes | Template ID used for password reset verification codes. |
| Login secondary verification template ID | Required in some cases | Required if SMS MFA was enabled before configuring the custom provider. |
7. Send a Test SMS
Click Save and Send Test SMS to open the Send Domestic Test SMS dialog.
Select a template, enter a mainland China phone number, and click Confirm. If the SMS is sent successfully, the test phone number receives a verification code from RootAuth.
8. What Happens After Saving
After the configuration is saved, domestic SMS verification codes for the current application are sent through the selected provider. This affects sign-up, login, password reset, and SMS-based secondary verification for mainland China phone numbers.
If you switch providers, the new configuration takes effect after saving. Before going live, send a test SMS to confirm that the credentials, signature, and template IDs are valid.
9. Disable or Switch the Service
Domestic SMS does not have a separate disable switch. To stop using a custom provider, switch the service type back to Built-in SMS and save.
Switching providers does not delete historical user phone numbers or existing SMS verification bindings.