[Openid-specs-ab] JWT Header for signed id tokens

[Brian Campbell]

OP Command JWTs are explicitly typed, aren't they?

On Thu, Mar 13, 2025 at 12:06 PM george--- via Openid-specs-ab <
openid-specs-ab at lists.openid.net> wrote:

> Hi,
>
> As part of OP Commands, a design goal is to re-use the signing mechanisms
> of the id_tokens in the ecosystem (at least that is my understanding). In
> looking at the OpenID Connect core spec, it’s not very clear what should be
> present in the JWT Header object of a signed (JWS) id_token. The examples
> in the appendix include the ‘kid’ and ‘alg’ claims.
>
> I’m wondering if it’s possible for the OP Command to be an explicitly
> typed JWT to make it very clear it is NOT an id_token (rather than relying
> on presence or absence of a nonce claim) and still use the same keys for
> signing. It seems to me that the keys used for signing are not in any way
> bound to only being used for id_tokens and hence could be used for other
> JWT based structures.
>
> That might make some of this simpler and allow OP Commands to be extended
> in a cleaner way than trying to maintain some compatibility to id_tokens.
>
> Thoughts?
>
> George Fletcher
> Identity Standards Architect
> Practical Identity LLC
>
>
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20250313/4c663389/attachment.htm>