Reusing names of policy keys from policy_constants.h

components/policy/resources/policy_templates.json

 {
 # policy_templates.json - Metafile for policy templates
 #
 # The content of this file is evaluated as a Python expression.
 #
 # This file is used as input to generate the following policy templates:
 # ADM, ADMX+ADML, MCX/plist and html documentation.
 #
 # Policy templates are user interface definitions or documents about the
 # policies that can be used to configure Chrome. Each policy is a name-value
@@ skipping 105 matching lines @@
 #   templates and documentation. The policy definition list that Chrome sees
 #   will include policies marked with 'future'. If a WIP policy isn't meant to
 #   be seen by the policy providers either, the 'supported_on' key should be set
 #   to an empty list.
 #
 # IDs:
 #   Since a Protocol Buffer definition is generated from this file, unique and
 #   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: 284
+#   For your editing convenience: highest ID currently used: 289
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
 #     $1 -> Google Chrome / Chromium
 #     $2 -> Google Chrome OS / Chromium OS
 #     $3 -> Google Chrome Frame / Chromium Frame
 #     $6 is reserved for doc_writer
 #
 # Device Policy:
 #   An additional flag device_only (optional, defaults to False) indicates
@@ skipping 601 matching lines @@
             'dynamic_refresh': True,
             'per_profile': False,
           },
           'example_value': '12400-12409',
           'id': 264,
           'caption': '''Restrict the UDP port range used by the remote access host''',
           'desc': '''Restricts the UDP port range used by the remote access host in this machine.
 
           If this policy is left not set, or if it is set to an empty string, the remote access host will be allowed to use any available port, unless the policy <ph name="REMOTEACCESSHOSTFIREWALLTRAVERSAL_POLICY_NAME">RemoteAccessHostFirewallTraversal</ph> is disabled, in which case the remote access host will use UDP ports in the 12400-12409 range.''',
         },
+        {
+          'name': 'RemoteAccessHostMatchUsername',
+          'type': 'main',
+          'schema': { 'type': 'boolean' },
+          'supported_on': ['chrome.*:36-'],
+          'supported_on DO NOT SUBMIT': 'simonmorris@chromium.org 2012-10-30 22:31:12 52ba3ea',
+          'features': {
+            'dynamic_refresh': True,
+            'per_profile': False,
+          },
+          'example_value': False,
+          'id': 285,
+          'caption': '''Requires that username of the local user and the host owner match''',

[Sergey Ulanov, 2015/01/05 17:51:56]

Caption should make it clear that this is a policy for the CRD host, and it
doesn't.

[Łukasz Anforowicz, 2015/01/05 19:40:23]

Good point.  I'll fix this in a later patchset (when fixing the other new
entries in this file).

+          'desc': '''Requires that username of the local user and the host owner match.
+
+          If this setting is enabled, then the host will not start if the name of the host owner is different from the name of the local user that the host is associated with.
+
+          If this setting is disabled or not set, then the host can be associated with any local user.
+
+          This policy is ignored on Windows.''',
+        },
+        {
+          'name': 'RemoteAccessHostTokenUrl',
+          'type': 'string',
+          'schema': { 'type': 'string' },
+          'supported_on': ['chrome.*:36-'],
+          'supported_on DO NOT SUBMIT': 'rmsousa@chromium.org 2013-04-06 04:50:43 4386f0a',

[Sergey Ulanov, 2015/01/05 17:51:56]

There are bunch of "DO NO SUBMIT" in this file. Were you planning to double
check them?

[Łukasz Anforowicz, 2015/01/05 19:40:23]

I wanted to get an ACK on the general direction of the changes, before spending
time on researching Chrome versions + looping in Renato for helping with
captions and descriptions of the policies introduced by him.  

I guess I hear that I should fix the "DO NOT SUBMITS", but other than them
things look more or less okay (both from Chromoting and from Policy
perspective).

+          'features': {
+            'dynamic_refresh': True,
+            'per_profile': False,
+          },
+          'example_value': 'DO NOT SUBMIT',
+          'id': 286,
+          'caption': '''DO NOT SUBMIT''',
+          'desc': '''DO NOT SUBMIT
+
+          DO NOT SUBMIT''',
+        },
+        {
+          'name': 'RemoteAccessHostTokenValidationUrl',
+          'type': 'string',
+          'schema': { 'type': 'string' },
+          'supported_on': ['chrome.*:36-'],
+          'supported_on DO NOT SUBMIT': 'rmsousa@chromium.org 2013-04-06 04:50:43 4386f0a',
+          'features': {
+            'dynamic_refresh': True,
+            'per_profile': False,
+          },
+          'example_value': 'DO NOT SUBMIT',
+          'id': 287,
+          'caption': '''DO NOT SUBMIT''',
+          'desc': '''DO NOT SUBMIT
+
+          DO NOT SUBMIT''',
+        },
+        {
+          'name': 'RemoteAccessHostTokenValidationCertificateIssuer',
+          'type': 'string',
+          'schema': { 'type': 'string' },
+          'supported_on': ['chrome.*:36-'],
+          'supported_on DO NOT SUBMIT': 'rmsousa@chromium.org 2014-01-25 01:46:03 7181799',
+          'features': {
+            'dynamic_refresh': True,
+            'per_profile': False,
+          },
+          'example_value': 'DO NOT SUBMIT',
+          'id': 288,
+          'caption': '''DO NOT SUBMIT''',
+          'desc': '''DO NOT SUBMIT
+
+          DO NOT SUBMIT''',
+        },
+        {
+          'name': 'RemoteAccessHostDebugOverridePolicies',
+          'type': 'string',
+          'schema': { 'type': 'string' },
+          'supported_on': ['chrome.*:36-'],
+          'supported_on DO NOT SUBMIT': 'wez@chromium.org 2012-11-13 10:08:38 158b287',
+          'features': {
+            'dynamic_refresh': True,
+            'per_profile': False,
+          },
+          'example_value': '{ "RemoteAccessHostMatchUsername": true }',

[Sergey Ulanov, 2015/01/05 17:51:56]

Please fix.

[Łukasz Anforowicz, 2015/01/05 19:40:23]

Why?  What is wrong with this example?  The example is a string that contains
JSON representation of Chromoting policies.  I picked
RemoteAccessHostMatchUsername as an example.  Should I include 2 policies in the
JSON example to make it more obvious that this is not a copy&paste error / that
I didn't use RemoteAccessHostMatchUsername example instead of
RemoteAccessHostDebugOverridePolicies example?

+          'id': 289,
+          'caption': '''Policy overrides for Debug builds of the host''',
+          'desc': '''Overrides policies on Debug builds of the host.
+
+          The value is parsed as a JSON dictionary of policy name to policy value mappings.''',
+        },
       ],
     },
     {
       'name': 'PrintingEnabled',
       'type': 'main',
       'schema': { 'type': 'boolean' },
       'supported_on': ['chrome.*:8-', 'chrome_os:11-', 'android:39-'],
       'features': {
         'dynamic_refresh': True,
         'per_profile': True,
@@ skipping 6403 matching lines @@
       'desc': '''Text appended in parentheses next to the policies top-level container to indicate that those policies are of the Recommended level''',
       'text': 'Default Settings (users can override)',
     },
     'doc_complex_policies_on_windows': {
       'desc': '''Text pointing the user to a help article for complex policies on Windows''',
       'text': '''encoded as a JSON string, for details see <ph name="COMPLEX_POLICIES_URL">http://www.chromium.org/administrators/complex-policies-on-windows<ex>http://www.chromium.org/administrators/complex-policies-on-windows</ex></ph>''',
     },
   },
   'placeholders': [],
 }