[cifs-protocol] [EXTERNAL] [MS-OAPXBC] 3.2.5.1.3.1 JWT header undefined `ctx` - TrackingID#2401260010005387

[Kristian Smith]

Thanks for the confirmation, David. I'll get that change request submitted.

Have a great week!


Regards,

Kristian Smith

Support Escalation Engineer | Azure DevOps, Windows Protocols | Microsoft® Corporation

Office phone: +1 425-421-4442

Email: kristian.smith at microsoft.com<mailto:kristian.smith at microsoft.com>

________________________________
From: David Mulder <dmulder at samba.org>
Sent: Monday, January 29, 2024 12:23 PM
To: Kristian Smith <Kristian.Smith at microsoft.com>
Cc: cifs-protocol at lists.samba.org <cifs-protocol at lists.samba.org>; Microsoft Support <supportmail at microsoft.com>
Subject: Re: [EXTERNAL] [MS-OAPXBC] 3.2.5.1.3.1 JWT header undefined `ctx` - TrackingID#2401260010005387



On 1/29/24 1:20 PM, Kristian Smith wrote:
[Mike to Bcc]

Hi David,

Thanks for reaching out. After a cursory look, you are correct. The "ctx" parameter is not listed in RFC 7515.

It appears that we discuss derivation of the "ctx" parameter in an earlier section (3.1.5.1.3.3). I will suggest the following as a modification to the doc:

From:

"The JWT header fields MUST be given the following values. See [RFC7515]<https://go.microsoft.com/fwlink/?LinkId=691168> section 4 for field descriptions."

To:

"The JWT header fields MUST be given the following values. See [RFC7515]<https://go.microsoft.com/fwlink/?LinkId=691168> section 4 for field descriptions. The derivation for the "ctx" parameter is discussed in section 3.1.5.1.3.3."

Would this document modification provide the needed clarity?
Yes, that sounds fine.

--
David Mulder
Labs Software Engineer, Samba
SUSE
1221 S Valley Grove Way, Suite 500
Pleasant Grove, UT 84062
(P)+1 385.208.2989
dmulder at suse.com<mailto:dmulder at suse.com>
http://www.suse.com<http://www.suse.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20240129/67c4a7e8/attachment.htm>