Currently Safari doesn't ask for a PIN on security keys that have it set, this causes userVerification never to be true when invoking `navigator.credentials.get`. Newer security keys require the PIN to be entered even if userVerification is set to discouraged, these keys cannot be used on Safari at all is a PIN has already been set. If the PIN has not already been set, then the security keys works with reduced capabilities, resident keys are not supported on this operation mode.
*** This bug has been marked as a duplicate of bug 191516 ***