Add policy to restrict client domain for Me2Me.

components/policy/resources/policy_templates.json

Index: components/policy/resources/policy_templates.json
diff --git a/components/policy/resources/policy_templates.json b/components/policy/resources/policy_templates.json
index d32fe4f16334c5b9edfcfd1c2f0de6807a35d04f..0ca54206c6f0241b6a34c1c8405f1dc96dccea86 100644
--- a/components/policy/resources/policy_templates.json
+++ b/components/policy/resources/policy_templates.json
@@ -137,7 +137,7 @@
 #   persistent IDs for all fields (but not for groups!) are needed. These are
 #   specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs,
 #   because doing so would break the deployed wire format!
-#   For your editing convenience: highest ID currently used: 315
+#   For your editing convenience: highest ID currently used: 316
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
@@ -701,6 +701,25 @@
           If this setting is disabled and outgoing UDP connections are filtered by the firewall, then this machine can only connect to host machines within the local network.''',
         },
         {
+          'name': 'RemoteAccessHostClientDomain',

[Jamie, 2016/01/28 01:02:22]

I'm not a fan of this name, but by convention, all host-side policies begin with
RemoteAccessHost, and since this restricts the client domain, it seems apt. I'm
open to alternatives.

+          'type': 'string',
+          'schema': { 'type': 'string' },
+          'supported_on': ['chrome.*:22-', 'chrome_os:41-'],
+          'features': {
+            'dynamic_refresh': True,
+            'per_profile': False,
+          },
+          'example_value': 'my-awesome-domain.com',
+          'id': 316,
+          'caption': '''Configure the required domain name for remote access clients''',
+          'tags': [],
+          'desc': '''Configures the required client domain name that will be imposed on remote access clients and prevents users from changing it.
+
+          If this setting is enabled, then only clients from the specified domain can connect to the host.
+
+          If this setting is disabled or not set, then client from any domain can connect to the host.''',

[Sergey Ulanov, 2016/01/28 19:42:46]

For Me2me host only owner can connect. I think it should be mentioned here. Also
maybe add a sentence about RemoteAccessHostDomain policy.

Also this policy is currently implemented for It2Me only, but it's not mentioned
in the description. Potentially this policy can be useful for Me2Me,
particularly if we were to add host sharing, so maybe implement it for me2me
too? Otherwise behavior with this this policy set and without
RemoteAccessHostDomain would not match what one would expect in that case.

[Jamie, 2016/01/29 02:23:27]

Done.

+        },
+        {
           'name': 'RemoteAccessHostFirewallTraversal',
           'type': 'main',
           'schema': { 'type': 'boolean' },