Joseph Heenan
Joseph Heenan
> Clarifying questions: > > 1. Is the objective to be able to take a picture on the device where the wallet resides and send it to the issuer? As...
Discussed on today's WG call - given we still on work to do on the presentation during issuance PR that this would need to build on top of, it seems...
> What is the latest status of this question in 1.1? Is the new Interactive Authorization Endpoint the solution for this problem? Yes, the new IAE is the mechanism to...
Yeah, the first bit is definitely just a typo/oversight. I've opened https://github.com/openid/OpenID4VCI/pull/599 to fix that. I think the system works without `interaction_types_supported` as AS metadata (it's fine for the Wallet...
This sounds really complicated to me. Can dead-end flows be avoided by the AS checking the `interaction_types_supported` the wallet supplies, and erroring (or immediately directing to web) if they are...
discussed on this afternoon's WG call; no one objected to having a specific error code for this case.
I think (as I said above) it's just a signal to developers of what they might need to implement to integrate with a particular issuer, it's not required for the...
Agreed; we should be able to fix this in 1.1 or perhaps in an errata.
My understanding (writing as an individual contributor): F.4 is generic to all proof types, and not all proof types have an `aud` value, which is why it's not included there....
I've updated this PR to target the 1.1 spec - please review. As per @Sakurann's comment above, we'll discuss whether to move some of this to the VP spec and...