fortinet.fortimanager.fmgr_user_ldap_dynamicmapping module – Configure LDAP server entries.
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_user_ldap_dynamicmapping
.
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 (ldap) in requested url |
|
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 top level parameters set |
|
no description |
|
Name. |
|
Vdom. |
|
Account key filter, using the UPN as the search filter. |
|
Account-Key-Name. |
|
Account key processing operation, either keep or strip domain string of UPN in the token. Choices:
|
|
Enable/disable AntiPhishing credential backend. Choices:
|
|
CA certificate name. |
|
Common name identifier for the LDAP server. The common name identifier for most LDAP servers is “cn”. |
|
Distinguished name used to look up entries on the LDAP server. |
|
Filter. |
|
Group. |
|
Filter used for group matching. |
|
Group member checking methods. Choices:
|
|
Filter used for group searching. |
|
Group-Object-Search-Base. |
|
Search base used for group searching. |
|
Specify outgoing interface to reach server. |
|
Specify how to select outgoing interface to reach server. Choices:
|
|
Name of attribute from which to get group membership. |
|
Enable/disable obtaining of user information. Choices:
|
|
no description |
|
Name of attribute to get password hash. |
|
Enable/disable password expiry warnings. Choices:
|
|
Enable/disable online password renewal. Choices:
|
|
Port to be used for communication with the LDAP server (default = 389). |
|
Retrieve-Protection-Profile. |
|
no description Choices:
|
|
Secondary LDAP server CN domain name or IP. |
|
Port to be used for authentication. Choices:
|
|
LDAP server CN domain name or IP. |
|
Enable/disable LDAP server identity check (verify server domain name/IP address against the server certificate). Choices:
|
|
Source IP for communications to LDAP server. |
|
Source port to be used for communication with the LDAP server. |
|
Minimum supported protocol version for SSL/TLS connections (default is to follow system global setting). Choices:
|
|
Tertiary LDAP server CN domain name or IP. |
|
Enable/disable two-factor authentication. Choices:
|
|
Authentication method by FortiToken Cloud. Choices:
|
|
Notification method for user activation by FortiToken Cloud. Choices:
|
|
Authentication type for LDAP searches. Choices:
|
|
MS Exchange server from which to fetch user information. |
|
Username (full DN) for initial binding. |
|
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
- 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 dynamic mappings of LDAP server
fmgr_fact:
facts:
selector: 'user_ldap_dynamicmapping'
params:
adom: 'ansible'
ldap: 'ansible-test-ldap' # name
dynamic_mapping: ''
- 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 dynamic mappings of LDAP server
fmgr_user_ldap_dynamicmapping:
bypass_validation: False
adom: ansible
ldap: ansible-test-ldap # name
state: present
user_ldap_dynamicmapping:
_scope:
-
name: FGT_AWS # need a valid device name
vdom: root # need a valid vdom name under the device
dn: ansible-test-dn
password: fortinet
port: 9000
server: ansible
username: ansible-test-dyn
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)