Current utilization of did.json requires a file sit in the webroot of a publicly accessible URL. We have a client where their web hosting lacks a persistent contact and may be unreliable over a longer period of time, so it would be helpful to have an alternative DID authorization that is stored elsewhere (centrally?).
stuartf
commented
1 year ago
Current utilization of did.json requires a file sit in the webroot of a publicly accessible URL. We have a client where their web hosting lacks a persistent contact and may be unreliable over a longer period of time, so it would be helpful to have an alternative DID authorization that is stored elsewhere (centrally?).