Yes, thank you for clarifying. I didn't fully appreciate that. We expected to be able to enforce attestation on all Android Devices, but seeing a significant number of devices seemingly unable to provide attestation due to the issue I included in the screenshot has forced us to look at including no attestation at least as a fallback option.
Hello, I'd like to provide a small update. We've verified that the affected mobile devices seem to have issues accessing the Attestation Key (please see screenshot). Therefore, as a fallback option for those affected devices we planned to not provide the attestation statement (I understand this is acceptable in the FIDO protocol. For the other Android devices we planned to still use full attestation). In order to use this configuration (without Attestation) I understood that we needed to have the...
Hello, I'd like to provide a small update. We've verified that the affected mobile devices seem to have issues accessing the Attestation Key (please see screenshot). Therefore, as a fallback option for those affected devices we planned to not provide the attestation statement (I understand this is acceptable in the FIDO protocol. For the other Android devices we planned to still use full attestation). In order to use this configuration (without Attestation) I understood that we needed to have the...
Ok thanks. Please do note that the issue doesn't arise consistently even across the same device models. (i.e. some users with those same devices don't have an issue). I guess this would point to issues with the hardware or configuration on the affected mobile devices, but we're not sure how to test this and whether there are known limitations or usage requirements for the StrongKey Android Library.
Hello, I'm trying to implement FIDO Registration and Authentication on my Android mobile-app using the Strongkey Android Client Library along with StrongKey FIDO Server. For most devices (20-30+) this has been working well, but for a small minority of devices there is an error when trying to generate the public-private key pair. Order of events: - Mobile App calls preRegister API (200 OK) - Biometric prompt provided to user - Execute Step 1 from AuthenticatorMakeCredential class successfully - Step...