Chromad: Use DM server reply to determine enrollment type

chrome/browser/ui/webui/chromeos/login/enrollment_screen_handler.cc

Index: chrome/browser/ui/webui/chromeos/login/enrollment_screen_handler.cc
diff --git a/chrome/browser/ui/webui/chromeos/login/enrollment_screen_handler.cc b/chrome/browser/ui/webui/chromeos/login/enrollment_screen_handler.cc
index d78961c37569dc7d716f2156d2f3be17c9c86767..17e6e0ea01c9d80320878a95fc8eb488b86bb347 100644
--- a/chrome/browser/ui/webui/chromeos/login/enrollment_screen_handler.cc
+++ b/chrome/browser/ui/webui/chromeos/login/enrollment_screen_handler.cc
@@ -579,6 +579,7 @@ void EnrollmentScreenHandler::HandleAdDomainJoin(
     authpolicy::ErrorType code) {
   switch (code) {
     case authpolicy::ERROR_NONE:
+      ShowEnrollmentSpinnerScreen();
       controller_->OnAdJoined(gaia::ExtractDomainName(user_name));

[Thiemo Nagel, 2017/02/14 14:45:01]

The email splitting in Chrome is different from email splitting in authpolicy
(though I don't know whether that difference matters).

In the long run, imho it would be good to make the realm a separate parameter to
the JoinAdDomain() D-Bus call.  Wdyt?

[Roman Sorokin (ftl), 2017/02/14 16:01:33]

You mean output param from JoinAdDomain? Make sense

[Thiemo Nagel, 2017/02/14 16:43:05]

I think it could be either an input or an output parameter.  Anything that
ensures that authpolicy and Chrome agree on the realm.

       return;
     case authpolicy::ERROR_UNKNOWN: