-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to resolve DID document after upgrading to version 1.2.0 #520
Comments
Also when requesting https://localhost/73650cd4-4750-49bc-ae90-fae346e53e58/did.json from the browser, the response never comes back. |
Can you let us know if @strumswell solution works here @Muhammad-Altabba ? |
Thanks all. Here is the code that do the setup:
However, how to place the did.json in the .well-known directory? The URL used to be automatically served according to the configuration. Is there something I need to do regarding this? Many thanks, |
Can you try matching your resolver config syntax to match our test cases? https://github.com/uport-project/veramo/blob/next/__tests__/localAgent.test.ts#L129 |
Thanks @mirceanis,
And below is my router setup.
|
Hey @Muhammad-Altabba , Your https://github.com/uport-project/veramo/blob/main/packages/cli/default/default.yml#L76 Your code should look like this: import { Application } from 'express';
import { WebDidDocRouter, RequestWithAgentRouter } from '@veramo/remote-server';
import { agent } from './setup';
export default function routes(app: Application): void {
app.use(RequestWithAgentRouter(agent));
app.use(WebDidDocRouter());
} |
This resolved the issue. Thanks, |
Bug severity
5
(I am not sure what configuration I did wrongly)
Describe the bug
Not able to resolve a DID Document.
To Reproduce
Steps to reproduce the behaviour:
Observed behaviour
The
await
, in the above code, never comes back with the DID Doc. It just waits forever.Expected behaviour
Be able to resolve the DID Doc .
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: