Resolve console login issues and LDAPSearchException errors when using Windows Active Directory with Puppet Enterprise 3.8.x to 2017.2.x

Related articles

• Console LDAP authentication is broken after upgrading to Puppet Enterprise 2018.1 or later
• Errors authenticating with your LDAP user account in the Puppet Enterprise console after generating a new self-signed certificate for your directory server
• Change the hostname of a primary server (master) in Puppet Enterprise 2018.1 and later
• Fix "java.lang.OutOfMemoryError" errors in Puppet Enterprise 2015.2 to 2017.3
• Installing the Windows agent with PowerShell fails with the error "Could not create SSL/TLS secure channel" in Puppet Enterprise 2018.1 to 2019.1