Im having a few issues with the new Id.ai Internet Identity
I have a new identity (not old with number) that only exists for my phone right now and am trying to get it usable on my desktop as well
First, doing Identity Dropdown → Use another Identity → Continue with passkey → Use existing identity, just hangs with no errors in the console, just spins forever
Second, when doing Identity Dropdown → Use another Identity → Revcover → type in recovery key, i DO get my identity from my phone on my desktop BUT whenever i then goto the login page again its not an option in the dropdown and when i goto the manage identity again it is gone?
Third, when i do recover like mentioned above, i am unable to add a new ‘access method’ using a passkey from this device, it just spins like when trying to use an existing identity like above
Note for all of these i have tried in Brave and in Chrome
Also I have no problem with using my pre-existing identity (upgraded from a number) on my phone and on my desktop. I was able to transfer it to my phone with no issues
I was able to disable my ‘Dashlane’ browser extension then i started to use Windows Hello passkeys and it worked
Dashlane has always worked before, can that be fixed?
Unfortunately, Dashlane doesn’t support the newer discoverable passkey standard that id.ai relies upon.
You can try to contact Dashlane support to ask for them to add support, but it’s probably not likely to be supported soon.
Personally, I’d recommend switching to a password manager with better support like 1Password or Bitwarden, the latter is open source and can also be self hosted.
Well is it possible to at least skip/bypass ones that don’t support it. Having no indication that it’s failing on dashlane and having to disable the extension seems like a big vs lack of support
Unfortunately the browser passkey API is limited in this regard, there’s no way to identify a passkey provider and what they support.
Passkey providers can only be identified by attestation data when a passkey has been created/requested, but when you reach that point, things are already working
Proper 3rd party passkey support on desktop is non existent, contrary to mobile (iOS/Android), there’s no system and/or browser API on desktop systems yet.
As a result all desktop passkey providers rely on browser extensions and monkey patching the navigator.credentials.get() and navigator.credentials.create() methods to make them invoke their browser extensions instead of the system API.