Administration¶
Domain management¶
The product organizes discovered endpoints by domain (host header). Domains can be enabled or disabled to control which traffic is analyzed and stored.
Figure 5. The Domains page lists active and disabled domains. Each domain can be disabled or deleted.¶
To manage domains:
Go to Manage > Domains.
To pause analysis for a domain while retaining its historical data, select Disable.
To remove a domain and all of its associated data, select Delete.
To manually add a domain that has not yet been observed in traffic, select Add Domain.
Disabled domains appear in the Disabled Domains section at the bottom of the page.
User management¶
The product supports local user accounts with role-based access.
Figure 6. The Users page allows the administrator to create, edit, and remove local user accounts.¶
Roles¶
Role |
Capabilities |
|---|---|
Admin |
Full access, including configuration, user management, licensing, BIG-IP integration, and all operational tasks |
Maintainer |
Operational access, including domain management, API discovery rules, and enforcement actions; cannot manage users or licenses |
Viewer |
Read-only access to the dashboard, endpoint inventory, and exports |
Manage users¶
To manage users:
Go to System > Users.
To add a user, complete the inline form with Username, Role (Admin, Maintainer, or Viewer), and Password, then select Add.
To modify an existing user, select Edit in the Actions column.
Important
Change the default admin password on first login.
API Discovery Rules (Policy)¶
API Discovery Rules determine how traffic is classified and which actions are taken. Rules are evaluated top-down; the first matching rule is applied.
Figure 7. The Policy page displays ordered API Discovery Rules. The implied rule at the bottom always runs and is managed by backend defaults.¶
A rule consists of:
Field |
Purpose |
|---|---|
Name |
Human-readable identifier for the rule |
Domains |
Scope of domains the rule applies to |
Condition |
Match criteria, edited through the View / Edit Condition button |
Action |
Action to take when the rule matches (for example, NON-API) |
Comment |
Optional free-text comment |
The implied rule at the bottom always runs and is managed by backend defaults. After modifying rules, select Apply Rules to commit the changes.