Thank you. I know that we use SAMAccountName since:
# ldapsearch -LLL -H ldap://adserver:9999 -b 'dc=com,dc=local' -D 'TEST\xxxx' -w 'xxxxxx' '(sAMAccountName=fim.testnew)' works, however when I set the filter, to SAMAccountName={0} it results in: The filter sAMAccountName=TEST\5fim.testnew is invalid. I tried without the DOMAIN\ too The filter sAMAccountName=fim.testnew is invalid. On Thursday, July 30, 2015 at 3:23:30 PM UTC-4, Jason Haar wrote: > > You've got a bad filter. There is no "uid" field in AD, you either need to > use sAMAccountName or userPrincipalName > > Use "sAMAccountName" is you are a single domain, or "userPrincipalName" if > you have multiple domains in a single forest (and use the GC ldap port > [3268] instead of standard ldap) > > Jason > > On Friday, July 31, 2015 at 4:25:01 AM UTC+12, Aram Mirzadeh wrote: >> >> >> Hi, >> >> I'm trying to connect GrayLog2 to our local ActiveDirectory server and >> having no luck. >> >> I'm getting a ":-| User Check and {check mark} Login Check" when >> configuring and testing the user of a user. >> >> *Base DN is*: dc=<company>,dc=local >> >> *Search Pattern is*: (&(objectClass=person)(uid={0})) >> I have also tried: >> =organizationalPerson >> =Users >> =user >> >> *Display Name attribute*: displayName >> >> I'm 100% sure of the Base DN and displayName being valid, however the >> search is an open issue. >> >> Any thoughts? >> > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/2dfac8cb-db9e-4581-a948-64dfd6f2fb33%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
