Initial POC implementation of the "vLEI Credential Presentation/Revocation API"

[tsterker]

With below scope we should get very far in understanding/validating the interfaces/payloads. In case the scope conflicts with other tasks, we should find a way to get a minimum viable "slice" of it going (e.g. docker container with a single POST route that trigger some webhook).

Scope: Rudimentary/POC implementation of the vLEI Credential Presentation/Revocation API"

• Docker container to register webhook(s)
• webhook registration (via environment variable?)
• at least one type of credential presentation
• at least one type of credential revocation
• Payloads
  • Credential Reporting API (QVIs sending data) - https://github.com/GLEIF-IT/sally/issues/2#issuecomment-1196845683
  • Webhook Payload (KARA sending data)

Intended outcome:

• Frankfurt developers can start building/understanding the general system setup:
  • KARA container
  • "webhook backend"
  • integration with GLEIF API (?)
• Validate the intended approach of webhook registration (via docker environment variables?)
• Hands-on validation of the interfaces/payloads (esp. difference between the presentation API and the webhook payloads?).
• Working on an automated test setup

[pfeairheller]

New docker container is pushed and instructions have been added to this README. The steps can be accomplished within the docker container as it has working versions of both KERIpy and Sally, but I recommend using the repos.

This represents a working POC so I'm closing this issue.