fortinet.fortimanager.fmgr_application_list module – Configure application control lists.
Note
This module is part of the fortinet.fortimanager collection (version 2.1.5).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install fortinet.fortimanager
.
To use it in a playbook, specify: fortinet.fortimanager.fmgr_application_list
.
New in version 2.10: of fortinet.fortimanager
Synopsis
This module is able to configure a FortiManager device.
Examples include all parameters and values which need to be adjusted to data sources before usage.
Parameters
Parameter |
Comments |
---|---|
the parameter (adom) in requested url |
|
the top level parameters set |
|
Enable/disable replacement messages for blocked applications. Choices:
|
|
comments |
|
Enable/disable enforcement of protocols over selected ports. Choices:
|
|
Enable/disable deep application inspection. Choices:
|
|
Default-Network-Services. |
|
Entry ID. |
|
Port number. |
|
Network protocols. Choices:
|
|
Action for protocols not white listed under selected port. Choices:
|
|
Enable/disable default application port enforcement for allowed applications. Choices:
|
|
Entries. |
|
Pass or block traffic, or reset connection for traffic from this application. Choices:
|
|
ID of allowed applications. |
|
Application behavior filter. |
|
Category ID list. |
|
ID of excluded applications. |
|
Entry ID. |
|
Enable/disable logging for this application list. Choices:
|
|
Enable/disable packet logging. Choices:
|
|
Parameters. |
|
Parameter ID. |
|
Members. |
|
Parameter. |
|
Parameter name. |
|
Parameter value. |
|
Parameter value. |
|
Per-IP traffic shaper. |
|
Application popularity filter (1 - 5, from least to most popular). Choices:
|
|
Application protocol filter. |
|
Quarantine method. Choices:
|
|
Duration of quarantine. (Format ###d##h##m, minimum 1m, maximum 364d23h59m, default = 5m). Requires quarantine set to … |
|
Enable/disable quarantine logging. Choices:
|
|
Count of the rate. |
|
Duration (sec) of the rate. |
|
Rate limit mode. Choices:
|
|
Track the packet protocol field. Choices:
|
|
Risk, or impact, of allowing traffic from this application to occur (1 - 5; Low, Elevated, Medium, High, and Critical). |
|
Session TTL (0 = default). |
|
Traffic shaper. |
|
Reverse traffic shaper. |
|
Application Sub-category ID list. |
|
Application technology filter. |
|
Application vendor filter. |
|
Enable/disable extended logging. Choices:
|
|
Enable/disable forced inclusion of SSL deep inspection signatures. Choices:
|
|
List name. |
|
Basic application protocol signatures allowed by default. Choices:
|
|
Action for other applications. Choices:
|
|
Enable/disable logging for other applications. Choices:
|
|
P2P applications to be black listed. Choices:
|
|
P2P applications to be blocklisted. Choices:
|
|
Replacement message group. |
|
Pass or block traffic from unknown applications. Choices:
|
|
Enable/disable logging for unknown applications. Choices:
|
|
only set to True when module schema diffs with FortiManager API structure, module continues to execute without validating parameters Choices:
|
|
Enable/Disable logging for task Choices:
|
|
The overridden method for the underlying Json RPC request Choices:
|
|
the rc codes list with which the conditions to fail will be overriden |
|
the rc codes list with which the conditions to succeed will be overriden |
|
the directive to create, update or delete an object Choices:
|
|
the adom to lock for FortiManager running in workspace mode, the value can be global and others including root |
|
the maximum time in seconds to wait for other user to release the workspace lock Default: 300 |
Notes
Note
Running in workspace locking mode is supported in this FortiManager module, the top level parameters workspace_locking_adom and workspace_locking_timeout help do the work.
To create or update an object, use state present directive.
To delete an object, use state absent directive.
Normally, running one module can fail when a non-zero rc is returned. you can also override the conditions to fail or succeed with parameters rc_failed and rc_succeeded
Examples
- name: gathering fortimanager facts
hosts: fortimanager00
gather_facts: no
connection: httpapi
collections:
- fortinet.fortimanager
vars:
ansible_httpapi_use_ssl: True
ansible_httpapi_validate_certs: False
ansible_httpapi_port: 443
tasks:
- name: retrieve all the application list
fmgr_fact:
facts:
selector: 'application_list'
params:
adom: 'ansible'
list: ''
- hosts: fortimanager00
collections:
- fortinet.fortimanager
connection: httpapi
vars:
ansible_httpapi_use_ssl: True
ansible_httpapi_validate_certs: False
ansible_httpapi_port: 443
tasks:
- name: Configure application control lists.
fmgr_application_list:
adom: ansible
state: present
application_list:
app-replacemsg: enable
comment: 'ansible-test-comment'
deep-app-inspection: enable
extended-log: disable
name: 'ansible-test'
other-application-action: pass
other-application-log: disable
unknown-application-action: pass
unknown-application-log: disable
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The full url requested Returned: always Sample: “/sys/login/user” |
|
The status of api request Returned: always Sample: 0 |
|
The descriptive message of the api response Returned: always Sample: “OK.” |
Authors
Link Zheng (@chillancezen)
Jie Xue (@JieX19)
Frank Shen (@fshen01)
Hongbin Lu (@fgtdev-hblu)