Share via

3.1.5.1.1.2 Response Body

  • Article

If the DRS server successfully creates a device object in the directory, an HTTP 200 status code is returned. Additionally, the response body for the POST response contains a JSON-formatted object, as defined below. See section 3.1.5.1.1.3 for processing details.

 {
     "description": "object",
     "type": "object",
     "properties": {
         "Certificate": {
             "type": "object",
             "optional": false,
             "properties": {
                 "Thumbprint": { "type": "string", "optional": false },
                 "RawBody": { "type": "string", "optional": false }
             }
         },
         "User": {
             "type": "object",
             "optional": false,
             "properties": {
                 "Upn": { "type": "string", "optional": false }
             }
         },
         "MembershipChanges": {
             "type": "object",
             "optional": false,
             "properties": {
                 "LocalSID": { "type": "string", "optional": false },
                 "AddSIDs": { "type": "array", "optional": false }
             }
         }
     }
 }

Certificate: A property with the following fields.

Thumbprint: The SHA1 hash of the certificate thumbprint.

RawBody: An X.509 certificate signed by the DRS server as a base64-encoded string [RFC4648].

User: A property with the following fields.

Upn: The identifier of the identity that authenticated to the Web service. This value MUST be ignored by the client.

MembershipChanges: A property with the following fields.

LocalSID: The security identifier (SID) of the directory administrator account. This value MUST be ignored by the client.

AddSIDs: An empty array. This value MUST be ignored by the client.