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

[Kristian Smith]

[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?


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: Michael Bowen <Mike.Bowen at microsoft.com>
Sent: Friday, January 26, 2024 2:34 PM
To: David Mulder <dmulder at samba.org>
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

[DocHelp to bcc]

Hi David

Thanks for your question about MS-OAPXBC. We've created case 2401260010005387 to track this issue. One of our engineers will contact you soon.

Best regards,
Mike Bowen
Escalation Engineer - Microsoft Open Specifications

-----Original Message-----
From: David Mulder <dmulder at samba.org>
Sent: Friday, January 26, 2024 12:59 PM
To: Interoperability Documentation Help <dochelp at microsoft.com>
Cc: cifs-protocol at lists.samba.org
Subject: [EXTERNAL] [MS-OAPXBC] 3.2.5.1.3.1 JWT header undefined `ctx`

[MS-OAPXBC] 3.2.5.1.3.1 says that the header fields of the JWT are defined in [RFC7515]. Then it says we must provide:

`ctx (REQUIRED): The base64-encoded bytes used for signature key derivation.`

There is no definition in [RFC7515] for a header field called `ctx`.

--
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
https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.suse.com%2F&data=05%7C02%7CKristian.Smith%40microsoft.com%7C5f633984809b44a026a308dc1ebefc7a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638419052844432915%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=ykJAYLFzhewRuLwmoB6sTg%2B5gefcBYUuYS5SE9ib%2FUg%3D&reserved=0<http://www.suse.com/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20240129/24d9f3af/attachment.htm>