'samaccountname' AD attribute missing when browsing

[gabby3]

Hi Guys,

I can't seem to pull out the sAMAccountname attribute when browsing the LDAP directory from within ServiceNow. I'm using the default filter from SN:

(&(objectClass=person)(sn=*)(!(objectClass=computer))(!(userAccountControl:1.2.840.113556.1.4.803:=2)))

This is what I get when browsing the LDAP:

Does this have something to do with the LDAP's security? Or is there something within SN that I need to configure?

Thanks,
G

[Atul Kumar2]

Hi Cris,

All attributes comes as per the OU(Organization unit). Please check with ldap team if person as ou contains the sAMAccountname attributes or is there any attributes with different name corresponding to the sAMAccountname like name etc.

If you have a access to the ldap system then you check the person (ou) and look for column name for the sAMAccountname or any unique column that look like samaccountname.

Hope this helps.

Regards,

Atul Kumar

[gabby3]

Hi Atul,

Yeah, they have the samaccountname as an attribute:

Screenshot from AD:

Now I don't know why SN is not picking it up.

THanks!

[Atul Kumar2]

Hi Cris,

I believe you have given a certain filter criteria hence it is not coming. if there is not any restrictions from the LDAP server.

If you are accessing common name (cn) then put filter like this

(cn=*)

It will pull all the attributes from the ldap server and put the specific unique value under query field so that based on that it will fetch the records.

Like below.

Hope this helps.

Regards,

Atul Kumar

[tony_barratt]

Hi Cris,

Have you tried entering a specific DN for a specific user in the LDAP Browser Distinguished Name field and checking what attributes are returned?

If the sAMAccountname is not shown as an attribute with an appropriate value you should reach out to your LDAP admins for insight into why not.

If it is then further tests can be made, adding the filter and searching the LDAP Nodes for example.

Best Regards

Tony

edit:

My suggestion was based on browsing   from the LDAP server

additionally you could browse from the OU