Hi Christian, > Am 12.05.2020 um 11:57 schrieb Christian Mack > (christian.m...@uni-konstanz.de) <users@sogo.nu>: > > Hello > > Am 11.05.20 um 12:51 schrieb Götz Reinicke (goetz.reini...@filmakademie.de): >> Hi, >> >> a user informed me, he could not login to sogo any more , that might be >> since we updated to sogo 4.3.1 from 4.2 …. He had no accurate time. >> >> SOGoRootPage Login from ‚xxx.xxx.xxx.xxx' for user ‚myuser' might not have >> worked - password policy: 65535 grace: -1 expire: -1 bound: 0 >> >> Checking the SOGo log, I can see a couple of that message also for different >> users. >> >> The calling user can login to imap, smtp, wifi and some other services with >> the same credentials without a problem. >> >> May be something has changed … ? >> > > Do you see an error message above the "Login ... might not have worked" > message?
I do see the ldap search request and filter …. > Did your user clear his browser cache after the upgrade? Yes, but … the user was not sure that he ever used SOGo with that account …. And I was pointed into a different false direction: I found, that the account had one attribute missing, which I use in the search filter :-/ so from my POV the user could NEVER use SOGo … ;) May be the error message could also be a bit more specific, if a user tries to login and could not be found in the LDAP … Thx for taking your time and regards . Götz
smime.p7s
Description: S/MIME cryptographic signature
