How to run internet identity locally without docker?

internet-identity
1

how to run the internet identity locally for testing, without docker internet-identity/HACKING.md at main · dfinity/internet-identity · GitHub

To run the identity provider locally

  1. git clone https://github.com/dfinity/internet-identity#integration-with-internet-identity
  2. cd internet-identity
  3. ./scripts/docker-build
  4. cargo install ic-cdk-optimizer --version 0.3.4
  5. npm ci
  6. dfx start
    7.II_FETCH_ROOT_KEY=1 dfx deploy --no-wallet --argument '(null)'

after step 7 i got this error

  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'

Also, i got this interesting message in the logs

(node:93108) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time.
2

If it can help and assuming with “testing” you mean deploying locally II, I documented various way to deploy and use it locally (without docker) in following blog post:

Easiest being adding following in dfx:

"internet_identity": {
      "type": "custom",
      "candid": "https://github.com/dfinity/internet-identity/releases/latest/download/internet_identity.did",
      "wasm": "https://github.com/dfinity/internet-identity/releases/latest/download/internet_identity_dev.wasm",
      "shrink": false,
      "remote": {
        "candid": "internet_identity.did",
          "id": {
            "ic": "rdmx6-jaaaa-aaaaa-aaadq-cai"
          }
        }
      }
	}
1 Like
3

How can I use that? Can I do it like this?
how to run the internet identity locally for testing, without docker internet-identity/HACKING.md at main · dfinity/internet-identity · GitHub

  1. in dfx.json add this
"internet_identity": {
      "type": "custom",
      "candid": "https://github.com/dfinity/internet-identity/releases/latest/download/internet_identity.did",
      "wasm": "https://github.com/dfinity/internet-identity/releases/latest/download/internet_identity_dev.wasm",
      "shrink": false,
      "remote": {
        "candid": "internet_identity.did",
        "id": {
          "ic": "rdmx6-jaaaa-aaaaa-aaadq-cai"
        }
      }
    },
  1. after that you can use the identity host like this
let identityProvider = "https://identity.ic0.app/#authorize";
    if (process.env.DFX_NETWORK != "ic") {
        identityProvider = "http://127.0.0.1:4943/?canisterId=rkp4c-7iaaa-aaaaa-aaaca-cai&id=r7inp-6aaaa-aaaaa-aaabq-cai"
    }
    return await authClient.login({
        identityProvider,
        onSuccess: () => {
            window.location.reload()
        }
    });

I tried that but when I click login it shows me this, there is no login ui just the canister ui?

Screenshot 2023-01-04 at 5.48.57 AM
Screenshot 2023-01-04 at 5.48.57 AM1920×1142 101 KB

4

Oh that’s good sign, it means the canister was deployed but you picked the wrong canister ID. It happened to me too, the dfx output is a bit confusing.

The output is actually the candid explorer output, what you get in your screenshot. The effective canister ID deployed is the one indicated with param id= not the one with canisterId= (see my screenshot here).

So in your above snippet, instead of

identityProvider = "http://127.0.0.1:4943/?canisterId=rkp4c-7iaaa-aaaaa-aaaca-cai&id=r7inp-6aaaa-aaaaa-aaabq-cai

You can probably use

identityProvider = "http://127.0.0.1:4943/?canisterId=r7inp-6aaaa-aaaaa-aaabq-cai

Alternatively, if you don’t care about developing in Safari, you can also use the canisterId as sub-domain like http://r7inp-6aaaa-aaaaa-aaabq-cai.127.0.0.1:4943/.

Capture d’écran 2023-01-04 à 07.16.06
Capture d’écran 2023-01-04 à 07.16.062148×1022 369 KB

2 Likes
5

I need to see something like this!

Screenshot 2023-01-04 at 9.41.21 AM
Screenshot 2023-01-04 at 9.41.21 AM1920×1139 37.8 KB

However, using the http://127.0.0.1:4943/?canisterId=rkp4c-7iaaa-aaaaa-aaaca-cai without the &id=<id value> results in blanck white page like this
Screenshot 2023-01-04 at 9.42.54 AM
Screenshot 2023-01-04 at 9.42.54 AM1920×1133 22.8 KB

here are my canisters

Screenshot 2023-01-04 at 9.43.10 AM
Screenshot 2023-01-04 at 9.43.10 AM2560×1600 426 KB

6

I wasn’t unsure because I assumed agent-js adds it, but can you try to add #authorize to the identity provider?

let identityProvider = "https://identity.ic0.app/#authorize";
    if (process.env.DFX_NETWORK != "ic") {
        identityProvider = "http://r7inp-6aaaa-aaaaa-aaabq-cai.127.0.0.1:4943?#authorize"
    }
    return await authClient.login({
        identityProvider,
        onSuccess: () => {
            window.location.reload()
        }
    });

does that help?

if not, is your project open source? can you provide the link to your repo?

7

I would be grateful we are having a divinity grant you can get some if you can help :grin:

8

Thanks. Unfortunately I was not able to deploy your project and branch GitHub - aliscie/autodox-tauri at ali/ic locally. When I do so I get various errors.

From the code, I noticed that my last suggestion above was not the one coded, didn’t it work out? Did you gave it a try?

identityProvider = "http://r7inp-6aaaa-aaaaa-aaabq-cai.127.0.0.1:4943?#authorize"
9

Yeah I tried it, it just go to google, like it is invalid url

10

Mmmh hard to tell what is not correct in your app without being able to deploy it unfortunately.

Not later than this morning I answered the same question (How to get the Internet Identity ID dynamically? - #11 by peterparker) and such an url worked out.

11

oh gash solved now it is workin
for some reason using localhost instead of 127.0.0.1 made it works identityProvider = “http://r7inp-6aaaa-aaaaa-aaabq-cai.localhost:4943?#authorize”`

3 Likes
12

Ah cool, happy to hear it worked out!!!

Kind of weird, I remember few weeks ago I had to do the contrary locally to call a canister (not II) - i.e. I had to explicitely switch to 127.0.0.1 instead of localhost :man_shrugging:

2 Likes
13

@AliSci sorry for the delay! I was out for a bit, but I see our local hero @peterparker was able to help. I can also confirm that @peterparker’s suggestion of using remote canisters (described in the blog post linked above) is probably 100x easier than doing the docker build yourself!

Also, if you do go the route of the docker build in the future, note that you do not need to install ic-cdk-optimizer, since that’s already taken care of by the docker build. Out of curiosity, which instructions did you follow? It’d be worth clarifying!

14

yeah his solution is perfect, and I hate docker

3 Likes
15

@nmattia Just wanted to drop another datapoint here that I was encountering the same issue as @AliSci

I add the II dev canister in dfx.json as

"internet_identity": {
      "type": "custom",
      "candid": "https://github.com/dfinity/internet-identity/releases/latest/download/internet_identity.did",
      "wasm": "https://github.com/dfinity/internet-identity/releases/latest/download/internet_identity_dev.wasm",
      "remote": {
        "id": {
          "ic": "rdmx6-jaaaa-aaaaa-aaadq-cai"
        }
      }
    }

However when I try to login locally with

	await authClient.login({
					identityProvider: 'http://127.0.0.1:4943/?canisterId=r7inp-6aaaa-aaaaa-aaabq-cai'
			     });

I get the candidUI frontend but with an II purple gradient background.

Screenshot 2023-04-13 at 14.50.32
Screenshot 2023-04-13 at 14.50.321080×556 54.6 KB

while if I use localhost

await authClient.login({
					identityProvider: 'http://localhost:4943/?canisterId=r7inp-6aaaa-aaaaa-aaabq-cai'
				});

I got the expected II devbuild frontend.

I think importing the devbuild like this in dfx.json is a really smooth experience, but this turned it into something frustrating which others might run into as well.

Browser: Arc with Chromium Engine Version 112.0.5615.49
OS: Macos 13.2.1 (22D68) M1 pro
Frontend framework: sveltekit
dfx 0.12.1

1 Like
16

This worked for me too,i think it’s based on device configuration