fortinet.fortimanager.fmgr_pkg_firewall_proxypolicy module – Configure proxy policies.
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_pkg_firewall_proxypolicy
.
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 |
|
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 parameter (pkg) in requested url |
|
the top level parameters set |
|
Access Proxy. |
|
Accept or deny traffic matching the policy parameters. Choices:
|
|
Name of an existing Application list. |
|
Name of an existing Antivirus profile. |
|
Name of an existing CIFS profile. |
|
Optional comments. |
|
Decrypted traffic mirror. |
|
When enabled, the ownership enforcement will be done at policy level. Choices:
|
|
Web proxy disclaimer setting: by domain, policy, or user. Choices:
|
|
Name of an existing DLP sensor. |
|
Destination address objects. |
|
When enabled, destination addresses match against any address EXCEPT the specified destination addresses. Choices:
|
|
IPv6 destination address objects. |
|
Destination interface names. |
|
Name of an existing email filter profile. |
|
Name of an existing file-filter profile. |
|
Global web-based manager visible label. |
|
Names of group objects. |
|
Enable/disable HTTP tunnel authentication. Choices:
|
|
Name of an existing ICAP profile. |
|
Enable/disable use of Internet Services for this policy. If enabled, destination address and service are not used. Choices:
|
|
Custom Internet Service name. |
|
Custom Internet Service group name. |
|
Internet Service group name. |
|
Internet Service ID. |
|
Internet Service name. |
|
When enabled, Internet Services match against any internet service EXCEPT the selected Internet Service. Choices:
|
|
Name of an existing IPS sensor. |
|
VDOM-specific GUI visible label. |
|
Enable/disable logging traffic through the policy. Choices:
|
|
Enable/disable policy log traffic start. Choices:
|
|
Name of an existing MMS profile. |
|
Policy name. |
|
Policy ID. |
|
Name of IP pool object. |
|
Name of profile group. |
|
Name of an existing Protocol options profile. |
|
Determine whether the firewall policy allows security profile groups or single profiles only. Choices:
|
|
Type of explicit proxy. Choices:
|
|
Redirect URL for further explicit web proxy processing. |
|
Authentication replacement message override group. |
|
Enable/disable scanning of connections to Botnet servers. Choices:
|
|
Name of schedule object. |
|
Name of service objects. |
|
When enabled, services match against any service EXCEPT the specified destination services. Choices:
|
|
TTL in seconds for sessions accepted by this policy (0 means use the system default session TTL). |
|
Name of an existing Spam filter profile. |
|
Source address objects (must be set when using Web proxy). |
|
When enabled, source addresses match against any address EXCEPT the specified source addresses. Choices:
|
|
IPv6 source address objects. |
|
Source interface names. |
|
Name of an existing SSH filter profile. |
|
Redirect SSH traffic to matching transparent proxy policy. Choices:
|
|
Name of an existing SSL SSH profile. |
|
Enable/disable the active status of the policy. Choices:
|
|
Names of object-tags applied to address. Tags need to be preconfigured in config system object-tag. Separate multiple tags wit… |
|
Enable to use the IP address of the client to connect to the server. Choices:
|
|
Names of user objects. |
|
Enable the use of UTM profiles/sensors/lists. Choices:
|
|
Universally Unique Identifier (UUID; automatically assigned but can be manually reset). |
|
Name of an existing VideoFilter profile. |
|
Name of an existing VoIP profile. |
|
Name of an existing Web application firewall profile. |
|
Enable/disable web caching. Choices:
|
|
Enable/disable web caching for HTTPS (Requires deep-inspection enabled in ssl-ssh-profile). Choices:
|
|
Name of an existing Web filter profile. |
|
Name of web proxy forward server. |
|
Name of web proxy profile. |
|
ZTNA EMS Tag names. |
|
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
- 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 proxy policies.
fmgr_pkg_firewall_proxypolicy:
bypass_validation: False
adom: ansible
pkg: ansible # package name
state: present
pkg_firewall_proxypolicy:
action: accept #<value in [accept, deny, redirect]>
comments: ansible-comment
dstaddr: all
dstintf: any
policyid: 1
schedule: always
service: ALL
srcaddr: all
srcintf: any
status: disable
- 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 proxy policies
fmgr_fact:
facts:
selector: 'pkg_firewall_proxypolicy'
params:
adom: 'ansible'
proxy-policy: ''
pkg: 'ansible' # package name
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)