android - Fido2ApiCall 在 Android 版 Chromium 中失败,模式 = 浏览器

标签 android chromium webauthn

03-09 11:48:37.073   996  2738 I <a href="https://stackoverflow.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="1e687b707a716c306f6a7730767f6c7a697f6c7b306d7b6c68777d7b6a6c7f7d757b6c5e2f302c336d7b6c68777d7b" rel="noreferrer noopener nofollow">[email protected]</a>: total connections for service : com.google.android.gms/.chimera.GmsBoundBrokerServiceare :1
03-09 11:48:37.073   996  2738 I <a href="https://stackoverflow.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="6f190a010b001d411e1b0641070e1d0b180e1d0a411c0a1d19060c0a1b1d0e0c040a1d2f5e415d421c0a1d19060c0a" rel="noreferrer noopener nofollow">[email protected]</a>: total connections for client : org.chromium.chromeare :5
03-09 11:48:37.074  1935  5157 D CompatibilityInfo: mCompatibilityFlags - 0
03-09 11:48:37.074  1935  5157 D CompatibilityInfo: applicationDensity - 440
03-09 11:48:37.074  1935  5157 D CompatibilityInfo: applicationScale - 1.0
03-09 11:48:37.074   996  2738 I <a href="https://stackoverflow.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="c0b6a5aea4afb2eeb1b4a9eea8a1b2a4b7a1b2a5eeb3a5b2b6a9a3a5b4b2a1a3aba5b280f1eef2edb3a5b2b6a9a3a5" rel="noreferrer noopener nofollow">[email protected]</a>: startService() is called for servicecom.google.android.gms/.chimera.GmsBoundBrokerService
03-09 11:48:37.078 30122 30122 D BoundBrokerSvc: onBind: Intent { act=com.google.android.gms.fido.fido2.privileged.START pkg=com.google.android.gms }
03-09 11:48:37.078 30122 30122 D BoundBrokerSvc: Loading bound service for intent: Intent { act=com.google.android.gms.fido.fido2.privileged.START pkg=com.google.android.gms }
03-09 11:48:37.079  2895  6467 I SarService: Receiver polling >>>> Change receiver mode: off
03-09 11:48:37.086 30122 30448 E Fido    : [FidoBrowserApiChimeraService] Rejecting browser request from org.chromium.chrome because the hash of the certificate (32A2FC74D731105859E5A85DF16D95F102D85B22099B8064C5D8915C61DAD1E0) is not recognised. [CONTEXT service_id=149 ]
03-09 11:48:37.089 12271 12271 E cr_Fido2Request: FIDO2 API call failed
03-09 11:48:37.089 12271 12271 E cr_Fido2Request: com.google.android.gms.common.api.ApiException: 17: API: Fido.FIDO2_PRIVILEGED_API is not available on this device. Connection failed with: ConnectionResult{statusCode=RESTRICTED_PROFILE, resolution=null, message=null}
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.internal.ApiExceptionUtil.fromStatus(com.google.android.gms:play-services-base@@18.0.1:3)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.api.internal.ApiExceptionMapper.getException(com.google.android.gms:play-services-base@@18.0.1:1)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.api.internal.zag.zad(com.google.android.gms:play-services-base@@18.0.1:1)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.api.internal.zabq.zaE(com.google.android.gms:play-services-base@@18.0.1:7)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.api.internal.zabq.zaD(com.google.android.gms:play-services-base@@18.0.1:2)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.api.internal.zabq.zar(com.google.android.gms:play-services-base@@18.0.1:24)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.api.internal.zabq.onConnectionFailed(com.google.android.gms:play-services-base@@18.0.1:1)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.internal.zai.onConnectionFailed(com.google.android.gms:play-services-base@@18.0.1:1)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.internal.zzf.zzb(com.google.android.gms:play-services-basement@@18.1.0:2)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.internal.zza.zza(com.google.android.gms:play-services-basement@@18.1.0:3)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.internal.zzc.zze(com.google.android.gms:play-services-basement@@18.1.0:3)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at com.google.android.gms.common.internal.zzb.handleMessage(com.google.android.gms:play-services-basement@@18.1.0:31)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at android.os.Handler.dispatchMessage(Handler.java:106)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at android.os.Looper.loop(Looper.java:236)
03-09 11:48:37.089 12271 12271 E cr_Fido2Request:   at android.os.HandlerThread.run(HandlerThread.java:67)
03-09 11:48:37.257   594   594 E SELinux : avc:  denied  { find } for pid=4620 uid=10199 name=tethering scontext=u:r:vendor_systemhelper_app:s0:c512,c768 tcontext=u:object_r:tethering_service:s0 tclass=service_manager permissive=0

Linux 版 Chromium 工作正常。 安卓需要配置哪些设置?感谢您的帮助


最佳答案

请注意日志中的这一行:

Rejecting browser request from org.chromium.chrome because the hash of the certificate (32A2FC74D731105859E5A85DF16D95F102D85B22099B8064C5D8915C61DAD1E0) is not recognised.

Play 服务仅允许已识别的浏览器访问用户的 WebAuthn 凭据。

关于android - Fido2ApiCall 在 Android 版 Chromium 中失败,模式 = 浏览器,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/75745878/

相关文章:

Javascript 读取 Mime 类型 CSV 始终为空

android - FIDO2 - 获取身份验证器信息问题

Android Studio Gradle 构建错误 - Joda 时间

android - 查找回收站 View 中的第一个可见项目是否是列表的第一项

android - 使用 Robolectric 测试 HostApduService

javascript - CEF 支持哪个版本的 ECMAScript?

javascript - Chromium 内部 postMessage 事件

android - Android 上的 Chrome 是否支持使用 Webauthn/FIDO2 对安全 key 进行用户验证?

encryption - 如何在 Web 浏览器中使用 Webauthn/CTAP HMAC-Secret 扩展检索对称 key ?

java - Android:下载受 NTLM 身份验证保护的文件