The token authentication service provided by Message Queue for MQTT will become out of service on January 1, 2021. 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 your service based on the new cloud API.
  • If the operation for obtaining a token is called by using the cloud API, 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, out-of-the-box SDKs for multiple languages, and demos in multiple languages. This way, signature strings are automatically calculated, reducing access costs.
  • The new cloud service gateway supports global acceleration and comprehensive throttling and isolation measures, reducing the response time (RT) of API operations and improving 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 Resource Access Management (RAM) user or a Secure Token Service (STS)-authorized account. For more information about access methods, see Overview of token-based authentication.

Notes

  • Before the old-version token authentication service is out of service, the API operations provided by the new-version token authentication service are fully compatible with those provided by earlier versions. You can gradually switch traffic between the versions.
  • This migration only affects the cloud API for token scenarios. The tokens used by Message Queue for MQTT clients are not affected and do not need to be changed.
  • If you have any questions or difficulties in migration plans, please submit a ticket or Contact us.