Mark RemoteHostAccessRequireTwoFactor as deprecated.

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 547 matching lines @@
       'type': 'group',
       'caption': '''Configure remote access options''',
       'desc': '''Configure remote access options in <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph>.
 
       These features are ignored unless the Remote Access web application is installed.''',
       'policies': [
         {
           'name': 'RemoteAccessClientFirewallTraversal',
           'type': 'main',
           'schema': { 'type': 'boolean' },
-          'supported_on': ['chrome.*:14-', 'chrome_os:14-'],
+          'supported_on': ['chrome.*:14-16'],  # Removed by https://codereview.chromium.org/8275012.

[bartfab (slow), 2015/02/06 14:18:18]

1) The "chrome.*:14-16" part LGTM.
2) I would prefer to not add any inline comments here though. We have a number
of deprecated policies and we do not tend to include links to the CLs that
deprecated them.
3) What happened to "chrome_os:14-"? Why did it just disappear?

[Łukasz Anforowicz, 2015/02/06 20:29:20]

Ack.
Done.
Thanks for catching this.  I incorrectly removed this thinking that all
Chromoting policies were added much later to ChromeOS - in 41 (when it2me host
support was being added), but this is incorrect for a client-side policy like
the one here.

           'features': {
             'dynamic_refresh': True,
           },
           # Mark this 'removed' when http://crbug.com/100216 is resolved.
           'deprecated': True,
           'example_value': False,
           'id': 94,
           'caption': '''Enable firewall traversal from remote access client''',
           'desc': '''This policy is no longer supported.
           Enables usage of STUN and relay servers when connecting to a remote client.
@@ skipping 37 matching lines @@
           'desc': '''Configures the required host domain name that will be imposed on remote access hosts and prevents users from changing it.
 
           If this setting is enabled, then hosts can be shared only using accounts registered on the specified domain name.
 
           If this setting is disabled or not set, then hosts can be shared using any account.''',
         },
         {
           'name': 'RemoteAccessHostRequireTwoFactor',
           'type': 'main',
           'schema': { 'type': 'boolean' },
-          'supported_on': ['chrome.*:22-', 'chrome_os:41-'],

[Łukasz Anforowicz, 2015/02/06 20:29:20]

This is a host-side policy - it wasn't handled when it2me host support was being
added to ChromeOS in 41.  Therefore chrome_os annotation should be removed here
(this annotation was added in the current/42 release cycle - in
https://codereview.chromium.org/820133002/).

+          'supported_on': ['chrome.*:22-22'],  # Declared, but never used by crrev.com/10825149.

[bartfab (slow), 2015/02/06 14:18:18]

As above.

[Łukasz Anforowicz, 2015/02/06 20:29:20]

Done.

           'features': {
             'dynamic_refresh': True,
             'per_profile': False,
           },
+          'deprecated': True,

[bartfab (slow), 2015/02/06 14:18:18]

Please add the following above this line:

# Mark this 'removed' when http://crbug.com/100216 is resolved.

[Łukasz Anforowicz, 2015/02/06 20:29:20]

Done.

           'example_value': False,
           'id': 155,
           'caption': '''Enable two-factor authentication for remote access hosts''',
           'desc': '''Enables two-factor authentication for remote access hosts instead of a user-specified PIN.
 
           If this setting is enabled, then users must provide a valid two-factor code when accessing a host.
 
           If this setting is disabled or not set, then two-factor will not be enabled and the default behavior of having a user-defined PIN will be used.''',
         },
         {
@@ skipping 6608 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': [],
 }