# LDAPS issue AWX TLS **URL:** \ **Category:** AWX Project\ **Tags:** awx\ **Created:** [September 26, 2019, 4:55pm UTC](https://forum.ansible.com/t/ldaps-issue-awx-tls/31368 "2019-09-26T16:55:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Nilesh\_Jaiswal](https://avatars.discourse-cdn.com/v4/letter/n/5f9b8f/32.png) [@Nilesh\_Jaiswal](https://forum.ansible.com/u/Nilesh_Jaiswal)\ **Post date:** [September 26, 2019, 4:55pm UTC](https://forum.ansible.com/t/ldaps-issue-awx-tls/31368/1 "2019-09-26T16:55:24Z")
Dear All, When I configure authentication using LDAPS I see this error below. 2019-09-26 15:56:06,996 DEBUG django\_auth\_ldap Initiating TLS 2019-09-26 15:56:07,039 WARNING django\_auth\_ldap Caught LDAPError while authenticating myusername: SERVER\_DOWN({‘info’: ‘error:14090086:SSL routines:ssl3\_get\_server\_certificate:certificate verify failed (unable to get local issuer certificate)’, ‘desc’: “Can’t contact LDAP server”},) But I do have provided the valid certificate. my LDAP configuration did not show drop down list for LDAP Group Type, what might be the problem? But Authentication using LDAP works well, with no TLS switch enable. Any help will be appreciated? ---
**Author:** ![rpetrell](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rpetrell](https://forum.ansible.com/u/rpetrell)\ **Post date:** [September 26, 2019, 5:19pm UTC](https://forum.ansible.com/t/ldaps-issue-awx-tls/31368/2 "2019-09-26T17:19:48Z")
I think you might be seeing a bug we recently fixed: [https://github.com/ansible/awx/pull/4190](https://github.com/ansible/awx/pull/4190) What version of AWX are you on? ---
**Author:** ![rpetrell](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rpetrell](https://forum.ansible.com/u/rpetrell)\ **Post date:** [September 26, 2019, 6:07pm UTC](https://forum.ansible.com/t/ldaps-issue-awx-tls/31368/3 "2019-09-26T18:07:23Z")
Nilesh, You’ll likely have to upgrade AWX to work around this bug - the version you’re on was released about a year ago now, and the reason you’re seeing the error is that this version of AWX is on an older version of Django we updated from awhile ago. ---
**Author:** ![hashim\_vayalar](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/hashim_vayalar/32/10641_2.png) [@hashim\_vayalar](https://forum.ansible.com/u/hashim_vayalar)\ **Post date:** [September 23, 2020, 1:21am UTC](https://forum.ansible.com/t/ldaps-issue-awx-tls/31368/4 "2020-09-23T01:21:22Z")
I am getting below error still in Ansible Tower “Can’t contact LDAP server”, ‘info’: ‘error:14090086:SSL routines:ssl3\_get\_server\_certificate:certificate verify failed (unable to get local issuer certificate)’}, Ansible Tower version is 3.7.0 ---
**Author:** ![jowestco](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jowestco](https://forum.ansible.com/u/jowestco)\ **Post date:** [September 24, 2020, 2:35am UTC](https://forum.ansible.com/t/ldaps-issue-awx-tls/31368/5 "2020-09-24T02:35:20Z")
If you are on tower 3.7.0 you can open a ticket with red hat support instead of waiting for help in the community mailing list. -John ---
**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\ **Post date:** [September 24, 2020, 2:36am UTC](https://forum.ansible.com/t/ldaps-issue-awx-tls/31368/6 "2020-09-24T02:36:49Z")
I have seen this before. Our issue was related to selinux on our not being mapped properly on the host ---
**Author:** ![hashim\_vayalar](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/hashim_vayalar/32/10641_2.png) [@hashim\_vayalar](https://forum.ansible.com/u/hashim_vayalar)\ **Post date:** [September 24, 2020, 2:38am UTC](https://forum.ansible.com/t/ldaps-issue-awx-tls/31368/7 "2020-09-24T02:38:40Z")
We already scheduled meeting with red hat officials to show our LDAP setup and asking for their opinion. I guess the issue is with LDAP certs that we have updated yesterday. Seems working fine now. Anyway scheduled a meeting with rehat support team.