[PR #3694] [PM-10670] Prompt for PIN creation during passkey user verification #10493

Closed
opened 2026-04-11 02:43:26 -05:00 by GiteaMirror · 0 comments
Owner

Original Pull Request: https://github.com/bitwarden/android/pull/3694

State: closed
Merged: Yes


🎟️ Tracking

PM-10670

📔 Objective

Prompt for PIN creation when performing FIDO 2 user verification if the user is using TDE, does not have a master password, and has not previously setup a PIN.

How does this change fix the issue?
During FIDO 2 user verification flows, we only need to know if a PIN has been setup. We don't technically care what the vault unlock method is because we're performing user verification, not unlocking the vault.

📸 Screenshots

passkey-uv-pin-setup.webm

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
**Original Pull Request:** https://github.com/bitwarden/android/pull/3694 **State:** closed **Merged:** Yes --- ## 🎟️ Tracking PM-10670 ## 📔 Objective Prompt for PIN creation when performing FIDO 2 user verification if the user is using TDE, does not have a master password, and has not previously setup a PIN. How does this change fix the issue? During FIDO 2 user verification flows, we only need to know if a PIN has been setup. We don't technically care what the vault unlock method is because we're performing user verification, not unlocking the vault. ## 📸 Screenshots [passkey-uv-pin-setup.webm](https://github.com/user-attachments/assets/1f0f4f99-9a38-4777-b223-5a2211c9df67) ## ⏰ 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
GiteaMirror added the pull-request label 2026-04-11 02:43:26 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#10493