DID resolution fails with 404 – Publicly accessible did:web still not resolving

[Zhipeng-lin1]

Hi,

I'm encountering an issue when trying to resolve a did:web identifier. Here's the relevant log output:
DEBUG 2025-04-30T14:09:01.227773 Unauthorized: No public key could be resolved for key-ID 'did:web:<my-domain>#JWK2020-X509-0': Error resolving DID: did:web:<my-domain>. HTTP Code was: 404

To clarify:

• The domain (https://<my-domain>) is publicly accessible.
• The DID document is available at https://<my-domain>/.well-known/did.json and can be opened directly in a browser.
• I'm using <my-domain> here as a placeholder for the actual domain.

Despite this, the resolver still returns a 404.

Questions:

1. Do I need to implement or host anything else for this DID to resolve properly?

Thanks in advance for your help!

[paullatzelsperger]

I'm a bit confused here... does <my-domain> include the participant context ID? That means, is it example.com/participant1 or is it example.com? And related to that, what value are us providing for the did field when creating the participant context?

The DID must match the url, for instance the DID document for did:web:example.com:participant1 would be available at http(s)://example.com/participant1/.well-known/did.json. Obviously, if you have any network infrastructure (ingress controllers, load balancers, api gateways,...) you must take that into account.

So if <my-domain> is just the host without a path, I highly doubt that it works at all.

Also, what is preventing you from debugging the code (WebDidResolver and DidWebController)?

apart from that there are several things you may want to check:

• is https enabled? if you domain is using HTTPS, set edc.iam.did.web.use.https=true so that the resolver prepends "https" instead of "http"
• when you create your participant, are you using the correct value in the did field? I think yes, since the browser returns the correct JSON

[Zhipeng-lin1]

Thanks for the response.

No, does not include the participant context ID; it's only example.com. This domain is playing the role of an issuer. I think I haven't enabled edc.iam.did.web.use.https=true.

[paullatzelsperger]

I will close this discussion, as it is unclear what the problem is, and no clear problem statement has been made.