AD Authentication

Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question.
Don’t forget to select tags to help index your topic!

1. Describe your incident:

When setting up AD Authentication, if I when testing server connection, I can get a successful test if I leave the PW field blank, but the moment I enter a password it complains about a bad password, specifically:

80090308: LdapErr: DSID-0C09052B, comment: AcceptSecurityContext error, data 52f, v4f7c

I’m 100% sure it’s a correct password, we’re copy-pasting to be sure.

2. Describe your environment:

3. What steps have you already taken to try and solve the problem?

Tried different accounts.

4. How can the community help?

I’m clearly doing something wrong if merely adding a password causes that error. Tips for correcting would help.

I dont know for sure, but my hunch is that it’s not actually trying until yiu have the password.

Do you know that TLS is setup properly for LDAP and have other services using it correctly, that is always the first thing I check.

I’ve tried switching to TLS, which happens on port 636. We have multitudes of other services using it. Apparently only graylog seems to have password troubles. Should I switch to Ldap instead of Ad?

Even LDAP gives us the same results.

Figured it out. Needed a different (non-protected) user.

1 Like