Announcement on SMS-based authentication services not supporting custom signatures
Dear Alibaba Cloud Phone Number Verification Service users,
Because of carrier real-name signature policy requirements, effective immediately for Phone Number Verification Service products, all authentication methods that use SMS verification codes will no longer support sending text messages with custom signatures. The specific recovery time will be announced at a later date. If you encounter issues, such as failed or abnormal SMS verification code delivery, you can use the system-provided signature and template to send text messages.
Affected services:
Unified Authentication: You should promptly check the Unified Authentication policy and confirm that the relevant nodes for SMS authentication are configured to use a "system-provided signature" for sending text messages.
SMS Authentication Service: You can follow the operational guide to use the system-provided signature and template for SMS authentication.
SMS Authentication Feature - SDK Connection Type (will be deprecated soon): Historically, SMS authentication schemes created using this feature used the app name as the SMS signature for sending. This is no longer supported under current real-name signature policy requirements. You must migrate your existing SDK connection type to the SMS Authentication Service.
We apologize for any inconvenience this may cause.