github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-17 18:43:11 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

iOS/ipadOS 13.x cannot login on selfhosted bitwarden instance #831

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

Originally created by @l0rda on GitHub (Sep 26, 2019).

Hello,
i have own bw instance in docker container at local network.
CA certificate is added to ipad and iphone. It is fully trusted. I can login via browser, but mobile app says: "There is a problem connecting to the server". Of course, https is enabled. Container logs are empty, so i think there is problem with certificate.

This is started when updated to ios/ipados 13.1 (also maybe 13.0).

Originally created by @l0rda on GitHub (Sep 26, 2019). <!-- Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> Hello, i have own bw instance in docker container at local network. CA certificate is added to ipad and iphone. It is fully trusted. I can login via browser, but mobile app says: "There is a problem connecting to the server". Of course, https is enabled. Container logs are empty, so i think there is problem with certificate. This is started when updated to ios/ipados 13.1 (also maybe 13.0).
GiteaMirror commented 2025-11-26 22:31:42 -06:00
Author
Owner
Copy Link

@nessor commented on GitHub (Sep 26, 2019):

Can't confirm this with iOS 13 and iOS 13.1.

Are you trying to login the first time or are you already logged in while updating to the new iOS?

@nessor commented on GitHub (Sep 26, 2019): Can't confirm this with iOS 13 and iOS 13.1. Are you trying to login the first time or are you already logged in while updating to the new iOS?
GiteaMirror commented 2025-11-26 22:31:45 -06:00
Author
Owner
Copy Link

@l0rda commented on GitHub (Sep 26, 2019):

On ipadOS was clean install.
On phone i was previously logged in. I tried to sync and it is not work, then logged out and tried to log in again, got this error.

@l0rda commented on GitHub (Sep 26, 2019): On ipadOS was clean install. On phone i was previously logged in. I tried to sync and it is not work, then logged out and tried to log in again, got this error.
GiteaMirror commented 2025-11-26 22:31:47 -06:00
Author
Owner
Copy Link

@l0rda commented on GitHub (Sep 26, 2019):

I found, what can be a problem:
https://support.apple.com/en-us/HT210176

Additionally, all TLS server certificates issued after July 1, 2019 (as indicated in the NotBefore field of the certificate) must follow these guidelines:
TLS server certificates must contain an ExtendedKeyUsage (EKU) extension containing the id-kp-serverAuth OID.
TLS server certificates must have a validity period of 825 days or fewer (as expressed in the NotBefore and NotAfter fields of the certificate).
Connections to TLS servers violating these new requirements will fail and may cause network failures, apps to fail, and websites to not load in Safari in iOS 13 and macOS 10.15.

@l0rda commented on GitHub (Sep 26, 2019): I found, what can be a problem: https://support.apple.com/en-us/HT210176 Additionally, all TLS server certificates issued after July 1, 2019 (as indicated in the NotBefore field of the certificate) must follow these guidelines: TLS server certificates must contain an ExtendedKeyUsage (EKU) extension containing the id-kp-serverAuth OID. TLS server certificates must have a validity period of 825 days or fewer (as expressed in the NotBefore and NotAfter fields of the certificate). Connections to TLS servers violating these new requirements will fail and may cause network failures, apps to fail, and websites to not load in Safari in iOS 13 and macOS 10.15.
GiteaMirror commented 2025-11-26 22:31:49 -06:00
Author
Owner
Copy Link

@l0rda commented on GitHub (Sep 26, 2019):

I confirm, certificate was issued at 9 july 2019 and has a validity period more than 825.
With new server certificate all work fine.

@l0rda commented on GitHub (Sep 26, 2019): I confirm, certificate was issued at 9 july 2019 and has a validity period more than 825. With new server certificate all work fine.
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
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#831
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?