#Passwordless
1 messages · Page 1 of 1 (latest)
not working for me as well after the latest updates
(It was working before)
2023.1.1 broke them
2023.1.0 works
https://github.com/goauthentik/authentik/issues/4527 I opened an issue here
You were saying? https://github.com/goauthentik/authentik/issues/3847
I think that's a different issue
I'm just saying that it hasn't been working for ages. :D
in my case it was working perfectly until 2023.1.1 🥲
Did you try 2023.1.2?
yep, broken on that too
There were stage changes between those versions...
If only that was handled in a test... to make sure it doesn't break
yeah tests are a must to implement in a software like this
There are, but coverage is not the greatest.
@bronze plaza Is this a different issue to mine?
in my issue it seems that it's the flow that got broken, there are no console errors (and I'm using macOS/chrome passkeys)
You mean browser console?
yep
docker logs do not complain about errors as well (as you can see in the issue)
Maybe check the flow's settings.
downgrading to 2023.1.0 makes login via passwordless work again btw
It doesn't.
My problem is somehow related to Authentik being unable to properly save the things needed to the key and thus it doesn't detect it properly on login and no, doesn't matter which platform I try on (mac, windows, linux)
I think your issue is different than mine
It may be, but similar ish in the aspect that it doesn't work. :D
oh that absolutely 😂
And by passkey do you mean what exactly?
A FIDO credential that is backed up (usually to the user’s platform account; e.g., Google Account or AppleID), allowing users to restore the credential to, and use it from, another device. From a user experience standpoint, this will be very similar to how one interacts with a password manager today to help them securely enroll and sign into web...
Ah, so the Apple built-in thing.
they are not apple exclusive anymore 😛
(login fails on chrome too, so it's not a client issue)
90% it's a server side problem
Hmm, and the annoying thing is that even troubleshooting these kinds of bugs are beyond frustrating as the API (WebhAuth API that is) will not really tell you much about why it failed.
Hmm, could the issue just be Firefox? :D
have you tried with another browser?
Yes, Safari on Mac.
also small note: 2fa with passkeys works fine, it's the passwordless login only that does not work
Also Chrome and Safari seems to be the only to ask for my Yubikey's PIN for WebAuth. :D
Oh hey, in Chrome it might work if it actually worked:
:D
try to downgrade to the 2023.1.0 version
it should work there
But downgrading is not supported by database migrations.
Well, cannot downgrade as I need the changes in 2023.1.2 :)
ops xD
The fix itself is pretty simple, but it's one of those cases that didn't have full test coverage, so it wasn't obvious when the bug was introduced https://github.com/goauthentik/authentik/commit/68058fb2ae22c04c590fea7c5c5f705f5bb6fc14
Thank you for the so much fast fix!!
there's no major new things in the beta currently so it's safe to upgrade to the beta
You were saying?
will be fixed on the next beta build
It seems I had quite a few dupplicate prompts.