ClientData
Stay organized with collections
Save and categorize content based on your preferences.
This class is deprecated.
Please use Fido
APIs instead.
ClientData is sent from the FIDO Client to the relying party, and its hash will be sent
back from the relying party to the Client for verifying the signature on both registration
and authentication responses.
The registration and authentication request messages contain a challenge parameter, which
is defined as the SHA-256 hash of a (UTF8 representation of a) stringified JSON data
structure that the FIDO client has to prepare. The FIDO Client must send the Client Data to
the relying party during the verification phase, where the relying party can regenerate the
challenge parameter (by hashing the client data), which is necessary in order to verify the
signature both on the registration response message and authentication response message.
Client data
Inherited Method Summary
From class java.lang.Object
Object
|
clone()
|
boolean |
|
void |
finalize()
|
final Class<?>
|
getClass()
|
int |
hashCode()
|
final void |
notify()
|
final void |
notifyAll()
|
String
|
toString()
|
final void |
wait(long arg0, int arg1)
|
final void |
wait(long arg0)
|
final void |
wait()
|
Constants
public static final String
KEY_CHALLENGE
Constant Value: "challenge"
public static final String
KEY_CID_PUBKEY
Constant Value: "cid_pubkey"
public static final String
KEY_ORIGIN
public static final String
KEY_TYPE
public static final String
TYPE_FINISH_ENROLLMENT
Constant Value:
"navigator.id.finishEnrollment"
public static final String
TYPE_GET_ASSERTION
Constant Value:
"navigator.id.getAssertion"
Public Methods
public boolean equals (Object other)
public String toJsonString ()
Returns
- The stringified JSON object encoding of this ClientData object.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-31 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-31 UTC."],[[["`ClientData` is deprecated; use the `Fido` APIs instead for FIDO operations."],["It represents data sent from the FIDO Client to the relying party during registration and authentication."],["This data is used to generate a challenge parameter for signature verification."],["`ClientData` includes fields like challenge, origin, and type, with specific constants for enrollment and assertion."],["You can convert a `ClientData` object into a JSON string using the `toJsonString()` method."]]],["`ClientData`, now deprecated in favor of Fido APIs, is utilized in FIDO Client interactions with relying parties. It's a JSON structure sent from the FIDO Client; its SHA-256 hash, known as the challenge parameter, is sent back for signature verification in registration and authentication responses. The client must send this to the party for challenge parameter regeneration, which is required to verify both response message signatures. Key constants include `KEY_CHALLENGE`, `KEY_ORIGIN`, and `KEY_TYPE`. It also has `equals`, `hashCode`, and `toJsonString` methods.\n"]]