-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PM-14863] Force unlock when keys are cleared / on first unlock and fix account switching behavior #11994
Conversation
…switching behavior
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #11994 +/- ##
==========================================
- Coverage 33.53% 33.52% -0.02%
==========================================
Files 2884 2884
Lines 90079 90106 +27
Branches 17132 17135 +3
==========================================
Hits 30208 30208
- Misses 57485 57512 +27
Partials 2386 2386 ☔ View full report in Codecov by Sentry. |
No New Or Fixed Issues Found |
// cipherid is empty has the special meaning of "unlock in order to list public keys" | ||
if (cipherId == "") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue: I might be misunderstanding how this works, but my first thought is that we should use a proper message variable or message type to indicate this and not add hidden meaning to unrelated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that makes sense. We are extending this for other information aswell (information about the ssh request in the future, and process information in #12065) so we need to extend this either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I get the feeling that we're gonna need to take a proper look at how to consolidate this with passkeys, but not in this PR :)
…en/clients into km/PM-14863/allow-unlock-on-list
// cipherid is empty has the special meaning of "unlock in order to list public keys" | ||
if (cipherId == "") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I get the feeling that we're gonna need to take a proper look at how to consolidate this with passkeys, but not in this PR :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just ping me again when you've resolved the conflict 👍
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-14863
📔 Objective
The intended behavior is that:
📸 Screenshots
Screen.Recording.2024-11-14.at.14.43.19.mov
⏰ Reminders before review
🦮 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