Browse documentation
Credential types
JOATOS supports nine credential types, covering network devices, servers, and vendor APIs. You choose the type when adding a credential, and it can't be changed afterwards.
Network devices
| Type | Key fields |
|---|---|
| SNMP v2c | Community string |
| SNMP v3 | Username, auth protocol + key, privacy protocol + key |
| UniFi Controller | Controller URL, API key, site ID |
| Aruba CX | Username, password |
| MikroTik | Username, password, REST API port, verify-SSL option |
| FortiGate API | API token, HTTPS port, VDOM, verify-SSL option. Needed for a firewall's Rules, Zones and Security tabs — see Understanding device types. |
Use SNMP for general device polling (switches, routers, firewalls, APs, UPSs); the vendor APIs (UniFi, Aruba CX, MikroTik) unlock richer data than SNMP alone.
Servers
| Type | Key fields |
|---|---|
| SSH (Linux/Unix) | Username, port, password or private key (+ passphrase) |
| WMI (Windows) | Username, password, domain, HTTPS option, verify-SSL option |
| Proxmox VE | Host, API token ID, API token secret, port |
Use SSH for Linux, WMI for Windows, and Proxmox VE for Proxmox hypervisors — see Choosing a collection method.
Notes & tips
- For SSH, you can authenticate with a password or a private key (with an optional passphrase) — leave the password blank when using a key.
- For MikroTik and WMI with self-signed certificates, leave Verify SSL certificate unchecked.
- WMI needs a local Windows account, not a domain one. JOATOS uses Basic authentication to WinRM, which Windows only accepts for accounts local to the target machine. Leave Domain blank (or put the machine's own name in it); a real domain name will always fail with a 401. The account also needs to be a local administrator with
LocalAccountTokenFilterPolicy=1— see Preparing a Windows server for agentless scanning. - Proxmox uses an API token (
user@realm!tokenname) plus its secret, not a plain password.