Add Kerberos support to webview

android_webview/java/src/org/chromium/android_webview/AwBrowserProcess.java

Index: android_webview/java/src/org/chromium/android_webview/AwBrowserProcess.java
diff --git a/android_webview/java/src/org/chromium/android_webview/AwBrowserProcess.java b/android_webview/java/src/org/chromium/android_webview/AwBrowserProcess.java
index 35bb81ed96d516a924431fa1a3cb0ccd44142413..a0ac2e34bf3e23a27fcdcb76f7155dad77201a37 100644
--- a/android_webview/java/src/org/chromium/android_webview/AwBrowserProcess.java
+++ b/android_webview/java/src/org/chromium/android_webview/AwBrowserProcess.java
@@ -7,6 +7,7 @@
 import android.app.Application;
 import android.content.Context;
 
+import org.chromium.android_webview.policy.AwPolicyProvider;
 import org.chromium.base.ApplicationStatus;
 import org.chromium.base.CommandLine;
 import org.chromium.base.PathUtils;
@@ -15,6 +16,7 @@
 import org.chromium.base.library_loader.LibraryProcessType;
 import org.chromium.base.library_loader.ProcessInitException;
 import org.chromium.content.browser.BrowserStartupController;
+import org.chromium.policy.CombinedPolicyProvider;
 
 /**
  * Wrapper for the steps needed to initialize the java and native sides of webview chromium.
@@ -61,6 +63,12 @@ public void run() {
                 if (application != null) {
                     ApplicationStatus.initializeActivityIndependent(application, context);
                 }
+
+                // The policies are used by browser startup, so we need to register the policy
+                // providers before starting the browser process. This only registers java objects
+                // and doesn't need the native library.
+                CombinedPolicyProvider.get().registerProvider(new AwPolicyProvider(context));

[sgurun-gerrit only, 2015/11/13 08:43:51]

please remind me where the user manager reads the application restrictions from.
did you check if it does add any measurable latency? 

[dgn, 2015/11/25 00:27:15]

We read them through the app restriction system, where the administrator would
set the restrictions on the embedding app. Because this is done asynchronously,
we have a cache (in android shared preferences) that we read the policies
synchronously from. We then update them once we receive the policies from the
app restrictions system. But currently, since those policies can't be updated at
runtime, it's just as if we were only reading them from the cache, which should
not have much impact. I don't think we have any latency comparison, neither on
chrome nor on webview. 

+
                 try {
                     BrowserStartupController.get(context, LibraryProcessType.PROCESS_WEBVIEW)
                             .startBrowserProcessesSync(!CommandLine.getInstance().hasSwitch(