Add new Content settings type AUTO-SUBMIT-CERTIFICATE

chrome/app/policy/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 76 matching lines @@
 #   policy configuration files. 'dynamic_refresh' controls if the generated
 #   documentation should state that the policy supports dynamic refresh or not.
 #   Supporting dynamic refresh means that Chrome respects the changes to the
 #   policy immediately, without the need for restart.
 #
 # 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: 95
+#   For your editing convenience: highest ID currently used: 97
 #
 # 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 1136 matching lines @@
             },
           ],
           'supported_on': ['chrome.*:10-', 'chrome_os:0.11-'],
           'features': {'dynamic_refresh': 1},
           'example_value': 0,
           'id': 54,
           'caption': '''Default geolocation setting''',
           'desc': '''Allows you to set whether websites are allowed to track the users' physical location. Tracking the users' physical location can be allowed by default, denied by default or the user can be asked everytime a website requests the pysical location.''',
         },
         {
+          'name': 'DefaultAutoSubmitCertificateSetting',
+          'type': 'int-enum',
+          'items': [
+            {
+              'name': 'AllowAutoSubmitCertificate',
+              'value': 1,
+              'caption': '''TODO'''
+            },
+            {
+              'name': 'AllowAutoSubmitCertificate',
+              'value': 2,
+              'caption': '''TODO'''
+            },

[wtc, 2011/08/11 18:33:55]

I am not familiar with the json format of this file, so these
may be stupid questions.

Can two items have the same name (AllowAutoSubmitCertificate)?

What are the values 1 and 2 of these items?

On line 1268, the supported chrome versions should be 15-.

The example_value on line 1270 is 0.  Should it be a value
listed on lines 1259 and 1264 above?

[markusheintz_, 2011/08/15 19:09:04]

Sorry I didn't complete this yet.

You are absolutely right. I can not have the same names. I fixed that.

The integer values are the values of the content settings ALLOW (1), BLOCK (2)
and ASK (3)

I also changed the Chrome version.

+          ],
+          'supported_on': ['chrome.*:14-', 'chrome_os:0.11-'],
+          'features': {'dynamic_refresh': 1},
+          'example_value': 0,
+          'id': 96,
+          'caption': '''TODO''',
+          'desc': '''TODO''',
+        },
+        {
+          'name': 'AutoSubmitCertificateForUrls',

[Mattias Nissler (ping if slow), 2011/08/09 15:37:25]

How are you planning to extend that to matching also the cert? Would it be
possible to prefix the URL pattern with some cert pattern which is TBD? I'm
asking since I'd like the changes to make later be backward-compatible and old
patterns forward-compatible.

[markusheintz_, 2011/08/15 19:09:04]

I don't see another way than appending the string version of the filter to the
pattern. I really don't have a better solution yet. A missing filter would
default to a wildcard that matches anything. So we can stay backwards
compatible.

+          'type': 'list',
+          'supported_on': ['chrome.*:15-', 'chrome_os:0.11-'],
+          'features': {'dynamic_refresh': 1},
+          'example_value': ['http://www.example.com', '[*.]example.edu'],

[wtc, 2011/08/11 18:33:55]

Use https:// in this example_value.  http:// does not use SSL.

Please search for "http://" in this CL and fix all
occurrences. There are several http:// URLs in unit tests.

[markusheintz_, 2011/08/15 19:09:04]

Done.

+          'id': 97,
+          'caption': '''TODO''',
+          'desc': '''TODO''',
+        },
+        {
           'name': 'CookiesAllowedForUrls',
           'type': 'list',
           'supported_on': ['chrome.*:11-', 'chrome_os:0.11-'],
           'features': {'dynamic_refresh': 1},
           'example_value': ['http://www.example.com', '[*.]example.edu'],
           'id': 77,
           'caption': '''Allow cookies on these sites''',
           'desc': '''Allows you to set a list of url patterns that specify sites which are allowed to set cookies.''',
         },
         {
@@ skipping 481 matching lines @@
       'desc': '''The name of the feature that indicates for a given policy that changes to it are respected by Chrome without a browser restart''',
       'text': '''Dynamic Policy Refresh'''
     },
     'doc_deprecated': {
       'desc': '''Text appended in parentheses to the policy name to indicate t hat it has been deprecated''',
       'text': 'deprecated',
     }
   },
   'placeholders': [],
 }