github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-07-11 01:22:47 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[PR #3463] [MERGED] [PM-8137] Set initial FIDO 2 user verification state #23619

New Issue
Closed
opened 2026-04-16 23:39:03 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 23:39:03 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/bitwarden/android/pull/3463
Author: @SaintPatrck
Created: 7/12/2024
Status: ✅ Merged
Merged: 7/16/2024
Merged by: @SaintPatrck

Base: main ← Head: PM-8137/user-verification-state-tracking-main

📝 Commits (7)

  • 9b67fdf [PM-8137] Introduce FIDO 2 user verification state tracking
  • 399e66e Merge branch 'main' into PM-8137/user-verification-state-tracking
  • 19b206e [PM-8137] Set initial FIDO 2 user verification state
  • 725da84 Merge branch 'main' into PM-8137/user-verification-state-tracking-main
  • f4b91e2 Document why initial status is false on new intent
  • 8b39975 Apply suggestion
  • ced81e8 Merge branch 'main' into PM-8137/user-verification-state-tracking-main

📊 Changes

4 files changed (+88 additions, -12 deletions)

View changed files

📝 app/src/main/java/com/x8bit/bitwarden/MainViewModel.kt (+7 -1)
📝 app/src/main/java/com/x8bit/bitwarden/ui/auth/feature/vaultunlock/VaultUnlockViewModel.kt (+6 -0)
📝 app/src/test/java/com/x8bit/bitwarden/MainViewModelTest.kt (+37 -11)
📝 app/src/test/java/com/x8bit/bitwarden/ui/auth/feature/vaultunlock/VaultUnlockViewModelTest.kt (+38 -0)

📄 Description

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-8137

📔 Objective

When a FIDO 2 intent is received the FIDO user verification state is set to unverified so that user verification settings will be evaluated and respected if necessary.

When the user unlocks their vault after the first intent is received the FIDO user verification state is set to verified.

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
    issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/bitwarden/android/pull/3463 **Author:** [@SaintPatrck](https://github.com/SaintPatrck) **Created:** 7/12/2024 **Status:** ✅ Merged **Merged:** 7/16/2024 **Merged by:** [@SaintPatrck](https://github.com/SaintPatrck) **Base:** `main` ← **Head:** `PM-8137/user-verification-state-tracking-main` --- ### 📝 Commits (7) - [`9b67fdf`](https://github.com/bitwarden/android/commit/9b67fdfbc315309963422c22043b023986ac25b7) [PM-8137] Introduce FIDO 2 user verification state tracking - [`399e66e`](https://github.com/bitwarden/android/commit/399e66efdea38bc8df1c8b1317219ecc599807aa) Merge branch 'main' into PM-8137/user-verification-state-tracking - [`19b206e`](https://github.com/bitwarden/android/commit/19b206eaadb8f73e5d9b36ee4e0df124d6531975) [PM-8137] Set initial FIDO 2 user verification state - [`725da84`](https://github.com/bitwarden/android/commit/725da84cdabd300b8de5a08049222daf4b5df42c) Merge branch 'main' into PM-8137/user-verification-state-tracking-main - [`f4b91e2`](https://github.com/bitwarden/android/commit/f4b91e2ce73e74195d1ded827397391497298633) Document why initial status is false on new intent - [`8b39975`](https://github.com/bitwarden/android/commit/8b399754b64e30b1fb5e6f1491631f92c3612ed2) Apply suggestion - [`ced81e8`](https://github.com/bitwarden/android/commit/ced81e832e841fa1e60502c182709647e6ee95f3) Merge branch 'main' into PM-8137/user-verification-state-tracking-main ### 📊 Changes **4 files changed** (+88 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `app/src/main/java/com/x8bit/bitwarden/MainViewModel.kt` (+7 -1) 📝 `app/src/main/java/com/x8bit/bitwarden/ui/auth/feature/vaultunlock/VaultUnlockViewModel.kt` (+6 -0) 📝 `app/src/test/java/com/x8bit/bitwarden/MainViewModelTest.kt` (+37 -11) 📝 `app/src/test/java/com/x8bit/bitwarden/ui/auth/feature/vaultunlock/VaultUnlockViewModelTest.kt` (+38 -0) </details> ### 📄 Description ## 🎟️ Tracking https://bitwarden.atlassian.net/browse/PM-8137 ## 📔 Objective When a FIDO 2 intent is received the FIDO user verification state is set to unverified so that user verification settings will be evaluated and respected if necessary. When the user unlocks their vault after the first intent is received the FIDO user verification state is set to verified. ## ⏰ Reminders before review - Contributor guidelines followed - All formatters and local linters executed and passed - Written new unit and / or integration tests where applicable - Used internationalization (i18n) for all UI strings - CI builds passed - Communicated to DevOps any deployment requirements - Updated any necessary documentation or informed the documentation team ## 🦮 Reviewer guidelines <!-- Suggested interactions but feel free to use (or not) as you desire! --> - 👍 (`:+1:`) or similar for great changes - 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info - ❓ (`:question:`) for questions - 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion - 🎨 (`:art:`) for suggestions / improvements - ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention - 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt - ⛏ (`:pick:`) for minor or nitpick changes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 23:39:03 -05:00
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 pull-request
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#23619
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?