[CrOS Multidevice] Integrate SecureChannel API into proximity_auth::RemoteDeviceLifeCycle.
This injects SecureChannelClient and local device into RemoteDeviceLifeCycle, both of which are used to make a call to SecureChannel service. If the chromeos::features::kMultiDeviceApi flag is enabled, they are used to create an authenticated BLE connection to the remote device, instead of using BluetoothLowEnergyConnectionFinder. This change also injects a real ClientChannel into ProximityAuthMonitor. R=jhawkins@chromium.org, khorimoto@chromium.org Bug: 824568, 752273 Change-Id: Iefb03d1356ea7e8f5aac0136c8d7a4280302da16 Reviewed-on: https://chromium-review.googlesource.com/1107490 Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Reviewed-by:James Hawkins <jhawkins@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#569825}
Showing
Please register or sign in to comment