Use ClientAuthenticationConfig in PairingClientAuthenticator

remoting/protocol/authenticator.h

 // Copyright (c) 2012 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 REMOTING_PROTOCOL_AUTHENTICATOR_H_
 #define REMOTING_PROTOCOL_AUTHENTICATOR_H_
 
 #include <string>
 
-#include "base/callback.h"
+#include "base/callback_forward.h"
 #include "base/memory/scoped_ptr.h"
 
 namespace buzz {
 class XmlElement;
 }  // namespace buzz
 
 namespace remoting {
 namespace protocol {
 
 class Authenticator;
 class ChannelAuthenticator;
 
-typedef base::Callback<void(const std::string& secret)> SecretFetchedCallback;
-typedef base::Callback<void(
-    bool pairing_supported,
-    const SecretFetchedCallback& secret_fetched_callback)> FetchSecretCallback;
-
-// Callback passed to |FetchTokenCallback|, and called once the client
-// authentication finishes. |token| is an opaque string that should be sent
-// directly to the host. |shared_secret| should be used by the client to
-// create a V2Authenticator. In case of failure, the callback is called with
-// an empty |token| and |shared_secret|.
-typedef base::Callback<void(const std::string& token,
-                            const std::string& shared_secret)>
-    ThirdPartyTokenFetchedCallback;
-
-// Fetches a third party token from |token_url|. |host_public_key| is sent to
-// the server so it can later authenticate the host. |scope| is a string with a
-// space-separated list of attributes for this connection (e.g.
-// "hostjid:abc@example.com/123 clientjid:def@example.org/456".
-// |token_fetched_callback| is called when the client authentication ends, on
-// the same thread on which FetchThirdPartyTokenCallback was originally called.
-typedef base::Callback<void(
-    const std::string& token_url,
-    const std::string& scope,
-    const ThirdPartyTokenFetchedCallback& token_fetched_callback)>
-    FetchThirdPartyTokenCallback;
-
 // Authenticator is an abstract interface for authentication protocol
 // implementations. Different implementations of this interface may be used on
 // each side of the connection depending of type of the auth protocol. Client
 // and host will repeatedly call their Authenticators and deliver the messages
 // they generate, until successful authentication is reported.
 //
 // Authenticator may exchange multiple messages before session is authenticated.
 // Each message sent/received by an Authenticator is delivered either in a
 // session description inside session-initiate and session-accept messages or in
 // a session-info message. Session-info messages are used only if authenticators
@@ skipping 103 matching lines @@
   // for the result of this method.
   virtual scoped_ptr<Authenticator> CreateAuthenticator(
       const std::string& local_jid,
       const std::string& remote_jid) = 0;
 };
 
 }  // namespace protocol
 }  // namespace remoting
 
 #endif  // REMOTING_PROTOCOL_AUTHENTICATOR_H_