OCSP responder for v3 documents

[morgatron]

The OCSP responder looks great for DID-signed documents, especially those for v3. However it seems that v3 documents aren't currently supported:

      case v3.RevocationType.OcspResponder:
        throw new Error("Ocsp revocation type not yet supported for v3");

(from didSignedDocumentStatus.ts)
This seems pretty straightforward to add however, using the v2 code as a guide.

Are there any plans to add this?

[HJunyuan]

Hi @morgatron, thanks for the suggestion! We'll add this into our backlog and keep you updated here when it gets implemented.

[morgatron]

Thanks @HJunyuan !
I'm guessing you can't give us a time estimate? ;)

[morgatron]

To be clear, it's looking like this will be important for our customer. We'll be needing the feature in the next couple of months...

any clarity you can provide would be fantastic.

[morgatron]

I could be wrong, but it looks as simple as replacing

  case v3.RevocationType.OcspResponder:
    throw new Error("Ocsp revocation type not yet supported for v3");

with

  case v3.RevocationType.OcspResponder:
    if (typeof location === "string") {
      return isRevokedByOcspResponder2({
        merkleRoot,
        targetHash,
        proofs,
        location,
      })
    }

in didSignedDocumentStatus.ts

I can raise a PR if desired, but I'm not sure I understand how tests work for this currently so I'm not sure I can update them.

Let me know!

[HJunyuan]

Yes you are right! We'll just need to focus on creating the tests and it should be done. Will get started on this around this or next week or when the new sprint starts.

[john-dot-oa]

🎉 This issue has been resolved in version 8.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[morgatron]

Great!!