+oauth working group and Paul:
Denis,
I have gone through every issue request you have made on this draft. I
would like to know what your motivation is for these drafts (I see you have
done the same on the SD-JWT-VC draft). It sort of looks like comment spam.
I realize that you are a long-time
Hi everyone,
*The registration for the OAuth Security Workshop 2025 is now open —
secure your ticket today at
https://oauth.secworkshop.events/osw2025#h.8vvhholy35zc*
We offer both regular tickets as well as companion tickets for attending
the social events only.
OSW 2025 will be hosted by
Thanks for the detailed review and treatment of the issues Deb,
The document editors will take an action to incorporate the indicated
changes in the next draft.
On Thu, Dec 12, 2024 at 6:58 AM Deb Cooley wrote:
> +oauth working group and Paul:
>
> Denis,
>
> I have gone through every issue requ
On Wed, Dec 11, 2024 at 2:56 PM Brian Campbell
wrote:
>
> Thanks Watson,
>
> I'm trying to synthesize this in my own thinking. So please tell me if I'm
> off base. Effectively one manifestation of this is as a problem is a
> verifier, which only uses an https issuer value to find issuer metadata
I think it sounds rather problematic to allow ambiguous situations where
you have an identifier and multiple possible ways of resolving it,
without a clear indication which one should be used.
In my opinion, this information can't be in the credential or in a
verifier config, it needs to be fu
