+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1511120 +++ ====================================================================== Description of problem: We have been having quite a few customers off late reporting setup issues with the error as defined in summary. In all these cases, we have seen that the underlying error is something different but the customer sees only "Unexpected comma or semicolon found at the end of the DN string." This error is very misleading and they are unable to determine the exact cause until we at support ask for debug logs to determine the actual cause. In one of the case, the actual problem was : The connection reader was unable to successfully complete TLS negotiation: LDAPException(resultCode=91 (connect error), errorMessage='Hostname verification failed because the expected hostname '<fqdn>' was not found in peer certificate..." We need some changes to showcase the actual error at these times. (Originally by Anitha Udgiri)
Verified with: ovirt-engine-extension-aaa-ldap-setup-1.3.6-1.el7ev.noarch Login sequence executed successfully
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3426
sync2jira