Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Problem

When using a HiveMQ Cloud REST API token with full control over MQTT Credentials, Roles, and Role Permissions, you may still receive an error when attempting to access the /mqtt/roles API endpoint.

image-20241011-134756.png

Solution

To resolve this issue, ensure that your REST API token not only has full control over MQTT Credentials, Roles, and Role Permissions, but also includes the Cluster Read permission. To modify and delete the REST API token should also include Cluster Read Write and Delete permissions

Follow these steps:

  1. Create the HiveMQ Cloud REST API token, making sure to assign:

    • Full control of MQTT Credentials, Roles, Role Permissions.

    • Cluster Read Write and Delete permissions.

    image-20241011-141014.png

  2. Save the updated token.

  3. Test your API call against the /mqtt/roles endpoint again. The inclusion of the Cluster Read permission should resolve the error.

💡 Important: The Cluster permissions are required for accessing the /mqtt/roles endpoint, even if MQTT related permissions are already in place.

  • No labels