netapp.ontap.na_ontap_ldap_client module – NetApp ONTAP LDAP client
Note
This module is part of the netapp.ontap collection (version 21.20.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 netapp.ontap
.
To use it in a playbook, specify: netapp.ontap.na_ontap_ldap_client
.
New in version 2.9.0: of netapp.ontap
Requirements
The below requirements are needed on the host that executes this module.
Ansible 2.9
Python3 netapp-lib (2018.11.13) or later. Install using ‘pip install netapp-lib’
netapp-lib 2020.3.12 is strongly recommended as it provides better error reporting for connection issues.
A physical or virtual clustered Data ONTAP system. The modules support Data ONTAP 9.1 and onward.
REST support requires ONTAP 9.6 or later.
To enable http on the cluster you must run the following commands ‘set -privilege advanced;’ ‘system services web modify -http-enabled true;’
Parameters
Parameter |
Comments |
---|---|
Active Directory Domain Name. |
|
LDAP base DN. |
|
LDAP search scope. Choices:
|
|
The cluster uses the CIFS server’s credentials to bind to the LDAP server. Choices:
|
|
LDAP bind user DN. |
|
LDAP bind user password. |
|
path to SSL client cert file (.pem). not supported with python 2.6. |
|
Enable or disable a new feature. This can be used to enable an experimental feature or disable a new feature that breaks backward compatibility. Supported keys and values are subject to change without notice. Unknown keys are ignored. |
|
The hostname or IP address of the ONTAP instance. |
|
Override the default port (80 or 443) with this port |
|
Enable and disable https. Ignored when using REST as only https is supported. Ignored when using SSL certificate authentication as it requires SSL. Choices:
|
|
path to SSL client key file. |
|
Comma separated list of LDAP servers. FQDN’s or IP addreses. Required if state=present. |
|
Minimal LDAP server bind level. Choices:
|
|
The name of LDAP client configuration. |
|
The ontap api version to use |
|
Password for the specified user. |
|
Preferred Active Directory (AD) Domain Controllers. |
|
LDAP server query timeout. |
|
LDAP Referral Chasing. Choices:
|
|
LDAP schema. Required if state=present. default schemas - ‘AD-IDMU’, ‘AD-SFU’, ‘MS-AD-BIS’, ‘RFC-2307’. custom schemas are allowed as well. |
|
Client Session Security. Choices:
|
|
Whether the specified LDAP client configuration exist or not. Choices:
|
|
LDAP server TCP port. |
|
Whether to use REST or ZAPI. always – will always use the REST API if the module supports REST. A warning is issued if the module does not support REST. An error is issued if a module option is not supported in REST. never – will always use ZAPI if the module supports ZAPI. An error may be issued if a REST option is not supported in ZAPI. auto – will try to use the REST API if the module supports REST and modules options are supported. Reverts to ZAPI otherwise. Default: “auto” |
|
Start TLS on LDAP connection. Choices:
|
|
This can be a Cluster-scoped or SVM-scoped account, depending on whether a Cluster-level or SVM-level API is required. For more information, please read the documentation https://mysupport.netapp.com/NOW/download/software/nmsdk/9.4/. Two authentication methods are supported
To use a certificate, the certificate must have been installed in the ONTAP cluster, and cert authentication must have been enabled. |
|
If set to This should only set to Choices:
|
|
vserver/svm that holds LDAP client configuration. |
Examples
- name: Create LDAP client
netapp.ontap.na_ontap_ldap_client:
state: present
name: 'example_ldap'
vserver: 'vserver1'
ldap_servers: 'ldap1.example.company.com,ldap2.example.company.com'
base_dn: 'dc=example,dc=company,dc=com'
hostname: "{{ netapp_hostname }}"
username: "{{ netapp_username }}"
password: "{{ netapp_password }}"
Authors
Milan Zink (@zeten30) /