Closed securedimensions closed 4 weeks ago
Have you tried specifying the version of the universal resolver?
No I have not. Thanks for the hint! Will try when back in the office after Sep 9th…Sent from the roadAm 28.08.2024 um 09:08 schrieb Ricky Ng-Adam @.***>: Have you tried specifying the version of the universal resolver? https://dev.uniresolver.io/1.0
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Apologies, my fault! I should have tried dev.uniresolver.io before creating an issue. The DID did:web:emc.spacebel.be:organisations:dlr
is simply not resolvable.
I've tried with another resolvable DID and it shows that either option to start the agent is vaild and identical:
According to this pull request the aries cloud agent v1.0.0 startup parameter
--universal-resolver
is supposed to include DID resolving viahttps://dev.uniresolver.io
.There are two issues for me:
(1) Using the
--universal-resolver https://dev.uniresolver.io
as startup parameter requires to also use the startup parameter--universal-resolver-regex
. Otherwise, the agent won't start:(2) When starting the aries cloud agent 1.0.0 with
--universal-resolver --universal-resolver-regex did:web:.*
does start the agent but there seem to be no attempt to actually resolve DIDs via the Universal Resolver. The attempt to issue a W3C VC via OpenAPI page fails with the following error:However, the direct use of https://dev.uniresolver.io/ resolves the DID as follows:
This is the actual request to issue the W3C VC:
What do I do wrong? Any help is much appreciated...