Error Codes ​

Following list all the error codes will return in response and what it preset.

１□□□ ​

1000 ​

Which means you are access API without correct informations.
Such as not carry API Key, wrong API Key or access point, or RP / User information is not able to be found on AuthFi (were deleted).
Please check with your informations.

1001 ​

Which means you are block by accessing APIs.
Response with this error when RP reach Trailed expire date or suspend by AuthFi for reasons.
Please contect with AuthFi client services.

1002 ​

It means parameters send from RP server are not acceptable.

The following are possible causes:

• page index too large.
• record size of each page not between 20 to 100.
• user ID is wrong, AuthFi not able to find the user by user ID.
• credential ID from Security Key is wrong, AuthFi not able to find the key by credential ID.
• not sent user id when doing identity verification.

２□□□ ​

2000 ​

User try to do FIDO2 Security Key registration or authentication by Security Key, but RP set user as suspend.

３□□□ ​

3000 ​

When RP is in trail state or just apply for activate, there is max users limitaion.
API will return this code when users count is reached limitation and new user is trying to register Security Key.

3001 ​

Every user can register as much as 10 keys in single RP.
This code will be returned when user is trying to register more than 10 keys.

3100 ​

Server will response this error code when doing PUT /api/v1/webauthn/registration or PUT /api/v1/mobile/registration.
The fido_register_response object send by RP server got wrong format, missing items or parsing error will receive this code.

3200 ​

Server will response this error code when doing PUT /api/v1/webauthn/registration or PUT /api/v1/mobile/registration.
The attestation object content is not suit to FIDO2 specification.

3300 ​

Server will response this error code when doing PUT /api/v1/webauthn/registration or PUT /api/v1/mobile/registration.
The attestation object content in U2F format is not suit to FIDO2 specification.

3400 ​

Server will response this error code when doing PUT /api/v1/webauthn/registration or PUT /api/v1/mobile/registration.
The attestation object content in Packed format is not suit to FIDO2 specification.

3500 ​

Server will response this error code when doing PUT /api/v1/webauthn/registration or PUT /api/v1/mobile/registration.
The attestation object content in TPM format is not suit to FIDO2 specification.

3600 ​

Server will response this error code when doing PUT /api/v1/webauthn/registration or PUT /api/v1/mobile/registration.
The attestation object content in Android SafetyNet format is not suit to FIDO2 specification.

3700 ​

Server will response this error code when doing PUT /api/v1/webauthn/registration or PUT /api/v1/mobile/registration.
The attestation object content in Android Key format is not suit to FIDO2 specification.

3800 ​

Server will response this error code when doing PUT /api/v1/webauthn/registration or PUT /api/v1/mobile/registration.
The attestation object content in Apple format is not suit to FIDO2 specification.

3900 ​

Server will response this error code when doing PUT /api/v1/webauthn/login, PUT /api/v1/webauthn/verification or PUT /api/v1/mobile/verification.

The fido_login_response / fido_auth_response object send by RP server got wrong format, missing items or parsing error will receive this code.

４□□□ ​

4000 ​

Server will response this error code when fido_xxx_response contain clientDataJSON which got wrong format, missing items or parsing error

4100 ​

Server will response this error code when fido_register_response contain response.attestationObject.authData which got wrong format, missing items or parsing error.

And when fido_login_response / fido_auth_rersponse contain response.authenticatorData which got wrong format, missing items or parsing error.

4200 ​

Server will response this error code when fido_xxx_response contains wrong flag informations.

５□□□ ​

5000 ​

Server will response this error code when FIDO register/login/verify request were handle over 30 seconds on AuthFi.

51□□ ​

Server will response these error codes when mobile API request were found some thing wrong.

5100 ​

QRCode token was not found on AuthFi.

5101 ​

QRCode was expired.

5102 ​

QRCode was used.

5103 ​

Not able to find register user name with QRCode token.

5104 ​

User register name on authenticator app is not same as create QRCode user information.

７□□□ ​

7000 ​

Server will response this error code when some data store with wrong value not expected.

８□□□ ​

8000 ​

Server will response this error code when there are some unexpect errors happend.