GitHub Community
Replies: 34 comments 100 replies
-
|
Excited to see this. Tried to enable it on my current account (that currently uses authenticator app). Turned on in browser (Safari Version 17.0 (19616.1.27.111.16) on M1 Mac Studio running 14.0 (23A339)). Turned on passkey as an authenticator (this might have been a mistake but it wasn't too clear whether to use this or not). Logged out. Got an error dialog trying to log back in "Unable to sign in with your passkey. Please sign in with your password." Logged back in the normal way with credentials stored in Safari (which is tricky because Safari is convinced I should be using the passkey) Turned OFF passkey as an authenticator. Logged out. Tried again. Same error. Logged in via password instead… Tried on iPhone and WAS able to log in with Mobile Safari and Passkey. Issue seems limited to Mac Safari for me. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @schwa - we got some confirmation from Safari folks that this is likely a compat issue between STP and your MacOS version, that shouldn't reproduce in the release version. |
Beta Was this translation helpful? Give feedback.
-
|
"STP"? I'm on the release version of macOS (23A344) though. Can you be a bit more specific? |
Beta Was this translation helpful? Give feedback.
-
|
🚀 WAYYY |
Beta Was this translation helpful? Give feedback.
-
|
Ty |
Beta Was this translation helpful? Give feedback.
-
|
I am quite disappointed. I am experiencing problems as many state in this thread. It is now 7 months later and nothing has changed. What needs to happen to get GitHub to fix this? If they don't intend to support PassKeys, they should remove the illusion that they do. I am running a new Mac with all updated software. I would like to see this work, but I can't see anything that I can do to help this along. Does anyone have any suggestions? |
Beta Was this translation helpful? Give feedback.
-
|
Love this! Is there a way we can remove password from the account and go completely passwordless? |
Beta Was this translation helpful? Give feedback.
-
|
@Firstyear I'd love to grab some more detail on why non-rk is considered the definition of passwordless. If you'll be at one of the upcoming summits such as the passwordless summit or Authenticate would be great to go in depth. |
Beta Was this translation helpful? Give feedback.
-
|
Hey there, I'm Australian so I wont be attending either (I am not comfortable to enter the US due to a preexisting medical issue). I'd be happy to talk more via email though if you want - it's on my profile :) |
Beta Was this translation helpful? Give feedback.
-
|
I, too, would like to be able to disable password authentication. I'm not sure what benefit passkeys provide if someone can still authenticate using less-secure methods. |
Beta Was this translation helpful? Give feedback.
-
|
I agree with @Firstyear.
According to https://www.w3.org/TR/webauthn-2/#sctn-authenticator-taxonomy:
And 'user verification' is:
So I think for example, if you type in your username and then use a 'user-verifying platform authenticator', e.g. fingerprint sensor on your laptop/phone + a security chip, with or without a resident key aka. client-side discoverable credential, it's already considered MFA. Same goes for things like YubiKey Bio and PIN + touch:
I'm not quite sure why in the table 'first-factor roaming authenticator' is defined as having 'client-side credential storage' though. I think whether the authenticator is user verification-capable is more important.
I think @Firstyear meant non-rk is considered one of the forms of passwordless. |
Beta Was this translation helpful? Give feedback.
-
|
The problem here also is that there are a whole bunch of different terms in webauthn that have confusing or overlapping meanings. Passkeys for example, have 4 different definitions, all in use by various production IAM providers, with different behaviours. Passwordless in webauthn actually specifically means non-resident keys as a self contained MFA. RK can exist, but it's opportunistic. It's because in webauth passwordless was the goal for a long time (mainly when security keys were the most common authenticator class), but then passkey hype took over and now everyone wants to force rk's everywhere so the definition fell by the wayside. Passkeys in the "common" definition forces rk's which pretty much excludes security keys.
It's because "one definition" of passkeys enforces credential storage in the device (resident keys) which allows the user-id to be stored in the credential. so you don't need a username entry, you just "pick the passkey" and it identifies and authenticates you. It also ties in with certain vendors attempts to lock you in to their synced passkey systems and browser features around username autocomplete (see conditional ui). However, the flip side is that most of these workflows are actually pretty janky and confuse users. "Yes please I'd love to pick up my phone, scan a qr code and wait 30 seconds for it to authenticate me" (btw this workflow is an accessibility nightmare ... ). It also completely alienates and breaks security keys since they have so little rk storage, and now the browsers are pushing their sync ui's in front of security keys to make it extra clicks adding "forced friction". I already know of people who can't use passkeys because a certain cloud provider forces rk and it bricked their keys. Generally the people pushing passkeys as resident keys are making assumptions that you are "all in on chrome+android" or "all in on safari and iphone" or "all in on edge and windows". But none of them account for the reality that people use android + mac with firefox, or other combinations, which means that none of these passkey sync mechanisms will interoperate. For example, my partner (a surgeon) has an iphone, a windows machine, and uses chrome. None of these can sync keys with each other, and so there is no passkey provider that would work except security keys - and we can't use those because rk obsession means we'll fill the devices up in no time. Can you imagine her needing to juggle 4 yubikeys to find which one she needs? She has ~80 accounts in her pw manager, and this is a nightmare. Once passkey hype kicks in, this will be the future for her. Anyway, so passwordless is what we should be pursuing where the keys are opportunistically rk (iphone always makes rk even under discouraged for example). This way you still prompt with a username field. You can use conditional ui to opportunistically allow rk's to complete the username + authentication in one go. And then for users without those rk's such as yubikeys, you allow the username prompt to complete and then do the webauthn challenge with the credential id list set as normal for that user. |
Beta Was this translation helpful? Give feedback.
-
|
Tried to add a Yubikey 5c on Safari and Firefox on macOS, and on Firefox on Linux. Getting 422 with this error: |
Beta Was this translation helpful? Give feedback.
-
|
(Which incidentally why I have been repeatedly warning about rk's being required/preferred rather than discouraged since it can lead to devices filling their extremely limited storage, rather than rk being opportunistic to allow flows ontop of passwordless. ) |
Beta Was this translation helpful? Give feedback.
-
Related to that storage space issue I mentioned, if you've hit max storage on your yubikey then it won't let you create the type of webauthn credential that we'd accept as a passkey. You could check if that's the issue using the yubikey CLI depending on your hardware key version. Edit: what @Firstyear said. |
Beta Was this translation helpful? Give feedback.
-
|
Oh another gotcha. Only CTAP 2.1PRE and 2.1 support credential management. If your key is older (like mine) and is CTAP2.0 only, you CAN NOT list rk's, and you can never delete them. Meaning you're "stuck". You'll see this if ykman errors with |
Beta Was this translation helpful? Give feedback.
-
|
I have same problem, but when I set a PIN for FIDO2. |
Beta Was this translation helpful? Give feedback.
-
|
@xz-dev cos the PIN counts as a 'factor': https://www.w3.org/TR/webauthn-2/#authentication-factor-capability |
Beta Was this translation helpful? Give feedback.
-
|
It seems I cannot setup Windows Hello as a passkey as Windows only allows me to provision a USB key:
though Security Key via Windows Hello works fine. Windows 11 Pro 22H2 (22621.2283) |
Beta Was this translation helpful? Give feedback.
-
|
You need a tpm on machine and a PIN enabled for win hello to work without the security key. |
Beta Was this translation helpful? Give feedback.
-
|
I'm pretty sure I have a TPM and a PIN and the passkey features works elsewhere, for example, Google. |
Beta Was this translation helpful? Give feedback.
-
|
Two possible problems:
|
Beta Was this translation helpful? Give feedback.
-
|
Can confirm that removing the existing security key first works :) |
Beta Was this translation helpful? Give feedback.
-
|
I'm not able to set up a passkey on an Android device. After going through the setup on GitHub, following the push notification steps, and entering my phone PIN, I see "Passkey registration failed." Android 11 I was able to set one up with MacOS + Chrome and Windows 11 + Chrome without issue. I tried setting it up on my device from the Windows computer, but that also resulted in a failed registration. I saw this error in the browser console at that time: |
Beta Was this translation helpful? Give feedback.
-
|
Pixel 7 Pro with Android 13. I am also hitting this error. |
Beta Was this translation helpful? Give feedback.
-
|
I also wasn't able to use passkeys on my Pixel 6 Pro and my new phone with my main Google Account. But it was working with another account, I just setup. What fixed the issue for me now, was to manually disable the Screen Lock setting for my main account (had this manually enabled before) and then starting the passkey registration on e.g GitHub. In the process of creating the passkey, I was the asked to enable screen lock again and the registration went through successfully. Tested the registration with latest Chrome on Android 14. Hope it will fix the issue for others as well. This is the setting to disable first: |
Beta Was this translation helpful? Give feedback.
-
|
This worked. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I tried all of the steps proposed by @amoosbr, but I still get the I'm on Android 10 with a Samsung S9 OneUI (old, I know). |
Beta Was this translation helpful? Give feedback.
-
|
Likewise. Android device stopped working for roaming passkey registration and cannot see why. Tested everything i can think of. |
Beta Was this translation helpful? Give feedback.
-
|
Please help by explaining two things - I have read all the docs and posts but I cannot find an answer. I use a linux (ubuntu 22.04) laptop and edge browser.
Thirdly can someone answer if I don't set up 2FA or a passkey will I still be able to report bugs and contribute to discussions on github projects with a simple password. It is proving so difficult to understand all the unexplained stuff in your 2FA docs that I am thinking that it'll be easier simply to stop using github for my own code. |
Beta Was this translation helpful? Give feedback.
-
If you've been asked to enable 2FA by GitHub, and not by an organization that you belong to, then you won't be able to contribute on GitHub after the deadline if you haven't enabled 2FA. Passkey registration is separate from our 2FA rollout, so you can completely ignore it if you want. You just need to enable 2FA from your user settings. Passkeys are more like an additional benefit on top of 2FA to make your life easier. There are benefits to using passkeys without 2FA too but we're not asking or forcing anyone to do that. If you're still interested in passkeys: The QR code: you would have to scan it with your phone's camera. If your phone has passkey and bluetooth support then you could register a passkey for login. It's similar to the SMS flow that you described except using bluetooth - the benefit is better account security for folks that want it, and additional convenience for 2FA users or folks that don't like managing their passwords. |
Beta Was this translation helpful? Give feedback.
-
|
@hagould You should likely feed this back to the chrome team since the UI referenced by @rogercreagh is part of the browser, and this kind of usability issue will likely come up more often. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks you @hagould that was clear and most helpful (if not quite what I hoped to hear) |
Beta Was this translation helpful? Give feedback.
-
|
Excellent news! May I suggest adding the ability to enable 2FA for specific passkeys? |
Beta Was this translation helpful? Give feedback.
-
|
Indeed. Still, even though it is not the same as keeping passwords and TOTP keys in the same password manager, it is a single vendor. As a side note, it is quite cumbersome to use YubiKey with resident keys for git access on Windows. Because it requires 5+ confirmations for "git push". Because SSH on Windows does not support the ControlMaster option. |
Beta Was this translation helpful? Give feedback.
-
|
Huh, TIL, and I was on the team that added openSSH to Windows... Looking over some older issues from e.g. Would a non-rk registration be easier to use? That's a bit surprising to me, but certainly it's something we want to make a good experience. |
Beta Was this translation helpful? Give feedback.
-
Yes, non-residential keys can be stored in the SSH agent, removing the need to enter a password each time at the cost of less protection compared to residential keys. Non-rk keys should protect against most attacks targeting credentials. And if there was an attack that was able to dump memory from the SSH agent and extract keys, then it could do much more damage than just steal credentials. It seems I should reconsider my usage of rk and switch to non-rk instead. (My paranoid mind does not make my life easier...) |
Beta Was this translation helpful? Give feedback.
-
Isn't it a bit misleading (or a lot misleading) to call it a 'second factor', if it's a single passkey and therefore a single factor? |
Beta Was this translation helpful? Give feedback.
-
|
https://pages.nist.gov/800-63-3/sp800-63b.html#sec5 section 5.1.9 defines multi-factor cryptographic devices. |
Beta Was this translation helpful? Give feedback.
-
|
My small list of suggestions. It would be handy to have the ability to test the passkey directly in your account settings. Ability to add a passkey with a lifespan. Backup passkey(s). A passkey that is not intended for frequent usage and must be opened first, with a specific time period set in the initialization stage and, optionally, a list of users who must be informed. Periodically ask the user to check if he still has access to the passkey and if it is in a working condition by completing the test. If it is not already done. I never used keys for 2FA on GitHub. (pass+TOTP). And saw only messages about 2FA and backup codes. |
Beta Was this translation helpful? Give feedback.
-
You can actually do this today if you go to add a new passkey but auth with one of your existing ones. The other suggestions are interesting, thank you for the feedback! |
Beta Was this translation helpful? Give feedback.
-
This is something we're looking at adding to the existing checkup period! Right now there's a "security checkup" that's pretty useless - "you have security keys" is not a direct call to action. We would like to periodically check second factor freshness and warn on severely out of date factors that look like they're unused. Interestingly we do expire unused GitHub Mobile keys for authentication, which can lead to more lockouts since it kills a possible recovery factor. |
Beta Was this translation helpful? Give feedback.
-
|
Will it be possible to disable TOTP in the future? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I also have similar problems |
Beta Was this translation helpful? Give feedback.
-
|
My comment is not a problem report, just a question^^ |
Beta Was this translation helpful? Give feedback.
-
|
The next step will be to allow users to essentially disable/delete their passwords, but we haven't gotten there yet. Today you still need 2FA to keep your account secure with passkeys. |
Beta Was this translation helpful? Give feedback.
-
|
@hpsin is it still not possible to disable TOTP while having backup codes? |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
I got a popup from Github today demanding an SMS authentication. I have 2FA set up with a Yubikey, a backup Yubikey, and a list of TOTP passwords. But there was no option to use the Yubikey. It insisted on SMS. My first reaction was to think this was some kind of phishing message. If you've set up 2FA with a Yubikey, you should never be forced to use SMS. |
Beta Was this translation helpful? Give feedback.
-
|
We want to get there, but today we only accept an authenticator app or SMS number for your "primary factor" for 2FA. To reduce lockouts we've starting asking folks to authenticate with that factor (for you, SMS) a month after enrolling to make sure that it was successfully configured and to reduce account lockouts. If you'd gone with an authenticator app you would've had to prove you still had access to it in the same way. We're are working towards allowing folks to enroll with just a webauthn credential, we'll likely have some requirements that we're still working out. |
Beta Was this translation helpful? Give feedback.
-
|
I was able to setup and login while the beta was active but it seems there has been a recent change in the way webauthn is requesting the device on android chrome. If I tap sign in with a passkey I just get a window saying "there aren't any passkeys for github.com on this device", where as other sites are prompting for the type of passkey to use, NFC or USB. Works fine on all other platforms but now I have to use a computer to complain about free software. |
Beta Was this translation helpful? Give feedback.
-
|
We haven't changed anything about the request, so that's not a good sign. If you open Chrome, and navigate to the password manager, and locate GitHub.com in the list, there should be a passkey listed at the bottom of that entry. Do you see that?
|
Beta Was this translation helpful? Give feedback.
-
|
Today, not only did Github ask for SMS authentication again, and, as before, would not accept my Yubikey, it offered to redisplay my TOTP keys! Those are last-ditch credentials that were supposed to be sent once only! I printed them and put the printout in a safe deposit box. Now you're exposing them to anybody who can divert or steal my cell phone. This is really sloppy. Need to get Schneier on Security to review Github's 2FA system. |
Beta Was this translation helpful? Give feedback.
-
|
As written above, this is a verification step to ensure you've saved them properly. If you can't pass, we register new credentials. Yes, this does result in an opportunity where someone who has stolen your session (or your password and SMS) can re-register your 2FA credentials. That's also true of anyone who has stolen your password and SMS in general. You are not required to register SMS, and if you do not want to use it, please do not register it. |
Beta Was this translation helpful? Give feedback.
-
|
I had an issue when registering 1password as a passkey on Ubuntu 22.04 with Firefox 119.0 (64-bit). |
Beta Was this translation helpful? Give feedback.
-
|
Oh, interesting, thank you! When we show the upgrade prompt we flag the presumed upgrading key for deletion on the next registration. We have to clear that when the upgrade is rejected. Cc @hagould |
Beta Was this translation helpful? Give feedback.
-
|
@Logiar This has been fixed for a bit! Let us know if you're having any other issues. |
Beta Was this translation helpful? Give feedback.
-
|
2FA Organization Enforcement, doesn't recognize passkey as a viable solution for 2FA when answering an invite to join an organization where 2FA is enforced. |
Beta Was this translation helpful? Give feedback.
-
|
That's because you don't have 2fa enabled. Setting up a passkey does not enable 2fa on your account - we don't want to surprise people by changing their account security and recovery state without very explicit opt in. |
Beta Was this translation helpful? Give feedback.
-
|
i sent feedback by google |
Beta Was this translation helpful? Give feedback.
-
|
Trying to use a Solokeys V2 USB-A on Windows 11, I'm getting a "Something went wrong error". |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
This also has been happening on ChromeOS. |
Beta Was this translation helpful? Give feedback.
-
|
I just enabled passkeys on github and it worked fawlessly for about 3 days. Then for no explicable reason (all I see is "Authentication failed" in a red box), I can no longer sign in with my passkey, so I now have to revert back to my dreaded password and 2fa code. I am using an iphone running iOS 17.2, firefox 120.0.1, macOS Big Sur (11.7.10). I also use a password manager which somehow is still in the loop when trying to use a passkey. The password maanager is aware that im using a passkey and shows me an identity to click on (ie my user account), to confirm the passkey. Again, this all worked fine for 3 days, then stopped. |
Beta Was this translation helpful? Give feedback.
-
|
Do you happen to have a security key enabled as well, from the same device? We've seen some issues with iOS not fully removing the security key registration when upgrading to a passkey, meaning it offers both, but only one works. |
Beta Was this translation helpful? Give feedback.
-
|
No I do not have any other security device. I guess the problem is because I'm using Firefox on a now retired macOS Monterey. Firefox does show a vague message indicating that there is only partial support for pssskeys, but isn't specific enough so that I can troubleshoot it. Can you confirm wether GitHub passkeys should work on older mac os's or not, thanks |
Beta Was this translation helpful? Give feedback.
-
|
Will be passkeys feature ever be available on Github enterprise server? if yes what timeframe? |
Beta Was this translation helpful? Give feedback.
-
|
Yes! We're ironing out some details there since the user accounts can have different credentials there, but we're looking at 3.13, 3.14 at the latest. It'll only work, of course, for users that aren't federated (i.e. LDAP/SAML won't have access to passkeys) |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
I verified that no security key has been created. That is, when I click
through to that setting, none exists.
…On Mon, Jan 8, 2024, 13:12 Hirsch Singhal ***@***.***> wrote:
Do you happen to have a security key enabled as well, from the same
device? We've seen some issues with iOS not fully removing the security key
registration when upgrading to a passkey, meaning it offers both, but only
one works.
—
Reply to this email directly, view it on GitHub
<#67791 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2BCDFGNFKPDSVVBSOI5DTYNQZJZAVCNFSM6AAAAAA5A7NFNSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANJTGYZTI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
While clicking through on my phone to check the settings for an existing passkey, it occurred to me that I could try the process using Chrome on my phone. So, I logged out of GitHub in Chrome on my phone, and tried to log back in using a passkey. This works (I get to use my fingerprint and don't need to type any passwords or do 2FA). However, when I try (as above) to log in to Github using Chrome in Windows and specify the passkey on my phone, I'm taken through all the steps on my Phone, even up to the fingerprint scan. Before I have a chance to scan my fingerprint, the Chrome browser on Windows already displays the error (as above). That is, it's failing before I can get the scan. I have rebooted my Windows PC several times. This is not by any means a complaint (I have the GitHub app and the Authenticator App that work well with 2FA in GitHub). I have been using Google 2FA since 2012 according to the Google's security page (it sounds right), if somehow that could make a difference. |
Beta Was this translation helpful? Give feedback.
-
|
This is attempting a caBLE flow, and there are a lot of things that can go wrong - specifically you need bluetooth enabled and working (you don't need to pair however), and a working internet connection on all involved devices. Saying this, caBLE is quite fragile/slow, so you may also need to check the console/inspector in your pc browser for errors. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Is it possible to add modern Chromebooks with PIN as a passkey? My |
Beta Was this translation helpful? Give feedback.
-
|
Hi Liz, |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Very happy to provide any additional debugging data that you need. |
Beta Was this translation helpful? Give feedback.
-
|
When they say "standard parameters" they mean "forcing resident keys" which a lot of older security devices don't work with. |
Beta Was this translation helpful? Give feedback.
-
|
I set up a GitHub passkey on my Pixel 8 (Android 14) when I first got it, and it worked for a while 👍 I used Chrome desktop on macOS Sonoma to set this up But then after a few weeks, the problems started 😬 (may have been after an Android OS software update, Chrome software update, macOS software update, or a combination of multiple of these) Problem 1: I cannot create a GitHub passkey on my Pixel 8 from macOS ChromeIt is able to add the device and prompts me on which Google account to save the passkey, which seems to succeed But then GitHub returns the following message in the macOS Chrome window: 
Problem 2: I cannot log in with a GitHub passkey created on the Pixel 8 directlyIf I create a GitHub passkey using the mobile Chrome on the Pixel 8, it seems to create the passkey, and GitHub sends me an email that the passkey was successfully created Interestingly, this passkey is nowhere to be found in the Pixel 8 Chrome mobile password manager (Settings -> Password Manager). GitHub does not have an entry for the passkey as in the message by @hpsin. And then any attempts to use the GitHub passkey (eg. to sign in) will fail - the mobile Chrome will show only "NFC security key" and "USB security key" as options: 
Attempts At Resolving the ProblemThings I have tried include (many cycles of the following):
Versions
|
Beta Was this translation helpful? Give feedback.
-
|
Given how prevalent this issue is, and how long it's gone on for, I think there is very little hope sorry. |
Beta Was this translation helpful? Give feedback.
-
|
Please also add to the list that passkeys dont work at all on some Android vendors like Oppo, Oneplus and LG when the device is acting as a roamin authenticator. Crashes on lockscreen. Not sure who to channel this info to either. |
Beta Was this translation helpful? Give feedback.
-
|
@FrankSzendzielarz probably better to add your own separate discussion "Answer" so that can be discussed separately |
Beta Was this translation helpful? Give feedback.
-
|
@Firstyear don't lose hope :) We need to keep trying. I'm hoping that:
|
Beta Was this translation helpful? Give feedback.
-
|
I've been working in the webauthn space for multiple years, and I would assert my lack of faith in future behaviour from these orgs, is based on having witnessed their past behaviour. I would say that your best bet is to use something like bitwarden. |
Beta Was this translation helpful? Give feedback.
-
|
I'm sorry, but biometric authentication methods aren't more secure than regular password-based and 2FA-based authentication. In fact, they're worse.
See also this video: Biometric "Security" Is NOT Secure One interesting quote of the video is the following: “It is plain stupid to use something that you can´t change and that you leave everywhere every day as a security token", said Frank Rieger, spokesperson of the CCC. |
Beta Was this translation helpful? Give feedback.
-
|
Cool then don't use them. Everyone has different risk models and profiles, don't assume my risk is yours. |
Beta Was this translation helpful? Give feedback.
-
|
Passkeys have nothing to do with biometric authentication. They work completely independent of it. There are hardware security dongles (Yubikey etc) that support passkeys that have absolutely no biometrics authentication at all. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for mansplaining this to me. Really appreciate it. 👍. |
Beta Was this translation helpful? Give feedback.
-
|
@Firstyear do try to keep up next time |
Beta Was this translation helpful? Give feedback.
-
|
I’m suddenly experiencing passkey failures from macOS and iOS after months of smooth running? I was forced to use username and password and 2fa via Auth app. any clues? How should I try fix this?
|
Beta Was this translation helpful? Give feedback.
-
|
لقد قمت أيضًا بتعطيل أدوات حظر المحتوى والإضافات لمعرفة ما إذا كان ذلك سيحدث فرقًا. ندى. |
Beta Was this translation helpful? Give feedback.
and others
-
We've taken passkeys from a public beta to general availability, with all users able to set up and use a passkey.
This discussion is to track known ecosystem issues and get your feedback about passkeys. Previous feedback from the beta can be found here.
Known issues
Passkey registration failed. This cannot be used as a passkey. This is because Firefox doesn't support setting up the PIN for a hardware key. If you encounter this issue, you have to set up the PIN yourself, using an app like Yubico Authenticator to manage the key directly, before trying again.Filing a report
If you've encountered a bug or undesirable behavior with how GitHub interacts with your device's passkey support , it's really helpful to know your operating system and browser version, I.e. Mac OS Ventura 13.5.2, Google Chrome 117.0.5938.62.
You can learn more about passkeys at these useful links:
Beta Was this translation helpful? Give feedback.
All reactions