Introduce new chrome.easyUnlock APIs for getting the sign-in challenge and using it to sign-in the …

chrome/common/extensions/api/easy_unlock_private.idl

Index: chrome/common/extensions/api/easy_unlock_private.idl
diff --git a/chrome/common/extensions/api/easy_unlock_private.idl b/chrome/common/extensions/api/easy_unlock_private.idl
index 6766a00d61d852264fae622f1f2391fee133181c..882505e0d776028e7667f302757af7a3c304fd34 100644
--- a/chrome/common/extensions/api/easy_unlock_private.idl
+++ b/chrome/common/extensions/api/easy_unlock_private.idl
@@ -259,5 +259,13 @@
 
     // Gets the remote device list.
     static void getRemoteDevices(GetRemoteDevicesCallback callback);
+
+    // Gets the sign-in challenge for the current user.
+    static void getSignInChallenge(DataCallback callback);

[Tim Song, 2014/09/08 23:54:23]

Should we pass m2 here and return the wrapped challenge SecureMessage?

[xiyuan, 2014/09/09 02:35:28]

Yep, makes sense.

[tbarzic, 2014/09/09 19:55:49]

I'm nit sure that we'll be able to create the message in Chrome without
knowledge about securemessage proto, so we would probably need a separate
function for signing m2. For first pass, this should be enough though.

[Tim Song, 2014/09/10 00:47:13]

I'm creating the wrapper SecureMessage in the app at the moment, but this will
eventually need to be piped through the TPM.

Okay, let's leave this work for later.

+
+    // Tries to sign-in the current user with a secret obtained by decrypting

[Yoyo Zhou, 2014/09/10 01:16:00]

This says something about trying, but it doesn't say what happens if it succeeds
or fails. Is that something you want to document?

[Tim Song, 2014/09/10 03:07:32]

Done.

+    // the sign-in challenge.
+    static void trySignInSecret(ArrayBuffer signInSecret,
+                                EmptyCallback callback);
   };
 };