-
Notifications
You must be signed in to change notification settings - Fork 87
[PM-22202] Perform sync in Fido2 findCredentials when they have counter #2201
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
base: main
Are you sure you want to change the base?
Conversation
…2 credentials with counter and sync is actually needed (30min has passed since last one).
|
Great job! No new security vulnerabilities introduced in this pull request |
…s and added unit tests.
|
Claude finished @fedemkr's task in 2m 11s —— View job Code Review Complete
The code review agent has analyzed this PR and posted inline comments with findings. Please review the inline comments for specific feedback. |
Code Review in Progress
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2201 +/- ##
==========================================
+ Coverage 85.52% 85.54% +0.01%
==========================================
Files 1738 1738
Lines 147216 147383 +167
==========================================
+ Hits 125909 126073 +164
- Misses 21307 21310 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
BitwardenShared/Core/Vault/Services/Fido2CredentialStoreService.swift
Outdated
Show resolved
Hide resolved
…e.swift Co-authored-by: Matt Czech <matt@livefront.com>

🎟️ Tracking
PM-22202
📔 Objective
Performance improvement to only sync credentials in Fido2 flows when there are Fido2 credentials with
counter > 0and the sync is needed (30 min have passed since last one).Important
findCredentialsnow calls a private function to prevent infinite loop while using recursion in some edge cases sync may present.⏰ 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