Kristina

it's described as part of client identifier prefixes section. in summary: - when verifier is pre-registered with the wallet in OAuth style (client_id_prefix pre-registered), usual oauth 2.0 rules apply. -...

i think this came up in OIDF - EC call where it was recommended to remove this section, at least from HAIP 1.0

@javereec we added non-key bound credentials to openid4vp. we can always use self-signed credentials using openid4vp if needed

has this been resolved with https://github.com/openid/OpenID4VP/pull/254 ? closing in a week unless objections.

resolved by https://github.com/openid/OpenID4VP/pull/263 and https://github.com/openid/OpenID4VP/pull/308

yes, we have a security considerations section on pre-authorized code flow https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html#section-12.3

WG discussion: - direction seems to make sense.

WG discussion: - current structure of the issuer metadata makes sense. also to enable a use-case of sending this object in the credential response - no concerns with `credential_metadata` parameter...

+1. there seems to be multiple implementers working on/interested in this in the EU and ISO communities

WG discussion - this solves a real problem: want to do it in 1.0, not 1.1 - there is quite some implementation experience (in cases without DC API) - requirements:...