Instead of building up a OOB invitation with code in VCAuth controller (this was not working, error boiled down to recipient keys not being added), call ACA-Py to use out-of-band/create-invitation with the resultant presentation exchange.
Use the invitation returned from that as the QR code linked payload.
Note this should only be used in QR code mode at the moment (which is what we configure in all envs for USE_OOB_PRESENT_PROOF) as doing it as a deep link runs into the 'too many characters' issue. A OOB is bigger than a Connections type so there's not really room for the actual proof unless it's narrowed to something as minimal as it gets.
This will be solved by https://github.com/bcgov/vc-authn-oidc/issues/504 anyways, so we won't be using the current deep link paradigm much longer anyways.
Fixes https://github.com/bcgov/vc-authn-oidc/issues/545
Instead of building up a OOB invitation with code in VCAuth controller (this was not working, error boiled down to recipient keys not being added), call ACA-Py to use
out-of-band/create-invitation
with the resultant presentation exchange. Use the invitation returned from that as the QR code linked payload.Note this should only be used in QR code mode at the moment (which is what we configure in all envs for
USE_OOB_PRESENT_PROOF
) as doing it as a deep link runs into the 'too many characters' issue. A OOB is bigger than a Connections type so there's not really room for the actual proof unless it's narrowed to something as minimal as it gets. This will be solved by https://github.com/bcgov/vc-authn-oidc/issues/504 anyways, so we won't be using the current deep link paradigm much longer anyways.Sample payload