Torsten Lodderstedt

Based on the discussion in the WG session today, I suggest the following design: a nonce is provided on demand with an error message from the PAR or token endpoint...

One thought just popped up that I would like to share with you. The proposal to use a nonce provided as part of an error response assume the wallet would...

Hi, I'm not comfortable with changing the title of the document depending on the deployment target. That means we need to (in github) change the title for every WG publication...

Is the requirement more related to the wallet or the key the credential shall be bound to? I’m asking since this is the separation between AS (wallet authentication and authorization)...

Is there an example in the wild using "dehydrated credentials". I'm asking since I feel this discussion tries to come up with a reasonable solution for "compression" and at the...

I think we need a understanding of what is implemented today. My assumption would be most implementations support "normal" issuance but not batch issuance so removing the "normal" issuance from...

I would like to understand what complexity is solved on the wallet end by this proposal and how much additional complexity it causes on the issuer end. The current approach...

This is the list of allowed client metadata parameters we agreed on in the WG call on the 21st of May: - jwks - vp_formats - authorization_signed_response_alg - authorization_encrypted_response_alg -...

I'm not a fan of PE. However, it is implemented now with OID4VP in a couple of places. So it is not a show stopper per se and people have...

@decentralgabe what is the problem you want to solve? Do you want to determine whether the user is already known with the SIOP v2 identifier and if not get one...