šŸš€ Announcement: identity.ic0.app & identity.internetcomputer.org ā†’ id.ai (Internet Identity 2.0)

Developers internet-identity
,
159

Most Efficient & Least Painful Way to Upgrade Legacy Internet Identities

This is currently the most efficient and least painful method to upgrade legacy Internet Identities while clearly seeing which ID belongs to what.

If you have legacy IDs lying around, this method is strongly recommended.

Step-by-step Upgrade Method

  1. Go to:
    1. https://id.ai/legacy

  2. Remove all existing passkeys, assuming:

    • Your recovery phrase is verified
    • You can successfully recover the identity if needed

  3. Add one new passkey only

    • Name it something like legacy or the legacy ID number
    • The exact name does not matter

  4. Make sure this is the only passkey listed for that identity

  5. Go to:
    https://id.ai

  6. Sign in ā†’ Continue with passkey

  7. Click Upgrade

  8. Enter your legacy ID

  9. Continue

  10. (optional) Additional step remove all the unknown/duplicated passkeys(windows link guide) on windows

VoilĆ .
From testing, this appears to be the most reliable and least confusing way to upgrade.

Issue 1: Passkey Naming Causes Confusion

On https://id.ai/legacy, the name you assign to a passkey is ignored at the OS level.

For example:

  • On Windows, the passkey is always saved as ā€œInternet Identityā€
  • The passkey name cannot be changed, also an windows? restriction
  • This becomes very confusing when managing multiple legacy IDs

Suggested improvement:
Allow the system to automatically use the name set on id.ai/legacy instead of defaulting to ā€œInternet Identityā€.

Issue 2: Adding Additional Devices Is Not Intuitive

When adding another device (for example, a phone):

  1. Go to https://id.ai
  2. Sign in ā†’ Continue with passkey

You are only given two options:

  • Create new identity
  • Use existing identity

Whatā€™s missing is a third option that takes users directly to:

https://id.ai/activate#<secret_code>

This would solve a large number of onboarding and recovery issues.

Current workaround:

This works, but feels accidental rather than intentional UX.

Final thoughts:
The upgrade process can be smooth, but currently relies too much on users discovering unintuitive flows.
A few small UX improvements would save users hours of frustration and reduce support overhead.

2 Likes