> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/access/client-registry.md).

# Client Registry

Secure self-registration for simplified device management.

The **Client Registry** in Connectware provides a secure, automated mechanism for registering new clients, users, and hardware devices without manually handling credentials.

Instead of manually adding users through the [Admin UI](/2-6-1/access/admin-ui.md), this self-registration process allows clients to register themselves or be automatically registered when they connect to Connectware. This eliminates security risks associated with pre-shared credentials while reducing administrative overhead.

## Advantages of Self-Registration

Traditional client authorization methods often rely on manually creating users and sharing passwords, which introduces security vulnerabilities and administrative overhead. The Client Registry solves this by:

* Eliminating the need to manually distribute credentials.
* Enabling secure, automated credential exchange in the background.
* Providing administrator oversight while minimizing manual intervention.
* Supporting certificate-based authentication for enhanced security.

## Self-Registration Methods

| Self-Registration Method                  | Advantages                                                                                                                                                                                                                                                                                                                                      |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Self-Registering Clients via REST API** | <p>• Support for certificate signing requests (CSR)<br>• Ability to request specific roles and permissions<br>• Enhanced control over client configuration<br>• Suitable for distributed Connectware agents and advanced clients<br>• <a href="/2-6-1/access/client-registry/self-registering-clients-via-rest-api.md">More information</a></p> |
| **Self-Registering MQTT Clients**         | <p>• Works with any standard MQTT or HTTP client<br>• The client can generate random passwords automatically<br>• Simple process for basic device integration<br>• <a href="/2-6-1/access/client-registry/self-registering-mqtt-clients.md">More information</a></p>                                                                            |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/access/client-registry.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
