LDAP issues for 2.1.0

Archives AWX Project
1

I’ve got my LDAP auth setup with the following information and I am pretty sure that it is working somewhat as I think it is finding my username properly, but it isn’t allowing me to login. Can someone please look over my settings and tell me what I’ve done wrong?

Also, one other thing I had saw done by others that might fix this was deleting cached credentials, but I can’t find the command to do that. Can someone tell me where to find the command short of nuking the docker container and refilling the information in again?

LDAP SERVER URI

ldap://servername.domain.local:389

LDAP BIND DN

CN=Ansible,OU=Service_Accounts,DC=domain,DC=local

LDAP USER SEARCH

[ "ou=LEVEL2,ou=LEVEL1,dc=domain,dc=local", "SCOPE_SUBTREE", "(sAMAccountName=%(user)s)" ]

LDAP GROUP SEARCH

`
[
“dc=domain,dc=local”,
“SCOPE_SUBTREE”,
“(objectClass=group)”
]

`

LDAP USER ATTRIBUTE MAP

{ "first_name": "givenName", "last_name": "sn", "email": "mail" }

LDAP USER FLAGS BY GROUP

{ "is_superuser": [ "cn=Domain Admins,ou=Users,dc=domain,dc=local" ] }

2

So when I am searching through the awx_web logs I see the warning message

“2018-11-20 16:05:22,851 WARNING django_auth_ldap Caught LDAPError while authenticating my_username: NO_SUCH_OBJECT({‘info’: “0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:\n\t’DC=domain,DC=local’\n”, ‘matched’: ‘DC=domain,DC=local’, ‘desc’: ‘No such object’},)”

I’m not sure why it isn’t able to match successfully. Any thoughts on what I’m missing here?

3

We had the same issue which we managed changing the samaccountname to uid and object class to group of unique names and a bad password for bind dn replaced to good ones .(as per the BIND DN created in ED/AD)

once i made above changed everything was good.

4

as well the bind dn

cn replaced with uid

5

So I made the following changes to my settings and it still isn’t woirking

Screen Shot 2018-11-20 at 10.26.18 AM.png
Screen Shot 2018-11-20 at 10.26.18 AM.png3690×2266 218 KB

6

Just a bump to see if anyone has any more ideas. I’m at a loss as to what is causing this. As a clarification it was working with a previous version of AWX and my domain servers. So I know it can work, but am just not sure where the disconnect is.

7

Hello,

I have another issue but not sure if it is related, in my case AWX has the group type drop down list empty, is it the same in your case ?

image.png

Thanks
Samer

8

Mine is also blank, but I ran across this to fill in the proper settings…

https://github.com/ansible/awx/issues/2586

This might fix your issue.