ESET Protect 8 login issues

[Jens_R 0]

Hello everyone,

we've updated our ESMC 7.2 (I think) to ESET Protect 8.0.1238.0 over the weekend and since then the only user able to login is the default "Administrator". Usually we use AD admin users to login and this worked fine before the update. We are also not able to use newly created native users without an AD connection to login. There's always the same error message: "Login failed: Invalid username or password". Does anyone have an idea where this issue might be coming from? Thanks in advance!

[Xfred 0]

I've the same problem!

[Marcos 5,074]

Couldn't it be that the username contains at least one accented character?

[MartinK 378]

3 hours ago, Marcos said:

Couldn't it be that the username contains at least one accented character?

... or password?

[Xfred 0]

No

The password contains a lowercase letter, an uppercase letter, a number, and a special character.

[Jens_R 0]

In my case all the user accounts have lowercase letters and at least one password contains upper- and lowercase letters as well as numbers and special characters. Also wouldn't I see an error message in ESET Protect if I wanted to create user accounts with forbidden passwords?

[Jens_R 0]

The username notation was a good idea though: I have just tried to create a username with upper- and lowercase letters and it worked. I have also asked a colleague to login with his account that contains uppercase letters and it worked for him as well.

@ ESET-Team: Could you please ask the devs to have a look at it if possible?

[Jens_R 0]

Sorry for Spamming in advance

I have another update. It's not the usernames. That was just a coincidence. It seems like it ESET Protect can't handle umlauts like ä, ö, ü anymore.

[MichalJ 434]

Just a note. We have just released a hotfix version of ESET Protect Webconsole, that should address the issue with login, when username / password contains a special characters. You can upgrade the console to the current version by running a component upgrade task on your ESET PROTECT server machine. IT will update the webconsole to the version 8.0.175.0 which should resolve those issues.