Fixed, thanks!
Took me a few glances to see the mistake ![]()
Fixed, thanks!
Took me a few glances to see the mistake ![]()
Are you saying that after registering in id.ai now you can’t log in to identity.internetcomputer.org?
I am currently unable to log in to https://identity.ic0.app/, https://id.ai/, or https://identity.internetcomputer.org/ using my current computer.
I also cannot recover access through other devices (it prompts that the account is already registered).
I’m not sure which event or action caused this situation, but I recall it started after using Caffeine on id.ai.
I can register a new identity, but I can’t use the old one.
Hi @ysyms
Sorry for the incoveniences,
Can you share with me on a DM a screenshot of the problem you see when you try to log in https://id.ai/ and in https://identity.internetcomputer.org/?
Thanks!
This seems related to the authentication mechanism of identity.ic0.app.
The following is the process to reproduce the issue:
https://identity.internetcomputer.org/.identity.ic0.app using identity 2854601, everything was normal.identity.ic0.app.identity.ic0.app using identity 2854613, and at the same time, the original identity 2854601 also became invalid, preventing me from logging in on any .Thanks for the replication steps!
I was able to perform all the steps and I successfully logged in all the new identities I created and never had any issue.
You performed all these steps in the same device, right?
Could you to the Windows Security Center to check for passkeys for the domains “identity.ic0.app” and “identity.internetcomputer.org” and tell me whether you see any passkeys there? It appears that your computer is unable to find the passkeys when there are multiple ones…
Could you try creating two registrations in this standard website for passkeys: https://www.webauthn.me/ and let me know how it goes?
You also mentioned that you can’t recover. Do you mean using a seed phrase?
@lmuntaner on https://id.ai, There’s a console error when doing the following:
“Upgrade from legacy identity” → “Continue” → “Upgrade Again”.
Now i can’t login to ii.1.0 on any windows web browser . Is somebody experience the same?
(the migrated one. I still can login to the fresh one i made)
okey, nevermind. some strange error. I regained access using the recovery phrase /sorry.
Not sure how to find that in Windows Security Center
When I restore, it will prompt that the device already exists.If I remove this device and add it again, it should recover normally
I am currently unable to log in with the identity registered on identity.ic0.app. It becomes invalid immediately after registration and also causes other identities to become invalid (but does not affect the passkey on https://www.webauthn.me/).
every time i login to ii 1.0 i have to use recovery phrase, it doesn’t remember my device, always the same error
“““ Authentication Failed
Something went wrong during authentication. Please try again.
Error details:
Error: Failed to authenticate using passkey: Unknown error: NotAllowedError, user-agent: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36”, is platform auth available: true “““
I’ve never had problems like this before. Permanently.
And when will there finally be basic security with a recovery phrase for ii.2.0 ?
Applications want to migrate …but obviously don’t want to take unnecessary risks.
Hi @casualchess
A few questions to help me debug the problem
Support for seed phrases is included in the roadmap and should be available soon, although I’m not sure exactly when.
Let’s continue in direct messages.
The next version of Kinic on the Chrome store is using II2! Thank you for the work
Onboarding for us will be much easier ![]()
So I just hooked up a custom domain to my caffeine site, and I notice some interesting behavior from II 2.0.
apparently if a user login by accessing the caffeine domain name it generate one principal.
if the user login from the raw canister url it generate a different principal (for the same II 2.0)
if the user login from the custom domain I attached it generates yet another principal ID.
so one user using the same authentication method generates 3 different principals for the same dApp. is this the intended behavior? theoretically if I had multiple domains that resolve to this canister would every single one generate a new principal ID?