-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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- 2059 Update Two factor webauthn dialog #9009
base: main
Are you sure you want to change the base?
PM- 2059 Update Two factor webauthn dialog #9009
Conversation
…059-update-two-factor-webauthn-dialog
@rr-bw When I click the read key button , it is not opening the windows authentication using PIN like in QA vault. That may be due to that im running using local host. Because I get the following err .. This error is due to the rp value in publicKeyCredentials passed to navigator. So I think this will work in qa vault |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9009 +/- ##
=======================================
Coverage 28.15% 28.16%
=======================================
Files 2432 2432
Lines 71563 71575 +12
Branches 13372 13373 +1
=======================================
+ Hits 20146 20156 +10
- Misses 49830 49831 +1
- Partials 1587 1588 +1 ☔ View full report in Codecov by Sentry. |
New Issues
|
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.
…059-update-two-factor-webauthn-dialog
…059-update-two-factor-webauthn-dialog
@rr-bw Actually the issue is when we give name in the name input field , it should read key. Since we already have issue in reading key in local host , webAuthnResponse is null. And actual workflow is if webAuthnResponse is null Save button should be disabled. It should not be enabled and user is unable to click. But here even if the webAuthnResponse is null save is getting enabled. Yes please help me in debugging. |
@rr-bw Please advise on the above |
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.
It won't let me comment on the specific line, but line 39 of the html file needs updated to tw-text-muted
.
@@ -31,6 +33,7 @@ interface Key { | |||
templateUrl: "two-factor-webauthn.component.html", | |||
}) | |||
export class TwoFactorWebAuthnComponent extends TwoFactorBaseComponent { | |||
@Output() onChangeStatus = new EventEmitter<boolean>(); | |||
type = TwoFactorProviderType.WebAuthn; | |||
name: string; |
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.
Do will still need name
? Where do we access this property?
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.
@rr-bw Yes this is used in setup component , to immediately send enabled status to set up component , the enabled tick mark should appear before we close the dialog . so we are using this event emitter.
apps/web/src/app/auth/settings/two-factor-webauthn.component.ts
Outdated
Show resolved
Hide resolved
apps/web/src/app/auth/settings/two-factor-webauthn.component.html
Outdated
Show resolved
Hide resolved
apps/web/src/app/auth/settings/two-factor-webauthn.component.html
Outdated
Show resolved
Hide resolved
<li>{{ "twoFactorU2fTouchButton" | i18n }}</li> | ||
<li>{{ "twoFactorU2fSaveForm" | i18n }}</li> | ||
</ol> | ||
<div class="tw-flex tw-flex-row"> |
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.
I think tw-flex-row
is unnecessary because it is the default.
apps/web/src/app/auth/settings/two-factor-webauthn.component.html
Outdated
Show resolved
Hide resolved
apps/web/src/app/auth/settings/two-factor-webauthn.component.html
Outdated
Show resolved
Hide resolved
@jlf0dev or @JaredSnider-Bitwarden Would either of you have capacity to help in debugging this? I can't seem to track down the issue. The "save" button is somehow getting enabled when you simply start typing in the name field. It's supposed to remain disabled as long as |
…059-update-two-factor-webauthn-dialog
@KiruthigaManivannan Reading the key should now work, and the "save" button will also remain disabled until the appropriate time. Could you now fix the remaining issues when clicking "deactivate all keys". The dialog should close, a toast should appear, and the green check mark next to "FIDO2 WebAuthn" should get removed. Here is a video of the correct deactivate flow on deactivate.mov |
@willmartian As you said , save button is working as expected now. But clicking on read key button does not do anything. This occurs not only in this branch , but also in main while running in localhost |
Type of change
Objective
Update Two factor webauthn dialog component to use the component library
Code changes
Screenshots
Two-step.login._Webauth_.Bitwarden.Web.vault.-.Google.Chrome.2024-05-02.13-42-28.mp4