microsoft.ad.debug_ldap_client module – Get host information for debugging LDAP connections
Note
This module is part of the microsoft.ad collection (version 1.4.1).
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 microsoft.ad
.
To use it in a playbook, specify: microsoft.ad.debug_ldap_client
.
New in microsoft.ad 1.1.0
Synopsis
Get information about the current Ansible host to debug LDAP connections and their capabilities.
Note
This module has a corresponding action plugin.
Attributes
Attribute |
Support |
Description |
---|---|---|
Support: full |
Indicates this has a corresponding action plugin so some parts of the options can be executed on the controller |
|
Support: full |
Supports being used with the |
|
Support: none |
Forces a ‘global’ task that does not execute per host, this bypasses per host templating and serial, throttle and other loop considerations Conditionals will work as if This action will not work normally outside of lockstep strategies |
|
Support: full |
Can run in check_mode and return changed status prediction without modifying target |
|
Support: none |
Will return details on what has changed (or possibly needs changing in check_mode), when in diff mode |
|
Platform: posix |
Target OS/families that can be operated against |
Notes
Note
See LDAP connection help for more information about LDAP connections.
The return values are not part of any contract and can change in the future. It is meant to give a snapshot of the Ansible host that can help debug LDAP connection issues and not be used as part of a normal playbook.
Examples
- name: Get information about the Ansible host's LDAP capabilities
microsoft.ad.debug_ldap_client:
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Details about the SRV LDAP server lookup. The values will only be populated if dnspython is installed. Returned: always |
|
The default port of the SRV record chosen. Returned: dnspython is installed Sample: |
|
The default hostname of the SRV record chosen. Returned: dnspython is installed Sample: |
|
Any exceptions that occurred when getting the SRV records. Returned: dnspython is installed Sample: |
|
The SRV records that were found during the LDAP server lookup. Returned: dnspython is installed |
|
The port of this SRV record. Returned: dnspython is installed and default_realm is found Sample: |
|
The record priority value. Returned: dnspython is installed and default_realm is found Sample: |
|
The target name of the SRV record. Returned: dnspython is installed and default_realm is found Sample: |
|
The record weight value. Returned: dnspython is installed and default_realm is found Sample: |
|
Details about the host Kerberos setup. The values will only be populated if krb5 is installed. Returned: always |
|
Details about the default Kerberos credential cache. Returned: krb5 is installed |
|
A list of credentials that is stored in the ccache. This requires Returned: krb5 is installed |
|
The client principal name the credential is for. Returned: krb5 >= 0.5.0 is installed Sample: |
|
The server principal name the credential is for. Returned: krb5 >= 0.5.0 is installed Sample: |
|
Any exceptions that occurred when getting the ccache information. Returned: krb5 is installed Sample: |
|
The default ccache type and name. Returned: krb5 is installed Sample: |
|
The default principal of the ccache Returned: krb5 is installed Sample: |
|
The default_realm as reported by Kerberos. This value is used for the automatic server lookup. Returned: krb5 is installed Sample: |
|
Exception details if the default realm could not be retrieved. Returned: krb5 is installed Sample: |
|
All the packages used by this collection for LDAP connections and their installed versions. If the package is not installed, or failed to import, the value is the traceback from the import process. This can be used to determine the availability of optional features like Kerberos authentication or server lookups. Returned: always |
|
The installed version of Returned: always Sample: |
|
The installed version of Returned: always Sample: |
|
The installed version of Returned: always Sample: |
|
The installed version of Returned: always Sample: |
|
The installed version of Returned: always Sample: |