Add Kerberos support to webview

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

 // Copyright 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 package org.chromium.android_webview;
 
 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;
 import org.chromium.base.ThreadUtils;
 import org.chromium.base.library_loader.LibraryLoader;
 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.
  */
 public abstract class AwBrowserProcess {
     public static final String PRIVATE_DATA_DIRECTORY_SUFFIX = "webview";
 
     private static final String TAG = "AwBrowserProcess";
 
     /**
@@ skipping 26 matching lines @@
     public static void start(final Context context, final Application application) {
         // We must post to the UI thread to cover the case that the user
         // has invoked Chromium startup by using the (thread-safe)
         // CookieManager rather than creating a WebView.
         ThreadUtils.runOnUiThreadBlocking(new Runnable() {
             @Override
             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(
                                             AwSwitches.WEBVIEW_SANDBOXED_RENDERER));
                 } catch (ProcessInitException e) {
                     throw new RuntimeException("Cannot initialize WebView", e);
                 }
             }
         });
     }
 
     /**
      * Same as {@link #start(Context, Application)} except it does not enable ApplicationStatus.
      */
     public static void start(final Context context) {
         start(context, null);
     }
 }