First proposal (22 Jun) about a possible utilization of their solution for our use cases:
Based on our discussion, Vida has sent us an updated version of the flow (11 Jul):
Original Schedule (20 Jul):
Key availability demonstration by us (26 Jul):
The updated version is exactly what we need with the extra syncSignatures call that is mostly due to Vida’s billing purposes (for a functionality that we do not really need…)
This below is an updated version with the missing message transfer added (between FE and Partner BE) and also updates based on the call on 26 Jul.
VIDA update on 28 Jul:
User presence & signing proposal (2 Aug):
12 Aug version:
SDK Flow v2 (22 Aug):
25 Aug version:
Updated schedule (26 Aug):
SDK Flow V2.1 (2 Sep):
CDK security (7 Nov):
Attachments:
VIDA-Proposal-PushSign.pdf (application/pdf)
Push Registration And Offline Sign.pdf (application/pdf)
Schedule - VIDA Auth - Confluence.pdf (application/pdf)
Push Registration And Offline Sign (2).pdf (application/pdf)
Push Registration And Offline Sign v3.pdf (application/pdf)
PushsigningSDKflow v1.pdf (application/pdf)
PushsigningSDKflow v2.pdf (application/pdf)
Push Registration And Offline Sign v4.pdf (application/pdf)
ProposedPushsigningSDKflow-V2.pdf (application/pdf)
Push Registration And Offline Sign v5.pdf (application/pdf)
Push Registration And Offline Sign - Revised Schedule - 260822.pdf (application/pdf)
ProposedPushsigningSDKflow-V2_1.pdf (application/pdf)
CDK-security.pdf (application/pdf)