yes, so solution as https://internetcomputer.org/docs/references/ii-spec#alternative-frontend-origins,
not sure how caffeine handle it
1 Like
I apologise if the questions have already been asked but:
- Is there currently a way to test Internet Identity V2 locally? I’m supposedely pulling the latest release from my
dfx.jsonbut it still appears as V1 locally. - How to use recuperation phrase? I’ve migrated an Identity to V2 and wanted to verify if the recuperation phrase still works, but I don’t find any option to try it.
2 Likes
Hi @Seb
Answering your questions:
- We are working on supporting 2.0 out of the box for local development.
- The workaround for now is not straightforward, you need to change one
init_argcallednew_flow_originsand set it to a vector with the URL of your local Internet Identity as element within it.
- The workaround for now is not straightforward, you need to change one
- 2.0 doesn’t support seed phrases yet. This is also in our roadmap.
I hope that helps!
4 Likes
I even get this error when logging in to other dapps. Just try again in a few minutes and it should work.
Thanks!I am thinking, can we reduce the probability of authorization failure and improve the speed of authorization? Otherwise, will we be at a disadvantage in future product competition?
Yes. I’ve had the same problem for the past couple of weeks now.
1 Like
For the people that are using the original 1.0 version, do they need to upgrade to the 2.0 version, or can they just keep the original Internet Identity 1.0 version without having to worry?
Thank you
Which version is used depends in the application, not the user for now.
If the application sends the users to the old domains identity.internetcomputer.org or identity.ic0.app, then the 1.0 is used. If the application uses the new domain id.ai, then 2.0 is used.
If you have an identity in 1.0 that uses an application with id.ai, you can upgrade by following the Upgrade flow.
Was this helpful?
1 Like
@lmuntaner Thanks for the reply. Im not sure sorry…
For people that use the original 1.0 Internet Identity with the anchor numbers on the NNS, do they need to upgrade to the new version 2.0 in the future or can they keep using their original 1.0 Internet Identity without having to worry that it will become unusable in the future?
Thanks again.
The current plan is to move all the Internet Identity domains (identity.ic0.app and identity.internetcomputer.org) to the new 2.0 flow eventually. So, yes, at some points, users will need to upgrade their internet identity.
1 Like
Ok. I like it how it is with the original 1.0 Internet Identity login on the NNS and would like to keep it like it is. Upgrading something like this sounds kind of scary. What if something goes wrong and the funds are just gone? I hope we can have a choice to uprgade or to keep it like it is.
4 Likes
@lmuntaner If users are not very active and not following the forum or other updates, if they return in say a year or two to retrieve their funds from OpenChat or other apps, will they have a problem?
3 Likes
They won’t have any problem; they simply won’t be able to log into any apps. All they’ll have to do then is upgrade their identity to 2.0 and they’ll be able to log in.
1 Like
If they try to log in will upgrade instructions be displayed?
One question about DAPPs made for Internet Identity v1.0, would they work normally with version 2.0, or the code needs to be changed?
Meaning has the API remained the same, is it compatible from a developer perspective?
If the answer is no, where can we find the best documentation to do the upgrade to the code, and when will version 1 support stop working for DAPPs?
Thanks.
I do prefer the original myself, and would prefer that 1.0 continues to work.
2 Likes
same I can no longer access any of my ii’s from my computer without using my phone to take a picture of the QR code.
Can someone tell me if there is a way I can type in my 4 digit code like before with my registered devices.
The option to keep the old ii needs to be available.
1 Like
Hi! I have 2 II 2.0 and 2 II 1.0. The problem I see here, is that nns app and oisy still ask for a number, that is, an II 1.0… So Why I would “upgrade” to II 2.0 if apparently it not supported by nns app neither oisy? I’m waiting for nns and oisy to implement II 2.0 since its release.