Does it work if you register a user in https://www.webauthn.me/ ? (Below the “Learn More” button
When you click on the upgrade from legacy button… it gives you this screen:
Those numbers are from ii 1.0.
i would like to use a NEW IIv2 and login into the nns. but thats not possible, cuz the NNS app only allows numbers to login.. ?! i dont get it… 
My new II is only connected to my google account… so there never was a number…
Each application decides which Internet Identity to use. It’s not up to the users yet to decide that.
Therefore, for now, if NNS sends users to the old domains with II 1.0, then you need an identity created in 1.0 to access NNS. You can’t use (yet) the new identity created in 2.0 there.
We are working on fixing that. But as of today, this is the current state.
1 Like
I would upgrade a dummy II v1 as a test. If I do that will I be able to remove it from the login options?
You’ll have to clear the browser data for the id.ai site since we don’t have functionality in the UI yet. Alternatively, you could use a private browsing window so it’s cleared the moment you close it.
Keep in mind that the passkey would still show up when you pick “Use an existing passkey” unless you delete the passkey from your credential manager.
1 Like
Thank you. What is a credential manager?
If it doesn’t work there, it means that there is something with your combination of device and browser with passkeys.
Could you try with another browser and maybe another device?
It’s the application that stored your passkey, most commonly its one of the following:
- iCloud KeyChain / Apple Passwords
- Windows Hello
- Google Passwords
- Samsung Passwords
Clarifying what passkeys are and where they’re stored is one of the many planned future improvements for II 2.0.
1 Like
We have a new product that we want to use ID.AI from the beginning. So when will this feature be production ready?
1 Like
It is production-ready today. It’s just not in feature parity with II 1.0 yet.
Now that we have the upgrade flow there is nothing stopping applications from using id.ai. You just need to understand that you will require existing users who haven’t done the upgrade to perform the upgrade. But that’s a one-time thing. Next time, they will have a seamless experience.
2 Likes
I successfully upgraded it using the computer browser. Thank you for your help.
1 Like
Awesome! BTW do you know when NNS will start supporting II 2.0?
No, I don’t know. I’ll ask but they might want to wait a bit until more people have done the upgrade to not have to force them to do so.
2 Likes
Can I label my new ii 2.0 by the numbers from old ii1.0? For example, 2734412 - and it won’t cause any collisions/issues in browsers etc.?
1 Like
Yes, you can. The name for the identity in 2.0 is just for you. They don’t need to be unique, nor will be used to authenticate. It’s a name for you to better identify and remember the identity.
Let’s say I upgraded my old II 1.0 on a single device, and I lost access to that device, and I didn’t create any other passkey on another device. Then I CAN’T log in to my new identity on ANY device ANYMORE — because when I try, I always get a message that the II is upgraded—but users are left without any way to log into the new II 2.0! (in case if we lose access to the device we initialy upgraded to 2.0, suppose the phone will be somehow crashed just a second after upgrade). You know what i mean??
1 Like