Cannot Create Identity
Closed this issue · 7 comments
After Generating api keys with valid username and password, create Identity is not working.
Network Mumbai + private key with testnet MATIC is also provided
It's working at our end. Please share the logs of your API to investigate further.
hi @AnoyRC, are you running the issuer node on http://localhost:3001?
yessir
hi @AnoyRC, are you running the issuer node on http://localhost:3001?
Issuer Logs :
2023-11-25 01:57:36 time=2023-11-24T20:27:36.954Z level=INFO msg="http req" req-id=7660373c3e24/AKSlxQzo8F-000012 method=POST uri=/v1/identities status=401 bytes=14 ua="Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:120.0) Gecko/20100101 Firefox/120.0" d=82.333µs
2023-11-25 01:58:04 time=2023-11-24T20:28:04.240Z level=INFO msg="publishing state to RHS" publishers=1
2023-11-25 01:58:04 time=2023-11-24T20:28:04.240Z level=INFO msg="new state nodes" nodes="[{Hash:18142913... Children:[20049607... 0 0]}]"
2023-11-25 01:58:04 time=2023-11-24T20:28:04.241Z level=INFO msg="http req" req-id=7660373c3e24/AKSlxQzo8F-000014 method=POST uri=/node status=404 bytes=19 ua=Go-http-client/1.1 d=40.792µs
2023-11-25 01:58:04 time=2023-11-24T20:28:04.241Z level=ERROR msg="publishing state to RHS" err="unexpected status code: 404"
2023-11-25 01:58:04 time=2023-11-24T20:28:04.241Z level=ERROR msg="creating identity" err="unexpected status code: 404" id=<nil>
2023-11-25 01:58:04 time=2023-11-24T20:28:04.241Z level=INFO msg="http req" req-id=7660373c3e24/AKSlxQzo8F-000013 method=POST uri=/v1/identities status=500 bytes=51 ua="Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:120.0) Gecko/20100101 Firefox/120.0" d=46.877125ms
hi @AnoyRC, what is the value of ISSUER_CREDENTIAL_STATUS_RHS_MODE in .env-issuer file?
If the value is OffChain you must provide a valid Reverse Hash Service Endpoint in this variable: ISSUER_CREDENTIAL_STATUS_RHS_URL, for instance, you can try our rsh https://rhs-staging.polygonid.me/
If the value of ISSUER_CREDENTIAL_STATUS_RHS_MODE is OffChain you must provide a valid smart contract information, here for Mumbai:
ISSUER_CREDENTIAL_STATUS_ONCHAIN_TREE_STORE_SUPPORTED_CONTRACT=0x76EB7216F2400aC18C842D8C76739F3B8E619DB9
ISSUER_CREDENTIAL_STATUS_RHS_CHAIN_ID=8001
If you choose ISSUER_CREDENTIAL_STATUS_RHS_URL=None the issuer node will resolve revocation credential status and you do not need to set up anything else regarding rhs.
You can check the basic config https://asciinema.org/a/EAdOyamC8QvwoWVGanl9zgMAY
This issue is stale because it has been open 20 days with no activity. Remove stale label, add the enhancement label or comment to avoid closing it in 10 days.
This issue was closed because it has been stalled for 10 days with no activity.