Public Sessions: fetch device robot api token during enterprise enrollment.

chrome/browser/chromeos/settings/device_oauth2_token_service.h

Index: chrome/browser/chromeos/settings/device_oauth2_token_service.h
diff --git a/chrome/browser/chromeos/settings/device_oauth2_token_service.h b/chrome/browser/chromeos/settings/device_oauth2_token_service.h
index 097008090d8d63114f418dcaf3e89b4a45086e34..122289ef211972466e0a33f78d7cf1e5b16d5771 100644
--- a/chrome/browser/chromeos/settings/device_oauth2_token_service.h
+++ b/chrome/browser/chromeos/settings/device_oauth2_token_service.h
@@ -17,6 +17,12 @@ namespace net {
 class URLRequestContextGetter;
 }
 
+namespace policy {
+namespace test {
+class DeviceCloudPolicyManagerChromeOSEnrollmentTest;
+}
+}
+
 class GoogleServiceAuthError;
 class PrefRegistrySimple;
 class PrefService;
@@ -44,6 +50,7 @@ class DeviceOAuth2TokenService : public OAuth2TokenService {
 
  private:
   friend class DeviceOAuth2TokenServiceFactory;
+  friend class policy::test::DeviceCloudPolicyManagerChromeOSEnrollmentTest;

[Mattias Nissler (ping if slow), 2013/04/22 10:59:00]

Is there anything wrong with making GetRefreshToken() public so we can avoid
these friend declarations?

[David Roche, 2013/04/23 01:36:08]

I guess not.  It seemed like clients of these classes "shouldn't" call
GetRefreshToken (or Initialize/Shutdown on the factory), but perhaps it's not
worth the hoops and extra LOC to keep them protected.  The only downside is that
any code could call Shutdown on the factory and cause it to return null to other
clients, but I suppose that sort of thing will quickly fail in testing anyway
(and hopefully code review too).

   FRIEND_TEST_ALL_PREFIXES(DeviceOAuth2TokenServiceTest, SaveEncryptedToken);
 
   // Use DeviceOAuth2TokenServiceFactory to get an instance of this class.