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.
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.
Follow these steps:
Create the HiveMQ Cloud REST API token, making sure to assign:
Full control of MQTT Credentials, Roles, Role Permissions.
Cluster Read permission.
Save the updated token.
Test your API call against the
/mqtt/roles
endpoint again. The inclusion of the Cluster Read permission should resolve the error.
💡 Important: The Cluster Read permission is required for accessing the /mqtt/roles
endpoint, even if MQTT related permissions are already in place.
Related articles
-
Expose the HiveMQ Control Center and Rest API using Ingress (HiveMQ Knowledge Base - Self Managed Offering)