Added affiliation IDs for the new affiliation determination.

components/policy/proto/device_management_backend.proto

 // Copyright 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
 package enterprise_management;
 
@@ skipping 359 matching lines @@
   // with a location.
   optional string annotated_location = 20;
 
   // The free-text asset identifier the admin enters to associate the device
   // with a user-generated identifier.
   optional string annotated_asset_id = 21;
 
   // The unique directory api ID of the device which was generated on the
   // server-side.
   optional string directory_api_id = 22;
+  
+  // List of device affiliation IDs. If exists overlap between user
+  // affiliation IDs and device affiliation IDs, we consider that the user is
+  // affiliated on the device. Otherwise the user is not affiliated on the
+  // device. Should be fetched with device policy. Ignored if fetched with 
+  // other polices.
+  repeated string device_affiliation_ids = 23;
+  
+  // List of user affiliation IDs. The list is used to define if current user
+  // is affiliated on the device. See device_affiliation_ids for details. 
+  // Should be fetched with user policy. Ignored if fetched with other polices.
+  repeated string user_affiliation_ids = 24;
 }
 
 message PolicyFetchResponse {
   // Since a single policy request may ask for multiple policies, we
   // provide separate error code for each individual policy fetch.
 
   // We will use standard HTTP Status Code as error code.
   optional int32 error_code = 1;
 
   // Human readable error message for customer support purpose.
@@ skipping 766 matching lines @@
   // Response to remote command request.
   optional DeviceRemoteCommandResponse remote_command_response = 14;
 
   // Response to check device attribute update permission.
   optional DeviceAttributeUpdatePermissionResponse
       device_attribute_update_permission_response = 15;
 
   // Response to update device attribute.
   optional DeviceAttributeUpdateResponse device_attribute_update_response = 16;
 }