github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-14 06:04:20 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

PKCS#12 User certificate failed to recognize by Bitwarden Android app #1491

New Issue
Closed
opened 2025-11-26 22:50:35 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-26 22:50:35 -06:00
Owner
Copy Link

Originally created by @lkthomas on GitHub (Sep 11, 2022).

Steps To Reproduce

on the self-hosted Bitwarden server side, I am using Stunnel with verify = 2 enforce peer certificate verification, then I am using the same CA to generate a user certificate, when I check stunnel log, I see this,

SSL_accept: ssl/statem/statem_srvr.c:3697: error:1417C0C7:SSL routines:tls_process_client_certificate:peer did not return a certificate

But my Android phone already installed the key
image

Why Bitwarden Android app can't utilize that key? When I try to use the same setup on desktop firefox, everything goes fine and client certificate could verify without issue.

Expected Result

TLS client certificate should work

Actual Result

User certificate failed to recognize by Bitwarden Android app

Screenshots or Videos

No response

Additional Context

Stunnel config,
docker run -itd --name bitwarden_ssl --link bitwarden:bitwarden_ssl \ -e STUNNEL_VERIFY=3 \ -e STUNNEL_SERVICE=bitwarden \ -e STUNNEL_ACCEPT=443 \ -e STUNNEL_CONNECT=bitwarden:80 \ -e STUNNEL_CAFILE=/etc/stunnel/rootCA.pem \ -p 8080:443 \ -v /bitwarden-data/ssl/host.org-key.pem:/etc/stunnel/stunnel.key:ro \ -v /bitwarden-data/ssl/host.org.pem:/etc/stunnel/stunnel.pem:ro \ -v /bitwarden-data/ssl/rootCA.pem:/etc/stunnel/rootCA.pem:ro \ dweomer/stunnel

Operating System

Android

Operating System Version

No response

Device

Huawei Mate 20 Pro

Build Version

2022.8.0 (4911)

Beta

  • Using a pre-release version of the application.
Originally created by @lkthomas on GitHub (Sep 11, 2022). ### Steps To Reproduce on the self-hosted Bitwarden server side, I am using Stunnel with verify = 2 enforce peer certificate verification, then I am using the same CA to generate a user certificate, when I check stunnel log, I see this, SSL_accept: ssl/statem/statem_srvr.c:3697: error:1417C0C7:SSL routines:tls_process_client_certificate:peer did not return a certificate But my Android phone already installed the key ![image](https://user-images.githubusercontent.com/581053/189546799-cebe6786-a3b4-4c08-afc3-f4f31999dfe1.png) Why Bitwarden Android app can't utilize that key? When I try to use the same setup on desktop firefox, everything goes fine and client certificate could verify without issue. ### Expected Result TLS client certificate should work ### Actual Result User certificate failed to recognize by Bitwarden Android app ### Screenshots or Videos _No response_ ### Additional Context Stunnel config, `docker run -itd --name bitwarden_ssl --link bitwarden:bitwarden_ssl \ -e STUNNEL_VERIFY=3 \ -e STUNNEL_SERVICE=bitwarden \ -e STUNNEL_ACCEPT=443 \ -e STUNNEL_CONNECT=bitwarden:80 \ -e STUNNEL_CAFILE=/etc/stunnel/rootCA.pem \ -p 8080:443 \ -v /bitwarden-data/ssl/host.org-key.pem:/etc/stunnel/stunnel.key:ro \ -v /bitwarden-data/ssl/host.org.pem:/etc/stunnel/stunnel.pem:ro \ -v /bitwarden-data/ssl/rootCA.pem:/etc/stunnel/rootCA.pem:ro \ dweomer/stunnel` ### Operating System Android ### Operating System Version _No response_ ### Device Huawei Mate 20 Pro ### Build Version 2022.8.0 (4911) ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:50:35 -06:00
GiteaMirror commented 2025-11-26 22:50:35 -06:00
Author
Owner
Copy Link

@scottsavarese commented on GitHub (Sep 22, 2022):

This may be related to #582.

@scottsavarese commented on GitHub (Sep 22, 2022): This may be related to #582.
GiteaMirror commented 2025-11-26 22:50:36 -06:00
Author
Owner
Copy Link

@essinghigh commented on GitHub (Sep 23, 2022):

Same issue, Bitwarden application does not appear to support PKCS#12 client cert authentication to my self-hosted instance, hitting my firewall, which drops if no client cert is presented.
This works fine via browser & firefox extension.

@essinghigh commented on GitHub (Sep 23, 2022): Same issue, Bitwarden application does not appear to support PKCS#12 client cert authentication to my self-hosted instance, hitting my firewall, which drops if no client cert is presented. This works fine via browser & firefox extension.
GiteaMirror commented 2025-11-26 22:50:36 -06:00
Author
Owner
Copy Link

@superuser866 commented on GitHub (Nov 18, 2022):

Same issue here on Android after importing PKCS certificate with full CA

TLS client authentication with nginx reverse proxy works well on

  • Web on Chrome and Edge (Windows 11)
  • Bitwarden client 2022.10.1 (Windows 11)
  • Chrome (Android 10 and 12)

NOT working on Android mobile app version 2022.10.0

Popup message during login "Si è verificato un errore"

@superuser866 commented on GitHub (Nov 18, 2022): Same issue here on Android after importing PKCS certificate with full CA TLS client authentication with nginx reverse proxy works well on - Web on Chrome and Edge (Windows 11) - Bitwarden client 2022.10.1 (Windows 11) - Chrome (Android 10 and 12) NOT working on Android mobile app version 2022.10.0 Popup message during login "Si è verificato un errore"
GiteaMirror commented 2025-11-26 22:50:36 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/2066

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/2066
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1491
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?