context for the subject can't be assumed to be the same as
> that of the transaction token.
>
> -Justin
> --
> *From:* OAuth on behalf of Atul Tulshibagwale <
> a...@sgnl.ai>
> *Sent:* Thursday, October 26, 2023 4:07 PM
> *To:* Kai Le
e
Sent: Thursday, October 26, 2023 4:07 PM
To: Kai Lehmann
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] sub_id in draft for Transaction tokens
Hi Kai,
Thanks for this and other feedback you have provided.
The primary reason for using "sub_id" was to enable a format that can be more
expr
Hi Kai,
Thanks for this and other feedback you have provided.
The primary reason for using "sub_id" was to enable a format that can be
more expressive than the "sub", which is always a string.
I can see the benefit of having either "sub" or "sub_id" in the Transaction
Tokens spec. "sub" will allo
Hi all,
I very much like the draft. We have a similar token mechanism implemented for
our service infrastructure.
I am not quite sure about the reasoning behind using “sub_id” for the subject
identifier instead of using “sub” as used across OAuth technology. The
referenced draft for SubjectIde
