LG-11867: Create separate user events for platform authenticators#11823
LG-11867: Create separate user events for platform authenticators#11823
Conversation
kevinsmaster5
left a comment
There was a problem hiding this comment.
Looks good and local testing works.
Do PRs still need screenshots of the translations for LQA?
I should have clarified in a comment, but: The strings in the current branch are meant to be temporary. There's a follow-up ticket LG-11867 which will implement the final translations, and we'll want to go through the LQA process for that ticket. Related Slack thread: https://gsa-tts.slack.com/archives/C05R6BLVAQG/p1738249868960499 |
|
But I'll update the original pull request comment with screenshots showing each language as it is, since that'd be helpful to share regardless of LQA. Good call-out 👍 Edit: Updated screenshots in original comment. |
changelog: User-Facing Improvements, Account History, Improve history label when adding or removing Face or Touch Unlock
db24f24 to
4490b86
Compare
|
Pushed rebase reflecting latest |
🎫 Ticket
LG-11867
🛠 Summary of changes
Adds new user event types for Face or Touch Unlock platform authenticators.
The implementation of Face or Touch Unlock built upon support for WebAuthn-based security keys. In the implementation of Face or Touch Unlock, the user experience was segmented based on whether or not the authenticator is a platform authenticator. However, prior to these changes, that did not extend to the user events created for adding an removing the authentication method. As a result, adding or removing Face or Touch Unlock would be reflected on a user's Activity page as "Hardware security key added" and "Hardware security key removed". The intent of these changes is to add new event types so that a more appropriate / familiar "Face or touch unlock added" and "Face or touch unlock removed" label can be shown instead.
📜 Testing Plan
👀 Screenshots