More explain:
- FIDO Authenticator will communicate with FIDO Client (WebAuthn in Browser), the protocol is FIDO2, the messages are CBOR syntax
- FIDO Client will communicate with FIDO Server, but not directly. Actually, FIDO Client will communicate with RP, RP can proceed any logic before forward the message to FIDO Server. So FIDO Server should be a stand alone server which talks with RP by APIs.
- When you complete such a system, you can get certified from FIDO, of course, we need to learn about process of FIDO certification.
More information:
We can actually develop our own FIDO Authenticator as a product, it can be a mobile app. I am also trying to make Mobile FIDO Authenticator.
--
You received this message because you are subscribed to the Google Groups "FIDO Dev (fido-dev)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fido-dev+u...@fidoalliance.org.
To view this discussion on the web visit https://groups.google.com/a/fidoalliance.org/d/msgid/fido-dev/97162a37-5b2b-4646-bed3-d9a23110c9c6%40fidoalliance.org.
ATTACHMENT_HINT which describes the method an
authenticator uses to communicate with the FIDO User Device, can be ATTACHMENT_HINT_NETWORK, which means the authenticator app can be connected to the client over internet?
The Nok-Nok, who is FIDO partner, has this concept called Out Of Band(OOB) authentication https://www.noknok.com/oob-fido2-authentication/ which uses QR/Push for the communication between the client and the authenticator app. Is this FIDO certified?