Challenge-response: How does attestor get hold of downstream did?

[pwochner]

Once requester has published candidate dDid, it needs to communicate that to attestor (probably already implemented in cli). However, we don't save this information and the attestor needs it again for attestation process. What's the best way to do this?

[pwochner]

The field requester_did of struct ContentCRInitiation containts the candidate dDID. However, it would be nice to have a cli command that prints to terminal information in a more human-friendly way:

• lists all the attestation requests
• For each attestation request:
  • Date
  • Org name
  • Temp key id
  • dDID
  • CR status (complete or not)