Class HybridLinkedData
Definition
- Assembly:
- Tizen.Security.WebAuthn.dll
Linked device data.
public class HybridLinkedData- Inheritance
-
objectHybridLinkedData
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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
Constructors
View SourceHybridLinkedData(byte[], byte[], byte[], byte[], byte[], byte[], byte[], byte[])
Initializes a new instance of the HybridLinkedData class.
Declaration
public HybridLinkedData(byte[] contactId, byte[] linkId, byte[] linkSecret, byte[] authenticatorPubkey, byte[] authenticatorName, byte[] signature, byte[] tunnelServerDomain, byte[] identityKey)Parameters
| Type | Name | Description |
|---|---|---|
| byte[] | contactId | CBOR:"1". |
| byte[] | linkId | CBOR:"2". |
| byte[] | linkSecret | CBOR:"3". |
| byte[] | authenticatorPubkey | CBOR:"4". |
| byte[] | authenticatorName | CBOR:"5". |
| byte[] | signature | CBOR:"6". |
| byte[] | tunnelServerDomain | Domain String of tunnel server. |
| byte[] | identityKey | Identity Key created during QR initiated transaction. |
Remarks
More information on the CBOR format can be found in the following specification: https://www.rfc-editor.org/rfc/rfc8949.html
Properties
View SourceAuthenticatorName
Gets the authenticator name (CBOR:"5").
Declaration
public byte[] AuthenticatorName { get; init; }Property Value
| Type | Description |
|---|---|
| byte[] |
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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
AuthenticatorPubkey
Gets the authenticator public key (CBOR:"4").
Declaration
public byte[] AuthenticatorPubkey { get; init; }Property Value
| Type | Description |
|---|---|
| byte[] |
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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
ContactId
Gets the contact id (CBOR:"1").
Declaration
public byte[] ContactId { get; init; }Property Value
| Type | Description |
|---|---|
| byte[] |
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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
IdentityKey
Gets the identity Key created during QR initiated transaction.
Declaration
public byte[] IdentityKey { get; init; }Property Value
| Type | Description |
|---|---|
| byte[] |
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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
LinkId
Gets the link id (CBOR:"3").
Declaration
public byte[] LinkId { get; init; }Property Value
| Type | Description |
|---|---|
| byte[] |
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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
LinkSecret
Gets the link secret (CBOR:"3").
Declaration
public byte[] LinkSecret { get; init; }Property Value
| Type | Description |
|---|---|
| byte[] |
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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
Signature
Gets the signature (CBOR:"6").
Declaration
public byte[] Signature { get; init; }Property Value
| Type | Description |
|---|---|
| byte[] |
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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
TunnelServerDomain
Gets the Domain String of tunnel server.
Declaration
public byte[] TunnelServerDomain { get; init; }Property Value
| Type | Description |
|---|---|
| byte[] |
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 PubkeyCredAttestation or PubkeyCredAssertion. Then the client can store the linked device data and use it in the next call for PubkeyCredCreationOptions or PubkeyCredRequestOptions. 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