webauthn-mobile-connector and icons are not called with the MTLs certificate. #2206

Closed
opened 2025-11-26 23:11:45 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @Daniel-dev22 on GitHub (Apr 1, 2025).

I have tested with the latest version and found that webauthn-mobile-connector and icons are not called with the certificate.
Here are a few logs from my HAproxy:

https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/api/config HTTP/2.0" 
https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/api/config HTTP/2.0" 
https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/api/devices/knowndevice HTTP/2.0" 
bitwarden-back/bitwarden 0/0/1/228/229 200 515 - - ---- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/identity/accounts/prelogin HTTP/2.0" 
bitwarden-back/bitwarden 0/0/0/380/380 400 1350 - - ---- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/identity/connect/token HTTP/2.0" 
https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/webauthn-mobile-connector.html?data=eyJjYW[...]dtT
https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/webauthn-mobile-connector.html?data=eyJjYW[...]dtT
bitwarden-back/bitwarden 0/0/3/3949/3952 200 3653 - - ---- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/identity/connect/token HTTP/2.0" 
bitwarden-back/bitwarden 0/0/0/426/438 200 323 - - ---- 3/3/1/1/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "PUT https://[BW-DOMAIN]/api/devices/identifier/3f70[...]2516/token HTTP/2.0" 
bitwarden-back/bitwarden 0/0/2/22/437 200 416232 - - ---- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "GET https://[BW-DOMAIN]/api/sync HTTP/2.0" 
bitwarden-back/bitwarden 0/0/3/30/33 200 1051 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/api/ciphers/create HTTP/2.0" 
https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 5/5/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET /icons/adobe.com/icon.png HTTP/1.1" 
bitwarden-back/bitwarden 0/0/2/10/12 200 1156 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "PUT https://[BW-DOMAIN]/api/ciphers/4655[...]1559633 HTTP/2.0" 
bitwarden-back/bitwarden 0/0/3/4/7 200 681 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "GET https://[BW-DOMAIN]/api/config HTTP/2.0"
[27/Mar/2025:20:57:06.467] https~ bitwarden-back/bitwarden 0/0/3/42/45 200 935 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/api/sends HTTP/2.0" 
[27/Mar/2025:20:57:07.143] https~ https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET / HTTP/1.1" 
https~ bitwarden-back/bitwarden 0/0/3/18/21 200 323 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "DELETE https://[BW-DOMAIN]/api/sends/33c0a[...]159466d HTTP/2.0" 

Otherwise I have not found any problems so far.

Originally posted by @Elegond in https://github.com/bitwarden/android/issues/4486#issuecomment-2759550334

Originally created by @Daniel-dev22 on GitHub (Apr 1, 2025). I have tested with the latest version and found that webauthn-mobile-connector and icons are not called with the certificate. Here are a few logs from my HAproxy: ``` https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/api/config HTTP/2.0" https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/api/config HTTP/2.0" https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/api/devices/knowndevice HTTP/2.0" bitwarden-back/bitwarden 0/0/1/228/229 200 515 - - ---- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/identity/accounts/prelogin HTTP/2.0" bitwarden-back/bitwarden 0/0/0/380/380 400 1350 - - ---- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/identity/connect/token HTTP/2.0" https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/webauthn-mobile-connector.html?data=eyJjYW[...]dtT https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET https://[BW-DOMAIN]/webauthn-mobile-connector.html?data=eyJjYW[...]dtT bitwarden-back/bitwarden 0/0/3/3949/3952 200 3653 - - ---- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/identity/connect/token HTTP/2.0" bitwarden-back/bitwarden 0/0/0/426/438 200 323 - - ---- 3/3/1/1/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "PUT https://[BW-DOMAIN]/api/devices/identifier/3f70[...]2516/token HTTP/2.0" bitwarden-back/bitwarden 0/0/2/22/437 200 416232 - - ---- 3/3/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "GET https://[BW-DOMAIN]/api/sync HTTP/2.0" bitwarden-back/bitwarden 0/0/3/30/33 200 1051 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/api/ciphers/create HTTP/2.0" https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 5/5/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET /icons/adobe.com/icon.png HTTP/1.1" bitwarden-back/bitwarden 0/0/2/10/12 200 1156 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "PUT https://[BW-DOMAIN]/api/ciphers/4655[...]1559633 HTTP/2.0" bitwarden-back/bitwarden 0/0/3/4/7 200 681 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "GET https://[BW-DOMAIN]/api/config HTTP/2.0" [27/Mar/2025:20:57:06.467] https~ bitwarden-back/bitwarden 0/0/3/42/45 200 935 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "POST https://[BW-DOMAIN]/api/sends HTTP/2.0" [27/Mar/2025:20:57:07.143] https~ https/<NOSRV> -1/-1/-1/-1/0 503 216 - - SC-- 2/2/0/0/0 0/0 {[BW-DOMAIN]} {0,""} "GET / HTTP/1.1" https~ bitwarden-back/bitwarden 0/0/3/18/21 200 323 - - ---- 1/1/0/0/0 0/0 {[BW-DOMAIN]} {0,"b-phone.[CA]"} "DELETE https://[BW-DOMAIN]/api/sends/33c0a[...]159466d HTTP/2.0" ``` Otherwise I have not found any problems so far. _Originally posted by @Elegond in https://github.com/bitwarden/android/issues/4486#issuecomment-2759550334_
Author
Owner

@S-Kakar commented on GitHub (Apr 1, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-19774

@S-Kakar commented on GitHub (Apr 1, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-19774
Author
Owner

@Neonwarden commented on GitHub (Apr 1, 2025):

Hi there,

This has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

@Neonwarden commented on GitHub (Apr 1, 2025): Hi there, This has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
Author
Owner

@SaintPatrck commented on GitHub (Apr 28, 2025):

Resolved by #5091

@SaintPatrck commented on GitHub (Apr 28, 2025): Resolved by #5091
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2206