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

Authentication via SSO conflicts with Touch ID - Currently unable to log in with SSO #1105

New Issue
Closed
opened 2025-11-26 22:39:14 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-26 22:39:14 -06:00
Owner
Copy Link

Originally created by @rkujawa on GitHub (Sep 22, 2020).

Originally assigned to: @mpbw2 on GitHub.

(This is a problem I've originally reported via mail, not knowing yet that it is related to Touch ID, but since I have never received a reply, I am reporting here)

Describe the Bug

Some time after app installation, it goes into a state where log in with SSO stops working. However, this happens only if Touch ID is enabled.

Steps To Reproduce

  1. Install Bitwarden app
  2. Open Bitwarden app, authenticate to SSO (provide org id, provide credentials to SSO, master password)
  3. It works, app is fully usable etc.
  4. Enable Touch ID in settings
  5. Wait some amount of time, try logging out, closing the app (sometimes this step must be repeated a few times)
  6. Open Bitwarden app
  7. Click "Enterprise Single Sign-On"
  8. Provide the organization identifier
  9. Click "Log In"
  10. Provide credentials to SSO server
  11. Notice "An error has occurred", "Currently unable to log in with SSO".

At this point it is never possible to authenticate to SSO again, until application is uninstalled and installed again OR until Touch ID is disabled.

Expected Result

Being able to log in via SSO consistently, with Touch ID used to unlock master password.

Actual Result

If Touch ID is enabled, logging in to SSO works only some time after the application is installed, then stops working with "Currently unable to log in with SSO" error.

Screenshots or Videos

None, but it wouldn't really help in this case - it's just a screen with "An error has occurred", "Currently unable to log in with SSO".

Environment

  • Device: iPhone 8
  • Operating system: iOS 14
  • Build Version (go to "Settings" → "About" in the app): 2.6.0 (262)
  • Is this a Beta release? N

Additional Context

Non-SSO authentication works correctly.

Originally created by @rkujawa on GitHub (Sep 22, 2020). Originally assigned to: @mpbw2 on GitHub. (This is a problem I've originally reported via mail, not knowing yet that it is related to Touch ID, but since I have never received a reply, I am reporting here) ## Describe the Bug Some time after app installation, it goes into a state where log in with SSO stops working. However, this happens only if Touch ID is enabled. ## Steps To Reproduce 1. Install Bitwarden app 2. Open Bitwarden app, authenticate to SSO (provide org id, provide credentials to SSO, master password) 3. It works, app is fully usable etc. 4. Enable Touch ID in settings 5. Wait some amount of time, try logging out, closing the app (sometimes this step must be repeated a few times) 6. Open Bitwarden app 7. Click "Enterprise Single Sign-On" 8. Provide the organization identifier 9. Click "Log In" 10. Provide credentials to SSO server 11. Notice "An error has occurred", "Currently unable to log in with SSO". At this point it is never possible to authenticate to SSO again, until application is uninstalled and installed again **OR** until Touch ID is disabled. ## Expected Result Being able to log in via SSO consistently, with Touch ID used to unlock master password. ## Actual Result If Touch ID is enabled, logging in to SSO works only some time after the application is installed, then stops working with "Currently unable to log in with SSO" error. ## Screenshots or Videos None, but it wouldn't really help in this case - it's just a screen with "An error has occurred", "Currently unable to log in with SSO". ## Environment - Device: iPhone 8 - Operating system: iOS 14 - Build Version (go to "Settings" → "About" in the app): 2.6.0 (262) - Is this a Beta release? N ## Additional Context Non-SSO authentication works correctly.
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#1105
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?