[cifs-protocol] What is ADWS? - TrackingID#2406240040003279

[Jeff McCashland (He/him)]

Hi Douglas,

We can confirm that MS-NBFS describes the SOAP protocol, and I see the document does provide binary representation of the Soap format. Is that what you needed, or was something more missing for you to decode the traffic?

If so, I'd like to collect a network trace with the traffic you're unable to decode. To collect that, our policies require me to give you access to our file sharing workspace. In order to do that, I need a Microsoft Account email address. You can create one at Live.com if you don't already have one.

Please let me know how you would like to proceed.


Best regards,
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft Corporation

Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada)

Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300



________________________________
From: Jeff McCashland (He/him) <jeffm at microsoft.com>
Sent: Tuesday, July 9, 2024 2:58 PM
To: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>
Cc: cifs-protocol at lists.samba.org <cifs-protocol at lists.samba.org>; Microsoft Support <supportmail at microsoft.com>
Subject: Re: What is ADWS? - TrackingID#2406240040003279

[Sreekanth to BCC]

Hi Douglas,

Is there a specific problem you're trying to solve? Is this blocking your implementation of ADWS?

MS-ADDM is the main documentation for ADWS.  MS-NBFS describes the SOAP protocol.  ADWS uses the common SOAP based web service protocol described in MS-NBFS, but MS-NBFS is not specific for ADWS.


Best regards,
Jeff McCashland (He/him) | Senior Escalation Engineer | Microsoft Corporation

Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada)

Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300



________________________________
From: Sreekanth Nadendla <srenaden at microsoft.com>
Sent: Monday, June 24, 2024 5:42 AM
To: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>
Cc: cifs-protocol at lists.samba.org <cifs-protocol at lists.samba.org>; Microsoft Support <supportmail at microsoft.com>
Subject: What is ADWS? - TrackingID#2406240040003279

Dochelp in Bcc

Hello Douglas, thank you for your question about Microsoft Open Specifications. We've created an incident #2406240040003279 to track the investigation for this issue. One of the open specifications team members will contact you soon to assist you.


Regards,

Sreekanth Nadendla

Microsoft Windows Open Specifications

________________________________
From: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>
Sent: Sunday, June 23, 2024 7:19 PM
To: Interoperability Documentation Help <dochelp at microsoft.com>; cifs-protocol at lists.samba.org <cifs-protocol at lists.samba.org>
Subject: [EXTERNAL] What is ADWS?

hi Dochelp.

I thought for a long time that Active Directory Web Services (ADWS) was not
fully documented because it the documentation talked about SOAP while the
wire packets are in a binary format that doesn't look at all like XML.

But then I found [MC-NBFX] and [MC-NBFS] and it all fell into place. I think.

What I want to ask is:

Is it broadly correct to say ADWS is mostly described in [MS-ADDM], but the
wire packets have been transformed using the encoding described in [MS-NBFS]
(which describes a specialisation of [MS-NBFX])?

There are other things that extend it various ways ([MS-WSDS], [MS-WSPELD],
[MS-ADCAP], etc), but [MS-ADDM] and [MS-NBFS] are the main ones?

Is there some documentation that links the two together? I note they don't
mention each other.

I don't need a long answer, unless I am completely on the wrong track.

thanks,
Douglas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20240710/64daecd1/attachment.htm>