search

decentralized-identity / universal-resolver

Universal Resolver implementation and drivers.
https://uniresolver.io/
Apache License 2.0
545 stars 240 forks source link

Can not resolve a public DID from IDunion test ledger #257

Open martinMustermann opened 2 years ago

martinMustermann commented 2 years ago

Reproduce steps:

  1. Follow readme and get docker container running.
  2. Go to IDunion test ledger explorer https://idu.cloudcompass.ca/browse/domain, find a random DID with public profile.
  3. try to run curl -X GET http://localhost:8080/1.0/identifiers/did:sov:RxkWFyrC2WKLS6UsTD7rKo

Expected result: Something should be returned (like diddoc).

Actual result: No resolve result with error notFound.

Am I missing some steps here?

(PS: resolving a random did in sov mainnet is working fine, but facing the same issue when resolving the DIDs from other indy based ledgers)

peacekeeper commented 2 years ago

Hello, the IDunion test ledger is currently configured with a did:sov:idu: prefix. See here:

https://github.com/decentralized-identity/uni-resolver-driver-did-sov/blob/main/docker/Dockerfile#L32

Therefore you should be able to use the following command:

curl -X GET http://localhost:8080/1.0/identifiers/did:sov:idu:RxkWFyrC2WKLS6UsTD7rKo

If the IDunion community prefers to use a different namespace or add additional ledgers, please let us know and/or raise a PR to change the did:sov driver's configuration.