You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user already has webauthn authenticators setup with Okta, and they have more than one, it would be quite helpful if they could provide names or aliases so that they can select the authenticator that they have on hand.
Expected Behavior
When using an 'unnamed' webauthn authenticator, we should prompt for a name or alias on successful use.
After that, we should include that name or alias when printing the list of possible MFA factors.
A further possible enhancement would be to get a list of webauthn devices currently connected, and if there is a single webauthn device matching the list of possible webauthn devices from Okta only list that device.
However that is definitely a more involved change,
Steps to Reproduce (for bugs)
Register multiple webauthn authenticators through the Okta web interface, attempt to authenticate with gimme-aws-creds, and make a guess as to which option is the authenticator currently plugged in.
Context
Trying to guess which entry is the connected device is a poor experience, and it definitely made me second guess myself at first.
When a user already has webauthn authenticators setup with Okta, and they have more than one, it would be quite helpful if they could provide names or aliases so that they can select the authenticator that they have on hand.
Expected Behavior
When using an 'unnamed' webauthn authenticator, we should prompt for a name or alias on successful use.
After that, we should include that name or alias when printing the list of possible MFA factors.
Current Behavior
Today, you will have multiple entries like:
With the suggested behavior, you would instead get something like:
Possible Solution
PR incoming.
A further possible enhancement would be to get a list of webauthn devices currently connected, and if there is a single webauthn device matching the list of possible webauthn devices from Okta only list that device.
However that is definitely a more involved change,
Steps to Reproduce (for bugs)
Register multiple webauthn authenticators through the Okta web interface, attempt to authenticate with gimme-aws-creds, and make a guess as to which option is the authenticator currently plugged in.
Context
Trying to guess which entry is the connected device is a poor experience, and it definitely made me second guess myself at first.
Your Environment
MacOS Monterey, Version 12.5.1
The text was updated successfully, but these errors were encountered: