About ADOMs
Enabling ADOMs alters the structure and available functionality of the GUI and CLI according to whether you are logging in as the admin
administrator, and, if you are not logging in as the admin
administrator, the administrator account’s assigned access profile.
The |
Characteristics of the CLI and GUI when ADOMs are enabled
|
Admin administrator account |
Other administrators |
Access to config system global |
Yes |
No |
Can create administrator accounts |
Yes |
No |
Can enter all ADOMs |
Yes |
No |
- If ADOMs are enabled and you log in as
admin
, a superset of the typical CLI commands appear, allowing unrestricted access and ADOM configuration. - If ADOMs are enabled and you log in as any other administrator, you enter the ADOM assigned to your account. A subset of the typical menus or CLI commands appear, allowing access only to only logs, reports, quarantine files, content archives, IP aliases, and LDAP queries specific to your ADOM. You cannot access Global Configuration, or enter other ADOMs.
config system global
contains settings used by the FortiAnalyzer unit itself and settings shared by ADOMs, such as the device list, RAID, and administrator accounts. It does not include ADOM-specific settings or data, such as logs and reports. When configuring other administrator accounts, an additional option appears allowing you to restrict other administrators to an ADOM.
By default, administrator accounts other than the admin
account are assigned to the root
ADOM, which includes all devices in the device list. By creating ADOMs that contain a subset of devices in the device list, and assigning them to administrator accounts, you can restrict other administrator accounts to a subset of the FortiAnalyzer unit’s total devices or VDOMs.
The admin
administrator account cannot be restricted to an ADOM. Other administrators are restricted to their ADOM, and cannot configure ADOMs or Global Configuration.
The maximum number of ADOMs varies by FortiAnalyzer model.