fortinet.fortimanager.fmgr_firewall_sslsshprofile – Configure SSL/SSH protocol options.
Note
This plugin is part of the fortinet.fortimanager collection (version 2.1.4).
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_firewall_sslsshprofile
.
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 top level parameters set |
|
Enable/disable exempting servers by FortiGuard allowlist. Choices:
|
|
Enable/disable blocking SSL-based botnet communication by FortiGuard certificate blacklist. Choices:
|
|
Enable/disable blocking SSL-based botnet communication by FortiGuard certificate blocklist. Choices:
|
|
CA certificate used by SSL Inspection. |
|
Optional comments. |
|
no description |
|
Action based on certificate validation failure. Choices:
|
|
Action based on certificate validation timeout. Choices:
|
|
Action based on received client certificate. Choices:
|
|
Action based on server certificate is expired. Choices:
|
|
Proxy traffic after the TCP 3-way handshake has been established (not before). Choices:
|
|
Action based on server certificate is revoked. Choices:
|
|
Check the SNI in the client hello message with the CN or SAN fields in the returned server certificate. Choices:
|
|
Configure protocol inspection status. Choices:
|
|
Action based on the SSL cipher used being unsupported. Choices:
|
|
Action based on the SSL negotiation used being unsupported. Choices:
|
|
Action based on server certificate is not issued by a trusted CA. Choices:
|
|
no description |
|
Action based on certificate validation failure. Choices:
|
|
Action based on certificate validation timeout. Choices:
|
|
Action based on received client certificate. Choices:
|
|
Action based on server certificate is expired. Choices:
|
|
Ports to use for scanning (1 - 65535, default = 443). |
|
Action based on server certificate is revoked. Choices:
|
|
Check the SNI in the client hello message with the CN or SAN fields in the returned server certificate. Choices:
|
|
Configure protocol inspection status. Choices:
|
|
Action based on the SSL cipher used being unsupported. Choices:
|
|
Action based on the SSL negotiation used being unsupported. Choices:
|
|
Action based on server certificate is not issued by a trusted CA. Choices:
|
|
no description |
|
Action based on certificate probe failure. Choices:
|
|
Action based on certificate validation failure. Choices:
|
|
Action based on certificate validation timeout. Choices:
|
|
Action based on received client certificate. Choices:
|
|
Action based on server certificate is expired. Choices:
|
|
Ports to use for scanning (1 - 65535, default = 443). |
|
Proxy traffic after the TCP 3-way handshake has been established (not before). Choices:
|
|
Action based on server certificate is revoked. Choices:
|
|
Check the SNI in the client hello message with the CN or SAN fields in the returned server certificate. Choices:
|
|
Configure protocol inspection status. Choices:
|
|
Action based on the SSL cipher used being unsupported. Choices:
|
|
Action based on the SSL negotiation used being unsupported. Choices:
|
|
Action based on server certificate is not issued by a trusted CA. Choices:
|
|
no description |
|
Action based on certificate validation failure. Choices:
|
|
Action based on certificate validation timeout. Choices:
|
|
Action based on received client certificate. Choices:
|
|
Action based on server certificate is expired. Choices:
|
|
Ports to use for scanning (1 - 65535, default = 443). |
|
Proxy traffic after the TCP 3-way handshake has been established (not before). Choices:
|
|
Action based on server certificate is revoked. Choices:
|
|
Check the SNI in the client hello message with the CN or SAN fields in the returned server certificate. Choices:
|
|
Configure protocol inspection status. Choices:
|
|
Action based on the SSL cipher used being unsupported. Choices:
|
|
Action based on the SSL negotiation used being unsupported. Choices:
|
|
Action based on server certificate is not issued by a trusted CA. Choices:
|
|
Enable/disable inspection of MAPI over HTTPS. Choices:
|
|
Name. |
|
no description |
|
Action based on certificate validation failure. Choices:
|
|
Action based on certificate validation timeout. Choices:
|
|
Action based on received client certificate. Choices:
|
|
Action based on server certificate is expired. Choices:
|
|
Ports to use for scanning (1 - 65535, default = 443). |
|
Proxy traffic after the TCP 3-way handshake has been established (not before). Choices:
|
|
Action based on server certificate is revoked. Choices:
|
|
Check the SNI in the client hello message with the CN or SAN fields in the returned server certificate. Choices:
|
|
Configure protocol inspection status. Choices:
|
|
Action based on the SSL cipher used being unsupported. Choices:
|
|
Action based on the SSL negotiation used being unsupported. Choices:
|
|
Action based on server certificate is not issued by a trusted CA. Choices:
|
|
Enable/disable inspection of RPC over HTTPS. Choices:
|
|
Certificate used by SSL Inspection to replace server certificate. |
|
Re-sign or replace the servers certificate. Choices:
|
|
no description |
|
Action based on certificate validation failure. Choices:
|
|
Action based on certificate validation timeout. Choices:
|
|
Action based on received client certificate. Choices:
|
|
Action based on server certificate is expired. Choices:
|
|
Ports to use for scanning (1 - 65535, default = 443). |
|
Proxy traffic after the TCP 3-way handshake has been established (not before). Choices:
|
|
Action based on server certificate is revoked. Choices:
|
|
Check the SNI in the client hello message with the CN or SAN fields in the returned server certificate. Choices:
|
|
Configure protocol inspection status. Choices:
|
|
Action based on the SSL cipher used being unsupported. Choices:
|
|
Action based on the SSL negotiation used being unsupported. Choices:
|
|
Action based on server certificate is not issued by a trusted CA. Choices:
|
|
no description |
|
Level of SSL inspection. Choices:
|
|
Ports to use for scanning (1 - 65535, default = 443). |
|
Proxy traffic after the TCP 3-way handshake has been established (not before). Choices:
|
|
Relative strength of encryption algorithms accepted during negotiation. Choices:
|
|
Enable/disable SSH tunnel policy check. Choices:
|
|
Configure protocol inspection status. Choices:
|
|
Action based on SSH version being unsupported. Choices:
|
|
no description |
|
Action based on certificate validation failure. Choices:
|
|
Action based on certificate validation timeout. Choices:
|
|
Action based on received client certificate. Choices:
|
|
Action based on server certificate is expired. Choices:
|
|
Level of SSL inspection. Choices:
|
|
Action based on server certificate is revoked. Choices:
|
|
Check the SNI in the client hello message with the CN or SAN fields in the returned server certificate. Choices:
|
|
Action based on the SSL cipher used being unsupported. Choices:
|
|
Action based on the SSL negotiation used being unsupported. Choices:
|
|
Action based on server certificate is not issued by a trusted CA. Choices:
|
|
Enable/disable logging SSL anomalies. Choices:
|
|
Ssl-Exempt. |
|
IPv4 address object. |
|
IPv6 address object. |
|
FortiGuard category ID. |
|
ID number. |
|
Exempt servers by regular expression. |
|
Type of address object (IPv4 or IPv6) or FortiGuard category. Choices:
|
|
Exempt servers by wildcard FQDN. |
|
Enable/disable logging SSL exemptions. Choices:
|
|
Enable/disable logging SSL negotiation. Choices:
|
|
Ssl-Server. |
|
Action based on client certificate request during the FTPS handshake. Choices:
|
|
Action based on received client certificate during the FTPS handshake. Choices:
|
|
Action based on client certificate request during the HTTPS handshake. Choices:
|
|
Action based on received client certificate during the HTTPS handshake. Choices:
|
|
SSL server ID. |
|
Action based on client certificate request during the IMAPS handshake. Choices:
|
|
Action based on received client certificate during the IMAPS handshake. Choices:
|
|
IPv4 address of the SSL server. |
|
Action based on client certificate request during the POP3S handshake. Choices:
|
|
Action based on received client certificate during the POP3S handshake. Choices:
|
|
Action based on client certificate request during the SMTPS handshake. Choices:
|
|
Action based on received client certificate during the SMTPS handshake. Choices:
|
|
Action based on client certificate request during an SSL protocol handshake. Choices:
|
|
Action based on received client certificate during an SSL protocol handshake. Choices:
|
|
Configure ALPN option. Choices:
|
|
Untrusted CA certificate used by SSL Inspection. |
|
Enable/disable the use of SSL server table for SSL offloading. Choices:
|
|
Enable/disable exempting servers by FortiGuard whitelist. 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
- 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 SSL/SSH protocol options.
fmgr_firewall_sslsshprofile:
bypass_validation: False
adom: ansible
state: present
firewall_sslsshprofile:
comment: 'ansible-comment1'
mapi-over-https: disable #<value in [disable, enable]>
name: 'ansible-test'
use-ssl-server: disable #<value in [disable, enable]>
whitelist: enable #<value in [disable, enable]>
- 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 SSL/SSH protocol options
fmgr_fact:
facts:
selector: 'firewall_sslsshprofile'
params:
adom: 'ansible'
ssl-ssh-profile: ''
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)