Message
Parameter error.
Description
This error code is reported when an input parameter is invalid.
Possible causes
Invalid input parameter.
Solution
Check the input parameter based on the API definition.
Message
User cancels.
Description
This error code is reported when a user cancels an operation.
Possible causes
A user taps the close button during biometric feature verification.
Solution
Initiate the verification again.
Message
No authenticator matching the authenticator policy specified is available.
Description
This error code is reported when there is no authenticator available.
Possible causes
1. checkPolicy: User data exists on the server but does not exist on the client, for example, because the user data has been deleted after FIDO authentication is enabled.
2. processUAFOperation:
Enabling: FIDO authentication has been enabled for a user, but FIDO authentication is to be enabled for the user again.
Authentication: Authentication is performed on a user for whom FIDO authentication is not enabled.
Solution
1. checkPolicy: Re-enable FIDO authentication.
2. processUAFOperation:
Enabling: FIDO authentication does not need to be enabled again. Perform authentication directly.
Authentication: Enable FIDO authentication for the user and then perform authentication. For details, please refer to Use Cases.
Message
A violation of the UAF protocol occurred.
Description
This error code is reported when there is a UAF protocol error.
Possible causes
The packet format or data is incorrect.
Solution
Ensure that the passed packet is correct.
Message
No Facet_ID is registered.
Description
This error code is reported when the facet ID does not match.
Possible causes
The facet ID calculated by the client is different from that configured on the FIDO server. (The facet ID is the signature value in the certificate for packaging your app. Obtain it in advance and then configure it on the FIDO server.)
Solution
Check whether the facet ID configured on the server is correct. The format of a facet ID for HarmonyOS is ohos:app-id:<App signature value>.
The app signature value can be obtained through the getBundleInfoForSelf API. Set BundleFlag to GET_BUNDLE_INFO_WITH_SIGNATURE_INFO, obtain the appId parameter in signatureInfo, and delete the package name prefix and all equal signs (=) at the end of the appId parameter value.
Example:
1. Obtain appId through the getBundleInfoForSelf API.
"com.huawei.hmos.test_6ea5b1b7d51b857cb46d570eb79f7b1c8936a18c5f9bd6b9592ccc75e3406863== "
2. Delete the package name prefix and all equal signs (=) at the end. The left part is the signature value.
"6ea5b1b7d51b857cb4d50e79f7b1c8936a18c5f9bd6b9592ccc75e3406863"
3. Obtain the facet ID by adding a prefix ohos:app-id:.
"ohos:app-id:6ea5b1b7d51b857cb46d570eb79f7b1c8936a18c5f9bd6b9592ccc75e3406863"
Message
The authenticator denies access to the generated request.
Description
This error code is reported when the authenticator denies a request.
Possible causes
The KHAccessToken value obtained after KeyHandle read from the database is decrypted during authentication does not match the dynamically calculated KHAccessToken value.
Solution
Disable the current FIDO fingerprint/facial authentication and enable it again.
Message
The user does not record biometric features or the authentication module is abnormal.
Description
This error code is reported when a user's biometric features are not recorded or the authentication module is abnormal.
Possible causes
The user's biometric features are not recorded.
Solution