Closed Muthurajj closed 2 years ago
Yes, that is possible. The third party would resolve the did:web DID by requesting the DID document from your web server and then proceed to verify the VC.
thank for the reply, I have some points to clear correct me if wrong
1.I have create http://
Yes, almost.
a) ensure that your webserver is reachable via HTTPS with a valid certificate, e.g. at https://domainname.io
b) the filename that you need to create is did.json
including any leading directories, e.g. for DID did:web:domainname.io:myid
you HTTPS server would need to serve the DID document at https://domainname.io/myid/did.json
. You'll find more examples in the spec.
thank, you to have any idea about the did document structure for did:web method
Take a look at the DID Core Spec
1.In did document we have mentioned the service endpoint , The service endpoint is reference to issuer url ? 2.while verifying the vc the verifier will access the endpoint url to check the credentials ??
Take a look at the DID Core Spec
thanks its very useful.
1.In did document we have mentioned the service endpoint , The service endpoint is reference to issuer url ?
It doesn't have to be the issuer URL it could be any URL.
2.while verifying the vc the verifier will access the endpoint url to check the credentials ??
No, the verification is actually designed to not required a back-channel. For the simple verification of the credential it's enough to have access to the credential and the DID documents of the issuer and the holder/presenter. These documents are cryptographically inter-linked to verify that the issuer made a statement (credential) about the holder. See the VC spec for more details.
The did:web method required any blockchain storage for storing the did??
No, it doesn't.
Thanks for the support @jceb
by creating the DID in WEB method the verifiable credential can be verified from the third party verifiers?? creating DID in web method will visible to verifier to access the VC??