Tizen Native API  8.0
__wauthn_hybrid_linked_data Struct Reference

Public Attributes

wauthn_const_buffer_scontact_id
wauthn_const_buffer_slink_id
wauthn_const_buffer_slink_secret
wauthn_const_buffer_sauthenticator_pubkey
wauthn_const_buffer_sauthenticator_name
wauthn_const_buffer_ssignature
wauthn_const_buffer_stunnel_server_domain
wauthn_const_buffer_sidentity_key

Detailed Description

The structure for a linked device data.

Since :
7.0
Remarks:
The linked device data is used for state assisted transaction. From the successful QR initiated transaction, the linked device data might be returned from an authenticator to a webauthn client via wauthn_pubkey_credential_attestation_s or wauthn_pubkey_credential_assertion_s. Then the client can store the linked device data and use it in the next call for wauthn_pubkey_cred_creation_options_s or wauthn_pubkey_cred_request_options_s. Then the stated assisted transaction will start instead of QR initiated transaction.
For more information, find a section with the keyword, "linking map", from the following specification. https://fidoalliance.org/specs/fido-v2.2-rd-20230321/fido-client-to-authenticator-protocol-v2.2-rd-20230321.html
For more information about state assisted transaction, refer to the following. https://fidoalliance.org/specs/fido-v2.2-rd-20230321/fido-client-to-authenticator-protocol-v2.2-rd-20230321.html#hybrid-state-assisted

Member Data Documentation

Identity Key created during QR initiated transaction.