Active Directory User Authentication Failing

Ignition
1

I've got a user who has been struggling to get authenticated into Ignition.

We authenticate through AD & when they try to log on, this is what I see in the log files.

image
image1213×199 19.8 KB

Observations:

  • Other users do not have issues logging on.
  • I have seen the user log on to other systems that use the same AD creds without an issue.
  • The account isn't locked in AD.
  • We have verified the users account is in fact assigned to the right AD groups (which is probably irrelevant anyhow, given the error message we're getting)
  • I've tried disabling account locking in Ignition temporarily as well just for good measure without any change.
  • User could previously log on but can no longer do so.
  • User has had a semi-recent password change but it's unclear if they were able to log on after it.

I'm not sure what I could try from the Ignition side, or how it might be causing AD to return an authentication error, but is there any chance this issue could stem from the Ignition side?

2

LDAP error code 49 is LDAP_INVALID_CREDENTIALS.

data 52e is ERROR_LOGON_FAILURE (The user name or password is incorrect).

I suppose it's always possible there's some problem on the Ignition side, but it's not the obvious answer here.

3

I would agree generally.

When I sat there & watched him log on to a different system though with no issue, using the same Active Directory credentials & then failing when he tried through Ignition.... I just don't know.

We've been at this for a few weeks now. I can't hardly fathom he's really still typing his creds in wrong every time... but on the other hand, I'm also aware of what the error message states so I don't have a leg to stand on here :smile:

4

Yeah he's probably not typing them in wrong, but there's probably some AD weirdness going on. Cache somewhere, a restart needed somewhere, not sure...

5

Fair enough, caching had crossed my mind as well.

We've requested him to do a password reset. Maybe that'll sync things back up & resolve this. If not, I'm kind of baffled.

Appreciate it!

6

If not, try support. They've probably seen more weird real world issues than I have.

1 Like
7

Sounds good, will do. Thanks again!

8

Not sure what the issue causing it was ultimately, but seems a password reset of the account resolved it. Maybe something cached or out of sync somehow... but seems back in order with the reset. Thanks again & have a nice weekend.

2 Likes