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
This could be considered a duplicate of #57 but it would be great to have an option to always show the cue message regardless if a suitable key is found or not. I'm trying to provide a good OOTB user experience with minimal configuration. I understand the security implications of this.
Trying a combination of interactive and cue is unfortunately even more confusing - at least on lightdm and gdm as the interactive prompt is shown within the password box and the user has to press enter and then the button (if it exists) on their yubikey to continue. I also tried using a combination of nodetect and cue but with that the cue message won't be shown at all.
I'll try modifying 26f3046 to suit my needs for now, but it thought I'd make the issue as something to consider, thanks in advance!
The text was updated successfully, but these errors were encountered:
Here, it is an authentication failure even with the device already plugged in. Until I hit the button, that's when I'm going to get logged in nevertheless.
This could be considered a duplicate of #57 but it would be great to have an option to always show the cue message regardless if a suitable key is found or not. I'm trying to provide a good OOTB user experience with minimal configuration. I understand the security implications of this.
Trying a combination of
interactive
andcue
is unfortunately even more confusing - at least onlightdm
andgdm
as the interactive prompt is shown within the password box and the user has to press enter and then the button (if it exists) on their yubikey to continue. I also tried using a combination ofnodetect
andcue
but with that the cue message won't be shown at all.I'll try modifying 26f3046 to suit my needs for now, but it thought I'd make the issue as something to consider, thanks in advance!
The text was updated successfully, but these errors were encountered: