Pascal Knoth
Pascal Knoth
closed in favor of #60
I agree with @peppelinux for the clarification about the entity. Note that the change may be reflected in oid4vci which has the same definition in the terminology section https://github.com/openid/OpenID4VCI/blob/main/openid-4-verifiable-credential-issuance-1_0.md#terminology
I think using bearer tokens force to perform authorization at each signature, since we do not have an OAuth server that would help to obtain such tokens, using the instance...
I think mandatory attributes can be useful since it enforces the integrity of the verifiable credential in some cases, some vc do not have any sense with null values for...
I got it now, the `response_mode` parameter should be used within the authorization request which should route the verifier to the redirection in the case of same-device or the display...
> The response_mode isn't really exclusive to cross-device, you can use it on same device too. I took the response_mode as a discriminant to determine if the request is same...
I saw the same device / cross device distinction made at the entry point of the oid4vp flow displaying a QR code or redirecting to the wallet as a response...
I came back to the same / cross-device considerations implementing a demo wallet that is browser-based. When I trigger the same device flow, the redirection is made from the verifier...
For me, it would be great to get in. Hoping we will find out some practices that help integrators to find their way through the hill of specs.