check_point.mgmt.cp_mgmt_trusted_client module – Manages trusted-client objects on Checkpoint over Web Services API
Note
This module is part of the check_point.mgmt collection (version 4.0.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 check\_point.mgmt
.
To use it in a playbook, specify: check_point.mgmt.cp_mgmt_trusted_client
.
New in check_point.mgmt 2.1.0
Synopsis
Manages trusted-client objects on Checkpoint devices including creating, updating and removing objects.
All operations are performed over Web Services API.
Parameters
Parameter |
Comments |
---|---|
Publish the current session if changes have been performed after task completes. Choices:
|
|
Color of the object. Should be one of existing colors. Choices:
|
|
Comments string. |
|
The level of detail for some of the fields in the response can vary from showing only the UID value of the object to a fully detailed representation of the object. Choices:
|
|
Domains to be added to this profile. Use domain name only. See example below, “add-trusted-client (with domain)”. |
|
Apply changes ignoring errors. You won’t be able to publish such a changes. If ignore-warnings flag was omitted - warnings will also be ignored. Choices:
|
|
Apply changes ignoring warnings. Choices:
|
|
IPv4 or IPv6 address. If both addresses are required use ipv4-address and ipv6-address fields explicitly. |
|
First IP address in the range. If both IPv4 and IPv6 address ranges are required, use the ipv4-address-first and the ipv6-address-first fields instead. |
|
Last IP address in the range. If both IPv4 and IPv6 address ranges are required, use the ipv4-address-first and the ipv6-address-first fields instead. |
|
IPv4 address. |
|
First IPv4 address in the range. |
|
Last IPv4 address in the range. |
|
IPv6 address. |
|
First IPv6 address in the range. |
|
Last IPv6 address in the range. |
|
IPv4 or IPv6 mask length. If both masks are required use mask-length4 and mask-length6 fields explicitly. |
|
IPv4 mask length. |
|
IPv6 mask length. |
|
Let this trusted client connect to all Multi-Domain Servers in the deployment. Choices:
|
|
Object name. |
|
State of the access rule (present or absent). Defaults to present. Choices:
|
|
Collection of tag identifiers. |
|
Trusted client type. Choices:
|
|
Version of checkpoint. If not given one, the latest version taken. |
|
Wait for the task to end. Such as publish task. Choices:
|
|
How many minutes to wait until throwing a timeout error. Default: |
|
IP wild card (e.g. 192.0.2.*). |
Examples
- name: add-trusted-client
cp_mgmt_trusted_client:
name: my client
state: present
type: ANY
- name: set-trusted-client
cp_mgmt_trusted_client:
ip_address: 192.0.2.1
mask_length: '24'
name: my client
state: present
type: NETMASK
- name: delete-trusted-client
cp_mgmt_trusted_client:
name: my client
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The checkpoint object created or updated. Returned: always, except when deleting the object. |