Troubleshooting Client Registry

The following table addresses common issues you might encounter when registering clients with Connectware. Use these solutions to quickly resolve problems with client registration, authentication, and connectivity.

Troubleshooting - Self-Registering Clients via REST API

These issues apply to clients registering via the /api/client-registry/register REST API. Also see Self-Registering Clients via REST API.

For detailed information about the Client Registry REST API parameters, see User Management API Reference.

Issue	Possible Cause	Solution
Client not appearing in registry	Registry is locked	Unlock the registry using the lock icon in the Admin Web App.
Registration failing	Username/password too short	Ensure username ≥ 3 characters, password ≥ 5 characters. Also adhere to the Password Policy Configuration.
CSR rejection	CN mismatch in CSR	Ensure CSR's Common Name matches the requested username.
Client stuck in "pending"	Admin hasn't granted access	Review and approve from Client Registry interface.
Unexpected "locked" (423) response	Registry timeout	Registry auto-locks after 5 minutes; unlock it again.
Certificate authentication failing	Invalid or missing certificate	Ensure CSR is valid and the signed certificate is used.

Troubleshooting - Self-Registering MQTT Clients

These issues apply to MQTT clients self-registering via authentication attempts. Also see Self-Registering MQTT Clients.

Issue	Possible Cause	Solution
Client not appearing in registry	Registry is locked	Unlock the registry using the lock icon in the Admin Web App.
Registration failing	Username/password too short	Ensure username ≥ 3 characters, password ≥ 5 characters. Also adhere to the Password Policy Configuration.
Client stuck in "pending"	Admin hasn't granted access	Review and approve from Client Registry interface.
Connection failures after registration	Missing permissions	Assign appropriate roles to the newly created user.
Multiple failed connection attempts	Incorrect credentials	Verify credentials match exactly what was registered.
Client disconnecting after successful connection	Permission issues	Ensure publish/subscribe permissions are correctly assigned.