-
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-15333] Portable Desktop Fix #12586
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #12586 +/- ##
==========================================
- Coverage 35.15% 35.10% -0.05%
==========================================
Files 2984 3002 +18
Lines 90539 91359 +820
Branches 16947 17100 +153
==========================================
+ Hits 31827 32074 +247
- Misses 56251 56780 +529
- Partials 2461 2505 +44 ☔ View full report in Codecov by Sentry. |
New Issues (40)Checkmarx found the following issues in this Pull Request
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-15333
Fixes #12141
📔 Objective
We need to support someone using the portable Bitwarden app using and signing in on one account then transporting the executable and data files to another computer and unlocking there. Right now we can't do that because we store the access token and refresh token in
Credential Manager
which is not portable to the new computer.The one problem with this fix is that people who are using the portable app right now on a single computer have their access token in
Credential Manager
and after this change the app will be told secure store isn't supported and won't even look there thinking they don't have an access token and they will need to fully login again. @JaredSnider-Bitwarden and I will need to discuss this and maybe we want TokenService to still look there when it's not supported, but I don't love that.📸 Screenshots
⏰ 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