community.general.ldap_search module – Search for entries in a LDAP server
Note
This module is part of the community.general collection (version 4.8.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 community.general
.
To use it in a playbook, specify: community.general.ldap_search
.
New in version 0.2.0: of community.general
Parameters
Parameter |
Comments |
---|---|
A list of attributes for limiting the result. Use an actual list or a comma-separated string. |
|
A DN to bind with. If this is omitted, we’ll try a SASL bind with the EXTERNAL mechanism as default. If this is blank, we’ll use an anonymous bind. |
|
The password to use with bind_dn. |
|
The LDAP DN to search in. |
|
Used for filtering the LDAP search result. Default: “(objectClass=*)” |
|
Set the referrals chasing behavior.
Choices:
|
|
The class to use for SASL authentication. possible choices are Choices:
|
|
Set to Choices:
|
|
The LDAP scope to use. Choices:
|
|
The server_uri parameter may be a comma- or whitespace-separated list of URIs containing only the schema, the host, and the port fields. The default value lets the underlying LDAP client library look for a UNIX domain socket in its default location. Note that when using multiple URIs you cannot determine to which URI your client gets connected. For URIs containing additional fields, particularly when using commas, behavior is undefined. Default: “ldapi:///” |
|
If true, we’ll use the START_TLS LDAP extension. Choices:
|
|
If set to This should only be used on sites using self-signed certificates. Choices:
|
Notes
Note
The default authentication settings will attempt to use a SASL EXTERNAL bind over a UNIX domain socket. This works well with the default Ubuntu install for example, which includes a
cn=peercred,cn=external,cn=auth
ACL rule allowing root to modify the server configuration. If you need to use a simple bind to access your server, pass the credentials in bind_dn and bind_pw.
Examples
- name: Return all entries within the 'groups' organizational unit.
community.general.ldap_search:
dn: "ou=groups,dc=example,dc=com"
register: ldap_groups
- name: Return GIDs for all groups
community.general.ldap_search:
dn: "ou=groups,dc=example,dc=com"
scope: "onelevel"
attrs:
- "gidNumber"
register: ldap_group_gids
Authors
Sebastian Pfahl (@eryx12o45)
Collection links
Issue Tracker Repository (Sources) Submit a bug report Request a feature Communication