Windows MDM OMA DM Setup Phase

Windows MDM OMA DM Setup Phase

After successfull enrollment device polls to the server

In request he gives its credentials in
<cred>
...
</cred>
And in reply to this server replies

But after that in the second request it send a challenge
<chal>
...
<chal>

for this what should be the status to be send...

Here is the request I'm getting from the Device

 

<SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncHdr>
      <VerDTD>1.2</VerDTD>
      <VerProto>DM/1.2</VerProto>
      <SessionID>1</SessionID>
      <MsgID>2</MsgID>
      <Target>
         <LocURI>mdmServerUrl</LocURI>
      </Target>
      <Source>
         <LocURI>deviceId</LocURI>
      </Source>
   </SyncHdr>
   <SyncBody>
      <Status>
         <CmdID>1</CmdID>
         <MsgRef>1</MsgRef>
         <CmdRef>0</CmdRef>
         <Cmd>SyncHdr</Cmd>
         <Chal>
            <Meta>
               <Format xmlns="syncml:metinf">b64</Format>
               <Type xmlns="syncml:metinf">syncml:auth-md5</Type>
               <NextNonce xmlns="syncml:metinf">4Pilpjuggt4uOqqLFmmZYGjMVebjxlAlmVBkco0SbkQ=</NextNonce>
            </Meta>
         </Chal>
         <Data>200</Data>
      </Status>
      <Status>
         <CmdID>2</CmdID>
         <MsgRef>1</MsgRef>
         <CmdRef>4</CmdRef>
         <Cmd>Alert</Cmd>
         <Data>200</Data>
      </Status>
      <Final />
   </SyncBody>
</SyncML>


so what should server respond.

Please help me in this I'm not able to proceed after this.

The server should respond with updated Cred value in the SyncHeader... i.e. using the NextNonce value in the MD5 hash calculation. 

The server should continue to use this new Nonce value until client sends a new chal which specifies a new NextNonce value.

Copyright © 2007-2012 www.chuibin.com Chuibin Copyright