fortinet.fortimanager.fmgr_icap_profile module – Configure ICAP profiles.
Note
This module is part of the fortinet.fortimanager collection (version 2.3.0).
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_icap_profile
.
New in fortinet.fortimanager 2.0.0
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 token to access FortiManager without using username and password. |
|
the parameter (adom) in requested url |
|
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:
|
|
Authenticate Ansible client with forticloud API access token. |
|
the top level parameters set |
|
Enable/disable allowance of 204 response from ICAP server. Choices:
|
|
204 response size limit to be saved by ICAP client in megabytes |
|
Enable/disable chunked encapsulation Choices:
|
|
Comment. |
|
no description Choices:
|
|
no description Choices:
|
|
Action to take if the ICAP server cannot be contacted when processing a file transfer. Choices:
|
|
Path component of the ICAP URI that identifies the file transfer processing service. |
|
ICAP server to use for a file transfer. |
|
Enable/disable UTM log when infection found Choices:
|
|
Icap-Headers. |
|
Enable/disable use of base64 encoding of HTTP content. Choices:
|
|
HTTP header content. |
|
HTTP forwarded header ID. |
|
HTTP forwarded header name. |
|
The allowed HTTP methods that will be sent to ICAP server for further processing. Choices:
|
|
ICAP profile name. |
|
Enable/disable preview of data to ICAP server. Choices:
|
|
Preview data length to be sent to ICAP server. |
|
Replacement message group. |
|
Enable/disable whether an HTTP request is passed to an ICAP server. Choices:
|
|
Action to take if the ICAP server cannot be contacted when processing an HTTP request. Choices:
|
|
Path component of the ICAP URI that identifies the HTTP request processing service. |
|
ICAP server to use for an HTTP request. |
|
Default action to ICAP response modification Choices:
|
|
Respmod-Forward-Rules. |
|
Action to be taken for ICAP server. Choices:
|
|
Header-Group. |
|
Enable/disable case sensitivity when matching header. Choices:
|
|
HTTP header regular expression. |
|
HTTP header. |
|
ID. |
|
Address object for the host. |
|
(list) HTTP response status code. |
|
Address name. |
|
Enable/disable whether an HTTP response is passed to an ICAP server. Choices:
|
|
Action to take if the ICAP server cannot be contacted when processing an HTTP response. Choices:
|
|
Path component of the ICAP URI that identifies the HTTP response processing service. |
|
Enable/disable addition of req-hdr for ICAP response modification Choices:
|
|
ICAP server to use for an HTTP response. |
|
Scan progress interval value. |
|
Enable/disable bypassing of ICAP server for streaming content. Choices:
|
|
Time |
|
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: |
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
- hosts: fortimanager-inventory
collections:
- fortinet.fortimanager
connection: httpapi
vars:
ansible_httpapi_use_ssl: True
ansible_httpapi_validate_certs: False
ansible_httpapi_port: 443
tasks:
- name: Configure ICAP profiles.
fmgr_icap_profile:
bypass_validation: False
workspace_locking_adom: <value in [global, custom adom including root]>
workspace_locking_timeout: 300
rc_succeeded: [0, -2, -3, ...]
rc_failed: [-2, -3, ...]
adom: <your own value>
state: <value in [present, absent]>
icap_profile:
methods:
- delete
- get
- head
- options
- post
- put
- trace
- other
- connect
name: <string>
replacemsg-group: <string>
request: <value in [disable, enable]>
request-failure: <value in [error, bypass]>
request-path: <string>
request-server: <string>
response: <value in [disable, enable]>
response-failure: <value in [error, bypass]>
response-path: <string>
response-server: <string>
streaming-content-bypass: <value in [disable, enable]>
icap-headers:
-
base64-encoding: <value in [disable, enable]>
content: <string>
id: <integer>
name: <string>
preview: <value in [disable, enable]>
preview-data-length: <integer>
response-req-hdr: <value in [disable, enable]>
respmod-default-action: <value in [bypass, forward]>
respmod-forward-rules:
-
action: <value in [bypass, forward]>
header-group:
-
case-sensitivity: <value in [disable, enable]>
header: <string>
header-name: <string>
id: <integer>
host: <string>
http-resp-status-code: <list or integer>
name: <string>
204-response: <value in [disable, enable]>
204-size-limit: <integer>
chunk-encap: <value in [disable, enable]>
extension-feature:
- scan-progress
file-transfer:
- ssh
- ftp
file-transfer-failure: <value in [error, bypass]>
file-transfer-path: <string>
file-transfer-server: <string>
icap-block-log: <value in [disable, enable]>
scan-progress-interval: <integer>
timeout: <integer>
comment: <string>
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The result of the request. Returned: always |
|
The full url requested. Returned: always Sample: |
|
The status of api request. Returned: always Sample: |
|
The api response. Returned: always |
|
The descriptive message of the api response. Returned: always Sample: |
|
The information of the target system. Returned: always |
|
The status the request. Returned: always Sample: |
|
Warning if the parameters used in the playbook are not supported by the current FortiManager version. Returned: complex |