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
login error with NC 21.0.2 #58
Comments
Works on my installation. I can't provide any support if you skip any useful information and ignore the bug template i set up. Feel free to reopen after supplying some more information about the issue. |
I can confirm the exact same issue on my side. After the upgrade to version 21.0.2 (docker) the 2FA login with this extension fails. I have to fall back to TOTP to be able to login. |
@mike2307 Any help is greatly appreciated. If you could provide the information asked the by bug_report template, it could help to find the issue. Thank you! |
Describe the bug To Reproduce
Expected behavior Screenshots Environment (feel free to add relevant information)
Webauthn Devices
Nextcloud error log Browser error log Additional context |
To Reproduce Environment (feel free to add relevant information)
Webauthn Devices
Nextcloud error log Browser error log Additional context |
Perhaps this might help, too:
|
Thank you all. I hope i find some time tomorrow to look into the issue, the provided information is a great starting point. |
Hi, chiming in also to confirm this bug on v 21.0.2
|
I got a similar issue on my docker installation and on a fresh test setup as I describe here nextcloud/server#27079 But i think the problem is in nextcloud, because the build-in FIDO2 Support doesn’t work to |
I see it the same way. I can also confirm this, as I also use the built-in FIDO2 support. I have also tested this with Firefox/Chromium and Chrome. |
I can confirm that the issue now also occurs on my freshly setup test environment. I also get the 303. @aryasenna I'm not sure if you have the same issue, but i will look into it. |
@michib thanks for checking. Also In my Javascript console, I get 500 error, not 303. |
This is especially frustrating as I cannot disable MFA for a user easily. If a user uses MFA and I disable MFA enforcement, they still cannot use MFA to login. |
This bug should be fixed with release 0.2.10. @aryasenna It was the same issue, i just didn't see the same logs in my test setup. But it was the reason for the bug and hopefully its fixed right now. @d4g I'm not quite sure how your comment adds valuable information for helping to solve the issue. I have the impression its target is to build up pressure? But because that wouldn't be nice, hopefully i just got a wrong impression ;-) |
Confirmed to be working! :) |
Just tested successfully using latest docker NC 21.0.2 (version from 04.06.2021) and Two-Factor Webauthn 0.2.10 |
This is about the build-in FIDO2 support. Not the app |
I'm sorry for mixing the issues, but looks both are fixed with 0.2.10 (or NC update). |
@osm-frasch No it is not. This issue is exactly about the twofactor-webauthn app. Please check the github repository name. 😅 The built-in passwordless webauthn is still broken. See: |
aaah i see ...this no longer functioning FIDO2 makes me all confused ;-) |
Since upgrading to NC 21.0.2 logging in with webauthn fails.
The text was updated successfully, but these errors were encountered: