AD Authentication Broken in 3.2

Hello

Can you check the audit log to see what is occurring when the AD attempt fails. I have found a similar issue that is occurring for me. Also, have you tried deleting and recreating the AD configuration?

OMEnt 3.2 AD login

Thanks

I have one entry in the audit log that says my credentials are wrong. But none of the other login attempts ever make it to the log. I'm guessing they just never timeout. The login page just stays at the three floating dots forever.

Actually I just let one login go for as long as it wanted and the login page said my credentials are wrong, but the audit log says login was successful...

It doesn't look like it matters if the account is real or not. Login still hangs. I get similar results on multiple machines. There was one instance where failure happened immediately but once I refreshed the page it didn't happen again and there was no record of any login in the audit log.

And yes I have to reboot the appliance after each failed attempt to login before I can login with local admin again.

Can you test with invalid logins to see if they timeout faster?

correctdomain/invalid_user doesntmatter
correctdomain/valid_user invalidpassword
wrongdomain/doesntmatter doesntmatter

Also, on the test that you just did where it took a long time to fail AD login, did you have to restart OMEnt to be able to login with a local account?

It looks like there is some extreme lag happening between a login attempt and when the record shows up in the audit log. My attempt at logging in with a fake account took about 20 minutes to show up in the audit log. And the only reason I saw it at all was because I got an email alert about it.

I set up a domain controller to test. I am able to log in as fast as using local credentials, and I am not experiencing any issues.

Was AD login working without issue previously? Are there any other advanced configuration options that you are using?

If you haven't already, I suggested deleting and re-importing the user groups. You may also want to delete and recreate the directory services. Something might have been corrupted during the update process.

@nivekdrol 

Sorry to hear that appliance is unable to login through Local User Account.

Can you please try rebooting the appliance manually from Terminal User Interface / Text User Interface and then launch the appliance in different browser by clearing cache of the browser.

Thanks,

Anil Kumar V K R

Dell EMC

i can't even login local admin after the update it just sits in the log in screen spinning on the 3 dots. I had another systems sit on the 50 min reboot page, I had to shut it down and bring it back up and that seemed to have fixed that one. but the first system won't let me in at all any suggestions?

rebooted I can log in admin now, logged out tried ad creds and it times out, tried to log back in admin and it times out, rebooted again logged in admin to try to readd AD and group to appliance. When I do test connection it just times out with no error messge. looks like the appliance is fubared. I'm having the same issue as OP if you try to login with ad creds it hangs and if you try admin again it hangs. I have to reboot it to get admin to log in

i didn't really have anything setup for the first instance so I just redeployed 3.2 fresh install and when testing connection for ad it took forever! Like 5 minutes to test connection. it finally said test successful and I added AD domain. when trying to Import ad group its taking forever and it errors out with unknown. man this version seems to have alot of issues

3.2 **bleep** redeployed to 3.1 added ad and reimported groups took less than 15 secs 

@nivekdrol 

Is it possible to share the AD setup info w Dell IPS via an SR?

#iwork4dell