-
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-18993] Opaque enrollment #13782
base: innovation/opaque
Are you sure you want to change the base?
[PM-18993] Opaque enrollment #13782
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## innovation/opaque #13782 +/- ##
======================================================
- Coverage 35.96% 6.00% -29.97%
======================================================
Files 3177 27 -3150
Lines 93153 1665 -91488
Branches 16975 0 -16975
======================================================
- Hits 33506 100 -33406
+ Misses 57050 1565 -55485
+ Partials 2597 0 -2597 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
New Issues (66)Checkmarx found the following issues in this Pull Request
|
/** | ||
* Authenticate using the Opaque login method. | ||
* @returns The UserKey obtained during the Opaque login flow. | ||
*/ | ||
abstract Login(masterPassword: string): Promise<UserKey>; |
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.
This could be called from a new OpaqueLoginStrategy
, so that the strategy itself can focus on the high level process and bootstrapping the environment, without needing to know about the opaque implementation.
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-18993
📔 Objective
Add client-side support for opaque enrollment.
📸 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