From ad134d00c118d4b3378519ad6f4e985a1787284b Mon Sep 17 00:00:00 2001 From: martinsaporiti Date: Tue, 3 Sep 2024 11:16:05 -0300 Subject: [PATCH 1/2] chore: remove kms from docs --- .env-issuer.sample | 7 +------ README.md | 17 ----------------- 2 files changed, 1 insertion(+), 23 deletions(-) diff --git a/.env-issuer.sample b/.env-issuer.sample index 6a37e7ce8..fd214caf0 100644 --- a/.env-issuer.sample +++ b/.env-issuer.sample @@ -17,18 +17,13 @@ ISSUER_ENVIRONMENT=local # -------------------------------------------------------------------------------- # KMS configuration # -------------------------------------------------------------------------------- -# Could be either [localstorage | vault] (BJJ) and [localstorage | vault | aws ] (ETH) +# Could be either [localstorage | vault] (BJJ) and [localstorage | vault ] (ETH) ISSUER_KMS_BJJ_PROVIDER=localstorage ISSUER_KMS_ETH_PROVIDER=localstorage # if the plugin is localstorage, you can specify the folder path ISSUER_KMS_PROVIDER_LOCAL_STORAGE_FILE_PATH=./localstoragekeys -# If the provider is AWS for ETH keys you need to specify the key id and secret key -ISSUER_KMS_ETH_PLUGIN_AWS_ACCESS_KEY=XXX -ISSUER_KMS_ETH_PLUGIN_AWS_SECRET_KEY=YYY -ISSUER_KMS_ETH_PLUGIN_AWS_REGION=eu-west-1 - # if one of the plugins is vault, you have to specify the vault address and token ISSUER_KEY_STORE_ADDRESS=http://vault:8200 ISSUER_KEY_STORE_PLUGIN_IDEN3_MOUNT_PATH=iden3 diff --git a/README.md b/README.md index 94a93be1f..87e91b749 100644 --- a/README.md +++ b/README.md @@ -178,23 +178,6 @@ ISSUER_KMS_ETH_PROVIDER=localstorage To import the private key necessary to transition onchain states, the command is the same as [explained before](#install-and-run-issuer-node-api-and-ui). -#### Running issuer node with AWS KMS Service instead of Vault for ETH Keys -Another alternative for eth keys associated with the identities created in the issuer node is to use the AWS KMS service. -In this case you have to change some variables in the .env-issuer file: - -```bash -ISSUER_KMS_BJJ_PROVIDER= -ISSUER_KMS_ETH_PROVIDER=aws -ISSUER_KMS_ETH_PLUGIN_AWS_ACCESS_KEY= -ISSUER_KMS_ETH_PLUGIN_AWS_SECRET_KEY= -ISSUER_KMS_ETH_PLUGIN_AWS_REGION= -``` - -In this case, to import the private key in AWS KMS run: -```shell -make private_key=XXX aws_access_key=YYY aws_secret_key=ZZZ aws_region=your-region import-private-key-to-kms -``` - ## Quick Start Demo This [Quick Start Demo](https://devs.polygonid.com/docs/quick-start-demo/) will walk you through the process of **issuing** and **verifying** your **first credential**. From b330a7b16fc1883a5b52b10f550a4a57bd128aa9 Mon Sep 17 00:00:00 2001 From: martinsaporiti Date: Tue, 3 Sep 2024 11:22:33 -0300 Subject: [PATCH 2/2] chore: add ISSUER_UNIVERSAL_LINKS_BASE_URL var --- .env-issuer.sample | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.env-issuer.sample b/.env-issuer.sample index fd214caf0..fc921fe13 100644 --- a/.env-issuer.sample +++ b/.env-issuer.sample @@ -61,3 +61,5 @@ ISSUER_RESOLVER_PATH=./resolvers_settings.yaml # if you want, you can specify the content of the resolvers encoded in base64. In this case ISSUER_RESOLVER_PATH have to be empty ISSUER_RESOLVER_FILE= + +ISSUER_UNIVERSAL_LINKS_BASE_URL=https://wallet.privado.id \ No newline at end of file