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

  1. Go to Settings → Connectors → Add connector and pick the type.
  2. Fill in the address and the login. Each type explains exactly what it needs.
  3. 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.

SystemConnects withTo monitorTo make changes
Proxmox VEAPI tokenPVEAuditorPVEVMAdmin + datastore rights
XCP-ngXen Orchestra tokenAn XO user with read rightsAn XO admin, or ACLs on the pools / VMs
KVM / libvirtThe host’s Linux (SSH) connectorA user in the libvirt groupSame, or sudo
VMware ESXi / vCentervSphere APIRead-only roleVM power, snapshot, provision
LinuxSSH (key recommended)A normal usersudo
WindowsWinRM (HTTPS 5986 recommended)A normal userLocal admin
DockerSocket proxy or SSHRead-only proxyProxy with actions allowed
Kubernetes / k3skubeconfig or tokenviewedit / admin
Active DirectoryLDAPSRead 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 DNSAPI tokenZone:ReadDNS:Edit
Microsoft 365 / AzureEntra ID app registrationGraph read permissions, Azure ReaderMatching write permissions
Firewalls (OPNsense, pfSense, MikroTik)REST API keyRead privilegesWrite privileges
FortiGateREST API admin tokenRead-only admin profile (with this server as a trusted host)— (read-only connector)
Palo Alto (PAN-OS)XML API key, or user name and passwordRead-only admin— (read-only connector)
Check PointManagement API (R80+), user or API keyRead-only permission profile— (read-only connector)
Meraki MXDashboard API keyRead-only organization access— (read-only connector)
SonicWall / Sophos FirewallSonicOS 7 REST API / SFOS XML API (enable the API, allow this server’s address)A read-only admin— (read-only connector)
Cisco Firepower / ASAFMC REST API / SSHRead-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 / v3A read-only community, or a v3 user with a password— (read-only)
Citrix Virtual Apps and DesktopsWinRM to a Delivery Controller (and the license, StoreFront and PVS servers)Read Only AdministratorHelp Desk / Machine Catalog / Delivery Group Administrator
Backups (PBS, Veeam)API tokenAudit / viewer roleOperator / admin role
CrowdSecLocal APIBouncer 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

StepWhereWhat you do
1Settings → Credentials → New credentialSave the shared login once: SSH key, Windows login, API token…
2Settings → Connectors → Add manyPick the type and credential, paste one server per line (name, host) or load a CSV
3Same pageAdd 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.