Add new Content settings type AUTO-SUBMIT-CERTIFICATE

chrome/app/policy/policy_templates.json

Index: chrome/app/policy/policy_templates.json
diff --git a/chrome/app/policy/policy_templates.json b/chrome/app/policy/policy_templates.json
index 59d9950e4388232301b07f6daf2d1cbfd7c16371..5bbc895e8f0b6466bfccfb4edb9324f7e77c1cb9 100644
--- a/chrome/app/policy/policy_templates.json
+++ b/chrome/app/policy/policy_templates.json
@@ -94,7 +94,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: 95
+#   For your editing convenience: highest ID currently used: 97
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
@@ -1251,6 +1251,38 @@
           '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-'],