Antwort auf: Neue Security Key App (1.01) wird von Google nicht unterstützt
Hello,
Small update now that I have more information about what is happening.
There is currently two ways to add the Ledger Security Key application as an authentication method on a Google account:
1/ Adding it as „2-step Verification“ => „Security Key“:
The UX flow is in my opinion broken because you will have to:
* Deny („Skip“) the request for access to security key „make and model“
* Enter the security key name
* Click „Next“
* a pop-up will appear in the background „Something went wrong. Try again.“.
* you will have to dismiss the pop-up requesting you to „Name your key“.
* you won’t see anything being listed in „2-step Verification“ => „Security Key“ but your key will appear in „Passkeys“ section and will be usable as a „2-step Verification“.
2/ Adding it as a „Passkeys“:
The UX flow is in my opinion broken because you will have to:
* Select „Use another device“ in the message saying „A passkey can’t be created on this device“.
* Select „Use a different device“ in the message saying „Create a passkey on a phone or tablet“.
* Select „USB security key“ in the message saying „Create a passkey“.
* Accept the request on the Ledger device.
* Deny („Skip“) the request for access to security key „make and model“
Note that with that second flow Google request for a „Resident Key“ / „Discoverable Crendential“. As mentionned in the warning on the Ledger device, this credential will be lost upon: OS update / Application update / Application uninstallation – reinstallation.
There might be soon some change in the app to disable this feature by default and allow to enable it with a setting for services really requiring it.