Dear all,
I was very surprised this morning when it tryed to log in Juno with my internet identity.
First option does not work ( Internet Computer Loading )
Second option work ( Internet Computer Loading )
WTF ? Can anyone explain ?
Cheers
Dear all,
I was very surprised this morning when it tryed to log in Juno with my internet identity.
First option does not work ( Internet Computer Loading )
Second option work ( Internet Computer Loading )
WTF ? Can anyone explain ?
Cheers
Hi,
Internet Identity is accessible on two domains (identity.internetcomputer.org and identity.ic0.app) due to an incident that occurred earlier this year (please refer to Important Community Update on ic0.app domain being flagged by an anti-spam blocklist).
The incident has been resolved, and canister domains have been migrated as mentioned in the follow-up communication (New canisters will only be accessible through the icp0.io domain. Existing canisters will be accessible both through ic0.app and icp0.io).
However, the domain for the Internet Identity was not migrated, remaining ic0.app until today.
Shortly after the incident, I made Juno public. Since it was unclear which domain would be the official one and since this information was not clearly communicated, I discussed it with the Juno community and we decided to use internetcomputer.org, considering it to be more future-proof.
When registering an anchor on the Internet Identity, it can work with both domains, but it requires some configuration. Thatâs why your anchor may work with one method but fail with the other.
The recovery phrase can be used to set up both domains for one anchor, but there may not be much documentation available on this topic.
I hope this answers your question. Let me know if you have any further questions!
Thank you for giving Juno a try
Many thanks,
I thought internet identity will be shared between domain name ( I am surprised its not )
Cheers,
It is share between domains but, not between the domains used by II itself.
For example:
If you go anchor 11111 registered with ic0.app you can log anywhere - on any dapps - where identity.ic0.app is used a login method (as said above, I understand it is still the default).
However, if a site, like Juno, uses identity.internetcomputer.org, it wonât work out the box. You would have to also configure your anchor 11111 to support identity.internetcomputer.org. Once done, once it supports both, you can log on such sites too.
It works also the other way around if you first register internetcomputer.org and then ic0.app.
You would have to also configure your anchor 11111 to support identity.internetcomputer.org . Once done, once it supports both, you can log on such sites too.
How can I configure my anchor to support http://identity.internetcomputer.org/?
Long story short, there is no official documentation (was removed my understanding), nor clear statement, about this particular subject from the foundation.
That said, I think that basically you configure your anchor to support internetcomputer.org
as following:
Sign-in https://identity.ic0.app
Select âAdd a new Passkeyâ
Copy the URL but, when you paste it in another tab, before hitting enter to confirm it, change the domain within the URL from ic0.app
to internetcomputer.org
. That way it will create the new Passkey for the other domain.
Confirm and continue as you would do if you would add any new Passkey.
Not required but, add the end of the process, I suggest to edit the Passkeyâs name to add a hint about which domain it corresponds, can be useful.
Let me know if that works out.
But, again, if as OP your goal is to try Juno, it is not a must. At the bottom there is a small link to sign-in with ic0.app
.
That workaround makes sense, the WebAuthn spec scopes a credential to the current domain or subdomain. The II canister frontend can only lookup and create the credentials of the current domain.
I donât see any way this could be resolved from the II dapp, itâs a limitation in the WebAuthn spec (by design).
This does clearly indicate why itâs so important to have a backup configured for your II, if the domain were to be no longer available and has to change to a different domain, you wonât be able to use the WebAuthn credentials anymore on the new domain.
So regarding backups, you can also use that to use your II anchor from https://identity.ic0.app on https://identity.internetcomputer.org instead of above workaround.
That worked (the alternative link below worked too, I was simply curious :)), thanks a lot!
Cool! Thanks for the feedback.
Forgot about this thread. If youâre interested, I have now published a tutorial on Juno guiding you through the whole process of how to set up your Internet Identity for internetcomputer.org as well.
Please I will appreciate if I can get a help, for several days I have tried to use my ID to login and it has not been funny getting thro, please I need to understand what could be the problem please
Explain with more details pls and maybe somebody can help you.
Thank you for your response, the last time I did, some in this forum sent me a phinsing link
Is there a way to share an image of what I am talking about please
You can upload a image in the comment right here. See the âuploadâ image button i the text field.
When was the âlast timeâ You made these 3 posts so far according to the profile stats.
Upload the image you like to explain and explain in detail if you can. So somebody with expertise can help.
I have tried the images will not upload
Hello @peterparker
I have a question regarding this, why is it that when I try to access my identity that I had signed up on: https://identity.ic0.app/ via https://identity.internetcomputer.org/ itâs telling me that my passkey is not saved at all and I have to create a new identity?
you do not need to set up a new identity, but you need to follow a workaround to re-use the identity if you want that.
you can follow this guide here: Setting Up Your Internet Identity on internetcomputer.org | Juno
I know that there is work going on to âfixâ this issue. maybe @lmuntaner wants to comment on this
actually @peterparker already provided this workaround earlier in the thread:
Thank you @marc0olo!
It worked.
Yes, as @marc0olo mentions this is on the roadmap.
There is no ETA yet. This will need a lot of testing to not disrupt current users from logging in with their current passkeys.