You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: seed Internet Identity identities on managed networks - #790
Local Internet Identity loses all identities whenever the network state is lost, so developers have to create them again after every launcher or PocketIC upgrade.
With II enabled, icp network start now registers alice, bob and charlie with II and logs one line, Seeding Internet Identity with 3 identities. The per-identity details are logged at debug level.
New optional network setting ii-identities: a list replaces the defaults, [] turns it off.
Local II runs with dummy auth, where the frontend derives an Ed25519 key from the seed index. Each identity is registered with exactly that key, so "use existing passkey" plus the name's position in the list signs in. This works in a fresh browser too.
Every icp network start begins with a fresh network, so the identities are registered on each start. Registration is sequential, so the same names get the same identity numbers every time.
Keys live only in memory. Nothing is added to the user's identities.
Launcher-managed networks only: for image networks, icp-cli can't tell whether II is running.
Fix: nns networks now also get the id.ai friendly domain. nns installs II, but previously only ii added the route.
No launcher or PocketIC change is needed. A follow-up proposal to the II team would make the frontend list these identities by name, without the index prompt.
When Internet Identity is enabled, `icp network start` registers the
identities named by the new `ii-identities` network setting (default:
alice, bob, charlie) with the keys local II's dummy auth derives for
their seed index, and prints the index to sign in with for each.
Limit identity seeding release note to launcher-managed networks
CHANGELOG.md:11
This release note overstates the scope: Docker image networks are also managed networks, but the implementation deliberately skips identity seeding for ManagedMode::Image. Qualify the statement as launcher-managed so users of image networks are not promised unavailable behavior.
nns implies Internet Identity, but only ii put the id.ai entry in
custom-domains.txt, so the address printed for seeded identities did not
route on NNS-only networks.
NNS networks:nns installs II, but only ii added the id.ai friendly domain, so the sign-in address printed on NNS-only networks didn't route (reproduced: HTTP 400). Seeding and the domain entry now share ManagedLauncherConfig::installs_ii(), and id.ai.localhost routes on NNS networks.
Changelog: the entry now says seeding applies to launcher-managed networks, not Docker image networks.
When friendly-domain files are unsupported, this fallback ignores the configured gateway domain. For example, a network launched with gateway.domains: [my-app.localhost] only passes that domain to the launcher, but this reports and registers uqzsh-….localhost; that host is not one of the gateway's routing domains, while the usable standard URL is uqzsh-….my-app.localhost. Preserve gateway_domain(gateway_url) for principal-based routing when friendly aliases are unavailable.
The per-identity table grew with every name. Log a single line like the
balance seeding does, with the details at debug level. The registered
origin now keeps the gateway domain when friendly domains are unavailable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Local Internet Identity loses all identities whenever the network state is lost, so developers have to create them again after every launcher or PocketIC upgrade.
With II enabled,
icp network startnow registersalice,bobandcharliewith II and logs one line,Seeding Internet Identity with 3 identities. The per-identity details are logged at debug level.ii-identities: a list replaces the defaults,[]turns it off.icp network startbegins with a fresh network, so the identities are registered on each start. Registration is sequential, so the same names get the same identity numbers every time.imagenetworks, icp-cli can't tell whether II is running.nnsnetworks now also get theid.aifriendly domain.nnsinstalls II, but previously onlyiiadded the route.No launcher or PocketIC change is needed. A follow-up proposal to the II team would make the frontend list these identities by name, without the index prompt.