As of January 1, 2021, the token authentication service provided by ApsaraMQ for MQTT is unavailable. The token service API has been migrated to a new cloud service gateway.
Distinguish between the new version and earlier versions of the token authentication service
- If the operation for obtaining a token is called at
https://{tokenServerUrl}/token/apply, you must migrate the token authentication service based on the new cloud API. For more information, see ApplyToken. - If the operation for obtaining a token is called by using the ApplyToken, you can ignore this notice.
Benefits
Migration to the new cloud service gateway brings you the following benefits:
- The new cloud service gateway supports access by using HTTP and out-of-the-box SDKs for multiple programming languages. The new cloud service gateway also provides demos in multiple programming languages. This way, signature strings are automatically calculated, which helps save access costs.
- The new cloud service gateway supports global acceleration and comprehensive throttling and isolation measures. This reduces the response time (RT) of API operations and improves service stability.
- The new cloud service gateway supports a wide range of debugging channels, allowing you to debug parameters at any time and view the final results during debugging.
- The new cloud service gateway allows you to apply for a token by using a RAM user or a Secure Token Service (STS)-authorized account. For information about access methods, see Overview of token-based authentication.
Notes
- Before the old-version token authentication service was out of service, the API operations provided by the new-version token authentication service were already fully compatible with those provided by earlier versions. You can gradually switch traffic between the versions.
- This migration affects only the cloud API for tokens. The tokens used by Message Queue for MQTT clients are not affected and do not need to be changed.
- If you have questions about the migration solution, Contact Us.