Paul Bastian

The same applies to PKCE, Dpop and so on?

This may also relate to PR on reworking batch credential issuance. Additionally it relates to the latest thinking that wallet/client attestation could include an array of public keys that are...

I think this is somewhat solved with key attestation.

To help clarify the issue: - Currently the `claims` value is a JSON object that mimics the nested structure of the credential - The proposal is to make it a...

Option 1.4: rename `mandatory` and `display` to values with `_mandatory` and `_display` (addresses only parts of the problems)

There weren't any opposing arguments in today's DCP call, but we were also short on time. Feedback is appreciated to know that the working group is in favour of the...

Implementers Feedback from IDunion Hackathon 2024 is that implementers are confused when implementing Credential Request, because they usually don't find the credential specific parameters in the Annex and rather expected...

> we brushed-up Paul's original proposals in the in-person WG: > > 1a: make credential_identifiers mandatory in credential request for RAR (can still use format/credential_config_id in authorization req) 1b: make...

Point 4 is still open

> There's a divergence arising because we need to be more precise in the language; "claims" is ambiguous, we need to be clear if we mean claim names or claim...