fortinet.fortios.fortios_firewall_access_proxy – Configure Access Proxy in Fortinet’s FortiOS and FortiGate.
Note
This plugin is part of the fortinet.fortios collection (version 2.1.3).
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.fortios
.
To use it in a playbook, specify: fortinet.fortios.fortios_firewall_access_proxy
.
New in version 2.10: of fortinet.fortios
Synopsis
This module is able to configure a FortiGate or FortiOS (FOS) device by allowing the user to set and modify firewall feature and access_proxy category. Examples include all parameters and values need to be adjusted to datasources before usage. Tested with FOS v6.0.0
Requirements
The below requirements are needed on the host that executes this module.
ansible>=2.9.0
Parameters
Parameter |
Comments |
---|---|
Token-based authentication. Generated from GUI of Fortigate. |
|
Enable/Disable logging for task. Choices:
|
|
Configure Access Proxy. |
|
Set API Gateway. |
|
Time in minutes that client web browsers should keep a cookie. Default is 60 minutes. 0 = no time limit. |
|
Domain that HTTP cookie persistence should apply to. |
|
Enable/disable use of HTTP cookie domain from host field in HTTP. Choices:
|
|
Generation of HTTP cookie to be accepted. Changing invalidates all existing cookies. |
|
Limit HTTP cookie persistence to the specified path. |
|
Control sharing of cookies across API Gateway. same-ip means a cookie from one virtual server can be used by another. Disable stops cookie sharing. Choices:
|
|
Enable/disable verification that inserted HTTPS cookies are secure. Choices:
|
|
API Gateway ID. |
|
Method used to distribute sessions to real servers. Choices:
|
|
Configure how to make sure that clients connect to the same server every time they make a request that is part of the same session. Choices:
|
|
Select the real servers that this Access Proxy will distribute traffic to. |
|
Address or address group of the real server. Source firewall.address.name firewall.addrgrp.name. |
|
Enable to check the responsiveness of the real server before forwarding traffic. Choices:
|
|
Protocol of the health check monitor to use when polling to determine server”s connectivity status. Choices:
|
|
Enable/disable holddown timer. Server will be considered active and reachable once the holddown period has expired (30 seconds). Choices:
|
|
HTTP server domain name in HTTP header. |
|
Real server ID. |
|
IP address of the real server. |
|
Port for communicating with the real server. |
|
Port for communicating with the real server. |
|
Set access-proxy SSH client certificate profile. Source firewall.access-proxy-ssh-client-cert.name. |
|
One or more server host key. |
|
Server host key name. Source firewall.ssh.host-key.name. |
|
Enable/disable SSH real server host key validation. Choices:
|
|
Set the status of the real server to active so that it can accept traffic, or on standby or disabled so no traffic is sent. Choices:
|
|
TCP forwarding server type. Choices:
|
|
Weight of the real server. If weighted load balancing is enabled, the server with the highest weight gets more connections. |
|
SAML service provider configuration for VIP authentication. Source user.saml.name. |
|
Service. Choices:
|
|
Permitted encryption algorithms for the server side of SSL full mode sessions according to encryption strength. Choices:
|
|
SSL/TLS cipher suites to offer to a server, ordered by priority. |
|
Cipher suite name. Choices:
|
|
SSL/TLS cipher suites priority. |
|
SSL/TLS versions that the cipher suite can be used with. Choices:
|
|
Number of bits to use in the Diffie-Hellman exchange for RSA encryption of SSL sessions. Choices:
|
|
Highest SSL/TLS version acceptable from a server. Choices:
|
|
Lowest SSL/TLS version acceptable from a server. Choices:
|
|
URL pattern to match. |
|
Type of url-map. Choices:
|
|
Virtual host. Source firewall.access-proxy-virtual-host.name. |
|
Set IPv6 API Gateway. |
|
Time in minutes that client web browsers should keep a cookie. Default is 60 minutes. 0 = no time limit. |
|
Domain that HTTP cookie persistence should apply to. |
|
Enable/disable use of HTTP cookie domain from host field in HTTP. Choices:
|
|
Generation of HTTP cookie to be accepted. Changing invalidates all existing cookies. |
|
Limit HTTP cookie persistence to the specified path. |
|
Control sharing of cookies across API Gateway. same-ip means a cookie from one virtual server can be used by another. Disable stops cookie sharing. Choices:
|
|
Enable/disable verification that inserted HTTPS cookies are secure. Choices:
|
|
API Gateway ID. |
|
Method used to distribute sessions to real servers. Choices:
|
|
Configure how to make sure that clients connect to the same server every time they make a request that is part of the same session. Choices:
|
|
Select the real servers that this Access Proxy will distribute traffic to. |
|
Address or address group of the real server. Source firewall.address6.name firewall.addrgrp6.name. |
|
Enable to check the responsiveness of the real server before forwarding traffic. Choices:
|
|
Protocol of the health check monitor to use when polling to determine server”s connectivity status. Choices:
|
|
Enable/disable holddown timer. Server will be considered active and reachable once the holddown period has expired (30 seconds). Choices:
|
|
HTTP server domain name in HTTP header. |
|
Real server ID. |
|
IPv6 address of the real server. |
|
Port for communicating with the real server. |
|
Port for communicating with the real server. |
|
Set access-proxy SSH client certificate profile. Source firewall.access-proxy-ssh-client-cert.name. |
|
One or more server host key. |
|
Server host key name. Source firewall.ssh.host-key.name. |
|
Enable/disable SSH real server host key validation. Choices:
|
|
Set the status of the real server to active so that it can accept traffic, or on standby or disabled so no traffic is sent. Choices:
|
|
TCP forwarding server type. Choices:
|
|
Weight of the real server. If weighted load balancing is enabled, the server with the highest weight gets more connections. |
|
SAML service provider configuration for VIP authentication. Source user.saml.name. |
|
Service. Choices:
|
|
Permitted encryption algorithms for the server side of SSL full mode sessions according to encryption strength. Choices:
|
|
SSL/TLS cipher suites to offer to a server, ordered by priority. |
|
Cipher suite name. Choices:
|
|
SSL/TLS cipher suites priority. |
|
SSL/TLS versions that the cipher suite can be used with. Choices:
|
|
Number of bits to use in the Diffie-Hellman exchange for RSA encryption of SSL sessions. Choices:
|
|
Highest SSL/TLS version acceptable from a server. Choices:
|
|
Lowest SSL/TLS version acceptable from a server. Choices:
|
|
URL pattern to match. |
|
Type of url-map. Choices:
|
|
Virtual host. Source firewall.access-proxy-virtual-host.name. |
|
Enable/disable to request client certificate. Choices:
|
|
Action of an empty client certificate. Choices:
|
|
Method used to distribute sessions to SSL real servers. Choices:
|
|
Access Proxy name. |
|
Select the SSL real servers that this Access Proxy will distribute traffic to. |
|
Real server ID. |
|
IP address of the real server. |
|
Port for communicating with the real server. |
|
Set the status of the real server to active so that it can accept traffic, or on standby or disabled so no traffic is sent. Choices:
|
|
Weight of the real server. If weighted load balancing is enabled, the server with the highest weight gets more connections. |
|
Enable/disable SSH real server public key authentication. Choices:
|
|
Server SSH public key authentication settings. |
|
Name of the SSH server public key authentication CA. Source firewall.ssh.local-ca.name. |
|
Configure certificate extension for user certificate. |
|
Critical option. Choices:
|
|
Name of certificate extension. |
|
Name of certificate extension. |
|
Type of certificate extension. Choices:
|
|
Enable/disable appending permit-agent-forwarding certificate extension. Choices:
|
|
Enable/disable appending permit-port-forwarding certificate extension. Choices:
|
|
Enable/disable appending permit-pty certificate extension. Choices:
|
|
Enable/disable appending permit-user-rc certificate extension. Choices:
|
|
Enable/disable appending permit-x11-forwarding certificate extension. Choices:
|
|
Enable/disable appending source-address certificate critical option. This option ensure certificate only accepted from FortiGate source address. Choices:
|
|
Virtual IP name. Source firewall.vip.name. |
|
Member attribute path to operate on. Delimited by a slash character if there are more than one attribute. Parameter marked with member_path is legitimate for doing member operation. |
|
Add or delete a member under specified attribute path. When member_state is specified, the state option is ignored. Choices:
|
|
Indicates whether to create or remove the object. Choices:
|
|
Virtual domain, among those defined previously. A vdom is a virtual instance of the FortiGate that can be configured and used as a different unit. Default: “root” |
Examples
- hosts: fortigates
collections:
- fortinet.fortios
connection: httpapi
vars:
vdom: "root"
ansible_httpapi_use_ssl: yes
ansible_httpapi_validate_certs: no
ansible_httpapi_port: 443
tasks:
- name: Configure Access Proxy.
fortios_firewall_access_proxy:
vdom: "{{ vdom }}"
state: "present"
access_token: "<your_own_value>"
firewall_access_proxy:
api_gateway:
-
http_cookie_age: "4"
http_cookie_domain: "<your_own_value>"
http_cookie_domain_from_host: "disable"
http_cookie_generation: "7"
http_cookie_path: "<your_own_value>"
http_cookie_share: "disable"
https_cookie_secure: "disable"
id: "11"
ldb_method: "static"
persistence: "none"
realservers:
-
address: "<your_own_value> (source firewall.address.name firewall.addrgrp.name)"
health_check: "disable"
health_check_proto: "ping"
holddown_interval: "enable"
http_host: "myhostname"
id: "20"
ip: "<your_own_value>"
mappedport: "<your_own_value>"
port: "23"
ssh_client_cert: "<your_own_value> (source firewall.access-proxy-ssh-client-cert.name)"
ssh_host_key:
-
name: "default_name_26 (source firewall.ssh.host-key.name)"
ssh_host_key_validation: "disable"
status: "active"
type: "tcp-forwarding"
weight: "30"
saml_server: "<your_own_value> (source user.saml.name)"
service: "http"
ssl_algorithm: "high"
ssl_cipher_suites:
-
cipher: "TLS-AES-128-GCM-SHA256"
priority: "36"
versions: "tls-1.0"
ssl_dh_bits: "768"
ssl_max_version: "tls-1.0"
ssl_min_version: "tls-1.0"
url_map: "<your_own_value>"
url_map_type: "sub-string"
virtual_host: "myhostname (source firewall.access-proxy-virtual-host.name)"
api_gateway6:
-
http_cookie_age: "45"
http_cookie_domain: "<your_own_value>"
http_cookie_domain_from_host: "disable"
http_cookie_generation: "48"
http_cookie_path: "<your_own_value>"
http_cookie_share: "disable"
https_cookie_secure: "disable"
id: "52"
ldb_method: "static"
persistence: "none"
realservers:
-
address: "<your_own_value> (source firewall.address6.name firewall.addrgrp6.name)"
health_check: "disable"
health_check_proto: "ping"
holddown_interval: "enable"
http_host: "myhostname"
id: "61"
ip: "<your_own_value>"
mappedport: "<your_own_value>"
port: "64"
ssh_client_cert: "<your_own_value> (source firewall.access-proxy-ssh-client-cert.name)"
ssh_host_key:
-
name: "default_name_67 (source firewall.ssh.host-key.name)"
ssh_host_key_validation: "disable"
status: "active"
type: "tcp-forwarding"
weight: "71"
saml_server: "<your_own_value> (source user.saml.name)"
service: "http"
ssl_algorithm: "high"
ssl_cipher_suites:
-
cipher: "TLS-AES-128-GCM-SHA256"
priority: "77"
versions: "tls-1.0"
ssl_dh_bits: "768"
ssl_max_version: "tls-1.0"
ssl_min_version: "tls-1.0"
url_map: "<your_own_value>"
url_map_type: "sub-string"
virtual_host: "myhostname (source firewall.access-proxy-virtual-host.name)"
client_cert: "disable"
empty_cert_action: "accept"
ldb_method: "static"
name: "default_name_88"
realservers:
-
id: "90"
ip: "<your_own_value>"
port: "92"
status: "active"
weight: "94"
server_pubkey_auth: "disable"
server_pubkey_auth_settings:
auth_ca: "<your_own_value> (source firewall.ssh.local-ca.name)"
cert_extension:
-
critical: "no"
data: "<your_own_value>"
name: "default_name_101"
type: "fixed"
permit_agent_forwarding: "enable"
permit_port_forwarding: "enable"
permit_pty: "enable"
permit_user_rc: "enable"
permit_x11_forwarding: "enable"
source_address: "enable"
vip: "<your_own_value> (source firewall.vip.name)"
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Build number of the fortigate image Returned: always Sample: “1547” |
|
Last method used to provision the content into FortiGate Returned: always Sample: “PUT” |
|
Last result given by FortiGate on last operation applied Returned: always Sample: “200” |
|
Master key (id) used in the last call to FortiGate Returned: success Sample: “id” |
|
Name of the table used to fulfill the request Returned: always Sample: “urlfilter” |
|
Path of the table used to fulfill the request Returned: always Sample: “webfilter” |
|
Internal revision number Returned: always Sample: “17.0.2.10658” |
|
Serial number of the unit Returned: always Sample: “FGVMEVYYQT3AB5352” |
|
Indication of the operation’s result Returned: always Sample: “success” |
|
Virtual domain used Returned: always Sample: “root” |
|
Version of the FortiGate Returned: always Sample: “v5.6.3” |
Authors
Link Zheng (@chillancezen)
Jie Xue (@JieX19)
Hongbin Lu (@fgtdev-hblu)
Frank Shen (@frankshen01)
Miguel Angel Munoz (@mamunozgonzalez)
Nicolas Thomas (@thomnico)