Connectors
Connect servers, hypervisors, DNS, firewalls, storage, cloud and smart home systems — one at a time or hundreds at once.
A connector is one system Opsaido can talk to: a Proxmox cluster, a Linux server, a DNS provider, a firewall. The assistant only uses tools for the systems you’ve connected.
Add one
- Go to Settings → Connectors → Add connector and pick the type.
- Fill in the address and the login. Each type explains exactly what it needs.
- Press Test connection. For SSH hosts, the host key is pinned on the first test.
Give Opsaido its own service account on each system, with only the rights you want the assistant to have. Read-only rights are enough to monitor and investigate.
What each system needs
The short version is below; Permissions lists exactly what to grant to look, to change and to delete, with Microsoft 365, Intune and Azure in detail.
| System | Connects with | To monitor | To make changes |
|---|---|---|---|
| Proxmox VE | API token | PVEAuditor | PVEVMAdmin + datastore rights |
| XCP-ng | Xen Orchestra token | An XO user with read rights | An XO admin, or ACLs on the pools / VMs |
| KVM / libvirt | The host’s Linux (SSH) connector | A user in the libvirt group | Same, or sudo |
| VMware ESXi / vCenter | vSphere API | Read-only role | VM power, snapshot, provision |
| Linux | SSH (key recommended) | A normal user | sudo |
| Windows | WinRM (HTTPS 5986 recommended) | A normal user | Local admin |
| Docker | Socket proxy or SSH | Read-only proxy | Proxy with actions allowed |
| Kubernetes / k3s | kubeconfig or token | view | edit / admin |
| Active Directory | LDAPS | Read on the OUs (any domain user) | Delegated admin rights on the OUs to manage users, computers and groups (create, change, reset passwords, move, delete) |
| Cloudflare DNS | API token | Zone:Read | DNS:Edit |
| Microsoft 365 / Azure | Entra ID app registration | Graph read permissions, Azure Reader | Matching write permissions |
| Firewalls (OPNsense, pfSense, MikroTik) | REST API key | Read privileges | Write privileges |
| FortiGate | REST API admin token | Read-only admin profile (with this server as a trusted host) | — (read-only connector) |
| Palo Alto (PAN-OS) | XML API key, or user name and password | Read-only admin | — (read-only connector) |
| Check Point | Management API (R80+), user or API key | Read-only permission profile | — (read-only connector) |
| Meraki MX | Dashboard API key | Read-only organization access | — (read-only connector) |
| SonicWall / Sophos Firewall | SonicOS 7 REST API / SFOS XML API (enable the API, allow this server’s address) | A read-only admin | — (read-only connector) |
| Cisco Firepower / ASA | FMC REST API / SSH | Read-only FMC user / a read-only ASA user (privilege 5 is enough for show commands) | — (read-only connector) |
| Switches, NAS, UPS, printers (any vendor) | SNMP v1 / v2c / v3 | A read-only community, or a v3 user with a password | — (read-only) |
| Citrix Virtual Apps and Desktops | WinRM to a Delivery Controller (and the license, StoreFront and PVS servers) | Read Only Administrator | Help Desk / Machine Catalog / Delivery Group Administrator |
| Backups (PBS, Veeam) | API token | Audit / viewer role | Operator / admin role |
| CrowdSec | Local API | Bouncer key (checks who is blocked) | Machine login (cscli machines add): alerts, ban, unban |
The full list of integrations is on the Integrations page.
Many servers with the same login
| Step | Where | What you do |
|---|---|---|
| 1 | Settings → Credentials → New credential | Save the shared login once: SSH key, Windows login, API token… |
| 2 | Settings → Connectors → Add many | Pick the type and credential, paste one server per line (name, host) or load a CSV |
| 3 | Same page | Add tags such as web or prod; Opsaido creates and tests the servers ten at a time |
Then:
- Rotate the password in the credential and every server using it picks it up.
- Ask by tag: “check updates on all #web servers”.
- Limit a role to a tag; servers added with that tag later are included automatically.
Hosts you can’t reach directly
For a DMZ, another site or an isolated VLAN, add a proxy gateway: a Linux or Windows machine that can reach them. See How connections work for the flow and set-up.
The same machine added twice — say as a Docker host and as a Linux host — is fine. Shell and file tasks use the SSH connector; container tasks use the Docker one.