[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cifs-protocol
Subject:    [cifs-protocol] [MS-MDE]/[MS-MDE2] for Linux clients
From:       David Mulder via cifs-protocol <cifs-protocol () lists ! samba ! org>
Date:       2024-04-08 14:50:09
Message-ID: 0fc5a284-d03f-4f65-b61e-df2123c4948a () suse ! com
[Download RAW message or body]

I can see Windows clients are making the request defined in [MS-MDE2] to 
enroll in Intune (for example, the requests match the examples in 
section 4.1). The Linux intune-client appears to be making a different 
call (though I'm having difficulty seeing the details of that call, 
since I can't seem to intercept the messages via a proxy, etc, unlike on 
Windows).

How does Linux Intune enrollment differ from Windows enrollment? I can 
see that it appears to be communicating with a different endpoint (and 
this endpoint rejects SOAP messages, and instead appears to expect 
json?). Is there a different spec which defines the Linux behavior?

-- 
David Mulder
Labs Software Engineer, Samba
SUSE
1221 S Valley Grove Way, Suite 500
Pleasant Grove, UT 84062
(P)+1 385.208.2989
dmulder@suse.com
http://www.suse.com


_______________________________________________
cifs-protocol mailing list
cifs-protocol@lists.samba.org
https://lists.samba.org/mailman/listinfo/cifs-protocol
[prev in list] [next in list] [prev in thread] [next in thread]