Implemented profile-aware owner key loading.

chrome/browser/chromeos/login/owner_key_reloader.h

+// Copyright 2014 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.
+
+#ifndef CHROME_BROWSER_CHROMEOS_LOGIN_OWNER_KEY_RELOADER_H_
+#define CHROME_BROWSER_CHROMEOS_LOGIN_OWNER_KEY_RELOADER_H_
+
+#include <string>
+
+#include "base/compiler_specific.h"
+#include "base/macros.h"
+#include "content/public/browser/notification_observer.h"
+#include "content/public/browser/notification_registrar.h"
+
+namespace chromeos {
+
+class OwnerKeyReloader : public content::NotificationObserver {

[Mattias Nissler (ping if slow), 2014/05/13 11:55:53]

Instead of tracking login / profile creation explicitly here, why not just make
this a (Profile) KeyedService that starts automatically when we bring up a new
profile and tries to load the owner key then? That'll also move us closer to the
long-term solution where the entire write path moves over to the profile-keyed
helper.

[Nikita (slow), 2014/05/13 15:33:06]

In case of PKS it should ignore sign in profile.

[ygorshenin1, 2014/05/14 09:10:58]

Done.

+ public:
+  OwnerKeyReloader();
+  virtual ~OwnerKeyReloader();
+
+  // content::NotificationObserver implementation:
+  virtual void Observe(int type,
+                       const content::NotificationSource& source,
+                       const content::NotificationDetails& details) OVERRIDE;
+
+  void ReloadOwnerKey(const std::string& username);
+
+ private:
+  std::string username_;
+
+  content::NotificationRegistrar registrar_;
+
+  DISALLOW_COPY_AND_ASSIGN(OwnerKeyReloader);
+};
+
+}  // namespace chromeos
+
+#endif  // CHROME_BROWSER_CHROMEOS_LOGIN_OWNER_KEY_RELOADER_H_