No response is sent to the user when they insert or touch their WebAuthn/U2F token. To the user, it's hard to tell if the token is being used or not.
Related Issue
410
Motivation and Context
348 provided a notification that authentication was successful, but there's still a long lag after the user touches the token waiting on the response from Okta. This change notifies the user as soon as they activate the token
How Has This Been Tested?
Tested with multiple Yubikey and Google Titan devices
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
No response is sent to the user when they insert or touch their WebAuthn/U2F token. To the user, it's hard to tell if the token is being used or not.
Related Issue
410
Motivation and Context
348 provided a notification that authentication was successful, but there's still a long lag after the user touches the token waiting on the response from Okta. This change notifies the user as soon as they activate the token
How Has This Been Tested?
Tested with multiple Yubikey and Google Titan devices
Types of changes
Checklist: