To anyone else who is encountering this issue, here is the root cause and the resolution: The above reported issue has been resolved.
#WEBTREES FAILED TO AUTHENTICATE CODE#
Server returned success HTTP status code (200) OMA-DM session is using Data Sense hresult (0), Initiation origin (5), data sense plan usage state (4) Other messages include (these always show up in pairs of 2): Client is now set to user protocol version 1.2
When recording during the sync process which is initiated by the workplace app the phone logs show the following messages: No further messages are received from client at this point. Vendor/MSFT/PolicyManager/Device/Security/RequireDevicEncryptionġ3UBuoYDUVAPwU/fVoUDZEnZGCLUUjzXXHTXrMsFRTQ= Header:User-Agent: MSFT OMA DM Client/1.2.0.1 Here, in all of it's detail, are the SOAP and SyncML Messages that are exchanged between the server If you need anymore information that is not provided below, please let me know, I will happily provide it. With the digest composed of the ProviderID:Password+nextNonce all properly Base64 Encoded and MD5 digested (send_command_workflow_3_of_3), the server simply doesn't respond back and the error message on the phone states "Failed to authenticate the However, if another command is sent along with the commands, such as (send_command_workflow_1_of_3), the client responds with a in the with a nextNonce value (send_command_workflow_2_of_3). When the sync button is pressed, it successfully sends a message to the MDM server (phone_check_in), when the server responds with just status messages acknowledging theĬommands enrollment reports as a success (successful_server_response).
Here's the scenario: The device successfully enrolls according to the Workplace app. Vendor/MSFT/PolicyManager/My/RequireDeviceEncryption". So far my teammates and I have been able to enroll the device, but not execute any MDM commands like ".
#WEBTREES FAILED TO AUTHENTICATE WINDOWS#
I'm attempting to create an DM Server to manage Windows Phone 8.1.