[Chrome OS] Adds support for injecting Corp cookies at startup

To support single-sign-on for Chrome OS, we need a way to inject cookies into Chrome.  In the case of session cookies, putting them into Chrome's cookie jar DB doesn't work.  This CL adds a command line flag that tells chrome the name of a Unix pipe to open, from which it can read said cookies.

Eventually, I want to replace this pipe-reading with an appropriate usage of DBus, but Chrome OS isn't there yet.  This CL adds the appropriate infrastructure, though, and the PipeReader class can later be replaced with something that pulls the cookies off DBus instead.
Review URL: http://codereview.chromium.org/174062

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23936 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 8 insertions, 0 deletions

diff --git a/chrome/browser/browser_main.cc b/chrome/browser/browser_main.cc
index bb3d1c3..9b71bde 100644
--- a/chrome/browser/browser_main.cc
+++ b/chrome/browser/browser_main.cc
@@ -117,6 +117,10 @@
 #include "views/focus/accelerator_handler.h"
 #endif
 
+#if defined(OS_CHROMEOS)
+#include "chrome/browser/chromeos/external_cookie_handler.h"
+#endif
+
 namespace Platform {
 
 void WillInitializeMainMessageLoop(const MainFunctionParams& parameters);
@@ -793,6 +797,10 @@ int BrowserMain(const MainFunctionParams& parameters) {
   if (parsed_command_line.HasSwitch(switches::kEnableWebResources))
     profile->InitWebResources();
 
+#if defined(OS_CHROMEOS)
+  ExternalCookieHandler::GetCookies(parsed_command_line, profile);
+#endif
+
   // Stat the directory with the inspector's files so that we can know if we
   // should display the entry in the context menu or not.
   browser_process->CheckForInspectorFiles();