-
-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SOME users AUTHENTICATIONFAILED after version update #969
Comments
I've analyzed the problem and see what is going on.
I will solve the bug and as workaround the user either removes the invalid settings of step 1 or sets the right credentials. |
My god, root cause has been user's fault to correct the password in the additional settings. Sorry for that one - but thank you for resolving the bug. |
I will close the bug when the fix lands in the commits. |
Confirm - the current release fixes the issue. Thank you very much. |
this is hard to reproduce as snappymail works for most users. For others, authentication does not work and the log throws (see below):
The same user can authenticate from another nextcloud instance using the same parameters.
Another nextcloud can authenticate from the failing nextcloud using another nextcloud account and the same mail account settings.
2FA has been disabled, that's not the reason.
nextcloud redis cache and snappymail data/cache have been cleared.
all browser cookies and data for the sessions have been cleared, another browser has been used.
Might content security policy be a reason - but why only for this user?
The text was updated successfully, but these errors were encountered: