This page lists all the possible errors returned by each of the HYPR platform components.
Code Prefixes
The first two digits in all HYPR error codes indicate the source. Some of the defined ranges of errors are linked here.
The easiest way to find an error is still just to search the page.
Error Prefixes by Component |
||||
15 : Windows | 14 : Mac | 12 : Server | 11 : Android | 10 : iOS |
1520xxx Registration |
1410xxx General |
1201xxx RP Services |
112xxx ASM/Authentication |
10100x-10107x User Agent |
1521xxx Installation Tokens |
1420xxx-1450xxx Reg/Auth |
1202xxx CC Services |
113xxx FIDO Client Errors |
101071-101074 API/Endpoint |
1522xxx Audit Events |
1460xxx HYPRspeed |
1203xxx FIDO2 Services |
114xxx General Errors |
101075-101079 OOB / Push |
1523xxx Log Submission |
1470xxx General |
1204xxx RADIUS Services |
115xxx Action Checks |
104xxx-106xxx FIDO Client |
1530xxx+ Miscellaneous |
1205xxx IdP Services |
116xxx User Agent |
107xxx Authenticators |
|
1206xxx UAF Services |
111xxxx Authenticators |
109xxx Offline Mode |
||
1207xxx IdV Services |
||||
1208xxx CA Services |
HYPR Passwordless for Windows
Code | Error | Cause and Resolution |
Registration Error Codes (1520xxx) |
||
1520001 | Registration failed. We're already waiting for a device to finish registering for this account, please try again in a minute. |
There appears to be an active device registration in progress, or else a previous attempt at registration may not have timed out yet. What to do? Wait 3 minutes then try to register again. This should allow enough time for any pending requests to complete. If the error reoccurs, reboot the computer and try again. |
1520002 | Registration failed. Something went wrong with that request. Check that you are connected to the Internet, then try again. |
The request timed out. Either the registration took longer than the allowed duration, or no response was received from the server or domain controller during one of the steps in the pairing process. What to do?
|
1520003 | Registration failed. Something went wrong with that request. Check that you are connected to the Internet, then try again. |
The request timed out. Either the registration took longer than the allowed duration, or no response was received from the server or domain controller during one of the steps in the pairing process. What to do?
|
1520004 | Registration failed. Something went wrong during device registration. Please try again, or contact support if this keeps happening. |
The workstation client isn't configured properly. The cause might be an invalid URL, incorrect app ID, or a problem with one of the other installation parameters. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. What to do?
|
1520005 | Operation failed. Something went wrong unpairing your device. Please try again. |
Failure to deregister a device. This may occur for several reasons, including a delay on the server. What to do?
|
1520006 | Registration failed. Something went wrong during device registration. Please try again on your company's intranet or over a secure network. Contact Support if this keeps happening. |
The workstation isn't on an authorized network, which prevents the pairing process from generating a certificate with the domain. This issue may also be experienced when proxies are involved in the routing connection. What to do?
|
1520007 | Registration failed. Something went wrong with that request. Failed to write the certificate to the Security Key. |
What to do? Retry updating the certificate on the security key. If you cannot remember the PIN, contact an admin for assistance and a possible factory reset. |
1520008 | Registration failed. Something went wrong with that request. Failed to generate key pair on the Security Key. |
What to do? Retry pairing with the security key. If the issue persists, contact an admin for assistance. |
1520009 | QR Fallback is not available. |
Contact an administrator to verify that QR Fallback is enabled for the RP Application in use. |
Installation Token Error Codes (1521xxx) |
||
1521001 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
There was a problem with the API endpoint protection token exchange request. What to do? Check the HyprOneService log files on the workstation for more information |
1521002 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
The workstation client does not have an API endpoint protection Install Token. What to do? Verify that the Install Token value in the workstation client install parameters is set correctly |
1521003 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
The workstation failed to save an API endpoint protection Exchange Token to replace the Install Token. What to do? Check the HyprOneService log files on the workstation for more information |
1521004 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
The API endpoint protection token exchange request didn't return a valid Exchange Token. What to do? Check the HyprOneService log files on the workstation for more information |
1521005 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
Exception processing the API endpoint protection token exchange response. What to do? Check the HyprOneService log files on the workstation for more information |
1521006 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
The API endpoint protection Exchange Token is invalid. What to do? If the Install Token is still active and valid, the workstation should reacquire an Exchange Token on the next HTTP request. |
1521007 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
Access to the API endpoint protection Exchange Token denied due to a deviceID, rpAppId, or machineId mismatch. What to do? If the Install Token is still active and valid, the workstation should reacquire an Exchange Token on the next HTTP request. |
1521008 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
Invalid or expired API endpoint protection Install Token. What to do? Provide a new Install Token value in the workstation client configuration settings |
1521009 | Registration failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
Access to the API endpoint protection Install Token denied due to a deviceID, rpAppId, or machineId mismatch. What to do? Provide a new Install Token value in the workstation client configuration settings. |
1521010 | Registration failed. The attempt to update the Install Token did not succeed. |
What to do? Provide a new Install Token value in the workstation client configuration settings. It may be necessary to contact an administrator to edit your Workforce Access Client installation parameters and/or reinstall WFA. |
Audit Event Error Codes (1522xxx) |
||
1522001 | Operation failed. Invalid PIN entered. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522002 | Operation failed. Failed to update PIN. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522003 | Operation failed. PIN verification failed. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522004 | Operation failed. Certificate error. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522005 | Operation failed. Failed to enroll Security Key. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522006 | Operation failed. Failed to reset Security Key. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522007 | Operation failed. Management key verification failed. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522008 | Operation failed. Error during install/uninstall. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522009 | Operation failed. Configuration error. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522010 | Operation failed. Error reported by CryptoManager. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522011 | Operation failed. Error during service start/stop. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522012 | Operation failed. Exception during workstation lock. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522013 | Operation failed. Exception during workstation unlock. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522014 | Operation failed. Failed to register workstation. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522015 | Operation failed. Failed to deregister workstation. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522016 | Operation failed. Failed to generate PIN/token. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522017 | Operation failed. Failed to load stored data. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522018 | Operation failed. Failed to register device. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522019 | Operation failed. Failed to deregister device. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522020 | Operation failed. Failed to unenroll Security Key. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522021 | Authentication failed. Failed to authenticate with offline token or recovery PIN. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522022 | Authentication failed. Failed to complete authentication. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522023 | Authentication failed. Failed to cancel authentication. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522024 | Operation failed. User presence failed. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522025 | Status update. Trying to switch to REST API polling due to WebSocket errors. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522026 | Status update. Successfully switched from WebSocket to REST API polling. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522027 | Status update. Trying to switch from REST API polling back to WebSocket. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522028 | Status update. Successfully switched from REST API polling back to WebSocket. |
This error code is used only for log analytics and isn't displayed in the user interface. The 'message' and 'extendedMessage' event fields will contain information about the specific failure. |
1522029 | Status update. Successful workstation logon with Smart Key. |
This error code is used only for log analytics and isn't displayed in the user interface. The event fields will contain information about the specific user and key. isSuccessful will be true. |
1522030 | Status update. Successful workstation unlock with Smart Key. |
This error code is used only for log analytics and isn't displayed in the user interface. The event fields will contain information about the specific user and key. isSuccessful will be true. |
1522031 | Failed to decrypt login certificate. |
The workstation failed to decrypt the login certificate presented by the mobile device. Could be caused by a problem on the mobile device, but workstation problems are more likely. The workstation's private keys may be damaged, or the TPM may have been reset. Also seen after doing P2V migration of a PC with a TPM. Even if the VM has a virtual TPM, the keys stored on the PC's TPM can't be migrated. What to do? Most likely WFA will need to be uninstalled and reinstalled. User will need to re-pair their mobile device(s). |
1522032 | Invalid SSO request. |
The workstation received an invalid Desktop SSO request. What to do? Collect HYPR logs from workstation and escalate to Engineering. |
1522033 | SSO is not supported. |
Either the Desktop SSO feature flag or Endpoint API Security is disabled. What to do? Update the RP App feature flags. If enabling Endpoint API Security for the first time, all users will need to uninstall and re-install Windows WFA. |
1522034 | Internal error during SSO processing. |
An unexpected exception occured during SSO operation. What to do? Collect HYPR logs from workstation and escalate to Engineering. |
1522035 | Last logon/unlock was not performed with HYPR. |
SSO doesn't work if last login/unlock used a security key or password. What to do? Lock the workstation and then unlock using the HYPR Mobile App. |
1522036 | Server rejected SSO. |
The server rejected the SSO attempt. Most likely cause is that too much time has elapsed since login/unlock with the HYPR Mobile App. What to do? Lock the workstation and then unlock using the HYPR Mobile App. Open web browser and attempt SSO as soon as possible after unlocking. |
1522037 | Failed to save device data. |
An error occured while adding a newly registered security key to the paired device database. What to do? This really shouldn't fail. It is likely that something is very wrong with the workstation. Check Windows event logs. |
1522038 | Failed to save offline/recovery PIN data. |
An error occured while saving recovery PINs for a newly registered security key. What to do? This really shouldn't fail. It is likely that something is very wrong with the workstation. Check Windows event logs. |
1522039 | The enrollment service encountered an error that wasn't directly associated with a request. |
Internal error in the Enrollment Service. What to do? Collect HYPR logs from enrollment server and escalate to Engineering. |
1522040 | The enrollment service was unable enroll a user certificate. |
Error during certificate enrollment. What to do? Collect HYPR logs from enrollment server and escalate to Engineering. |
1522041 | The enrollment service was unable revoke a user certificate. |
Error during certificate revocation. What to do? Collect HYPR logs from enrollment server and escalate to Engineering. |
1522042 | Login certificate has expired. |
Contact an administrator to obtain a valid certificate. |
Log Submission Error Codes (1523xxx) |
||
1523001 | Workstation logs submitted. |
Workstation log files were successfully submitted. |
1523002 | Log submission failed. Failed to submit log files. |
This error code is used with failure Audit Events and is intended for log analytics. It isn't displayed in the HyprUnlock user interface. This code is used when a more specific error code isn't available (1523003, 1523004, or 1523005). Consult the message and extendedMessage Event fields for information about the specific failure. |
1523003 | Log submission failed. Failed to collect HYPR log files. |
This error code is used with failure Audit Events and is intended for log analytics. It isn't displayed in the HyprUnlock user interface. This code indicates a failure while collecting HYPR application logs. Consult the message and extendedMessage Event fields for information about the specific failure. |
1523004 | Log submission failed. Failed to collect Windows Event Logs. |
This error code is used with failure Audit Events and is intended for log analytics. It isn't displayed in the HyprUnlock user interface. This code indicates a failure while collecting Windows event logs. Consult the message and extendedMessage Event fields for information about the specific failure. |
1523005 | Log submission failed. Failed to upload log files. |
This error code is used with failure audit events and is intended for log analytics. It isn't displayed in the HyprUnlock user interface. This code indicates a failure while uploading the collected logs to the RP Server. Consult the message and extendedMessage Event fields for information about the specific failure. |
Miscellaneous Errors (1530xxx+) |
||
1530001 | Registration failed. The password you entered is incorrect. |
If the Require User Presence option is turned on in the Control Center, users must type in their current password when pairing a device to validate that they are the employee who is logged into the workstation. When this is incorrectly entered, for example if a rogue or malicious user tries to register on a colleague's unlocked workstation, the pairing process will not complete. What to do? Use the correct password for the user in question. |
1530002 | Operation failed. Too many failed attempts. Your security key PIN is locked. Please contact Support for assistance |
An invalid security key PIN was entered while pairing or logging in. In contrast to HYPR Mobile App users, security key users are required to enter a PIN to accomplish multifactor authentication. What to do?
|
1540001 | Registration failed. You cancelled the registration process so this device was not set up. |
The pairing process was manually canceled. Typically this is a user-chosen action. What to do?
|
1550001 | Registration failed. Something went wrong with that request. Please try again, or contact Support if this keeps happening. |
This error indicates that the workstation client may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. What to do?
|
1550002 | Registration failed. Something went wrong with that request. Please try again, or contact Support if this keeps happening. |
The user isn't authorized to enroll a certificate for the certificate template type. What to do?
|
1550003 | Registration failed. Something went wrong with that request. Please try again, or contact Support if this keeps happening. |
The workstation client isn't configured properly. This is typically not a production issue and is usually only experienced during sandbox or deployment testing by internal or pilot users. This can be caused by Active Directory Certificate Service (AD CS) not working properly. What to do?
|
1550005 | Registration failed. Something went wrong with that request. Your admin will need to verify configuration of the application. Please contact Support. |
The workstation client isn't configured properly. This is typically not a production issue and is usually only experienced during sandbox or deployment testing by internal or pilot users. This can be caused by the value of the public key pinning having been set to an invalid entry. What to do?
|
1550006 | Registration failed. Something went wrong with that request. Your admin will need to verify configuration of the application. Please contact Support. |
This error indicates that the workstation user may not be configured properly. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. This can be caused by the registry values having been set to an invalid entry or having experienced an issue during installation or upgrade. What to do?
|
1550007 | Registration failed. Something went wrong with that request. Your admin will need to verify configuration of the application. Please contact Support. |
Indicates an unknown event. Generally a user may retry the pairing or authentication and proceed successfully but may need further troubleshooting in the case where this issue is caused by a current or change in the enterprise environment. This is typically not a production issue and may be experienced during sandbox or deployment testing by internal or pilot users. What to do?
|
1550008 | Registration failed. Your computer appears to be offline. Please check this computer's network connection and try again. |
The workstation client does not detect an internet connection. What to do?
|
1550009 | Registration failed. The current configuration is not compatible with your domain. Please contact Support for more information. |
The workstation client isn't configured properly. This is typically not a production issue and is usually only experienced during sandbox or deployment testing by internal or pilot users. This can be caused by the Control Center settings being in conflict with the type of end user seeking to pair and use the product. What to do? An admin may need to validate on the Control Center that workstation login is enabled. If it is not enabled, it is likely that a domain user is attempting to enroll and that functionality is not supported when the toggle is disabled. Once this is updated, the end user should be able to seamlessly pair with success. |
1550010 | Registration failed. The current configuration is not compatible with your domain. Please contact support for more information. |
The user is trying to enroll a security key using a local user account. What to do? Your registration policy is not compatible with the method you are using. Try a different method; verify your certificate is current; or contact an admin if the issue persists.
|
1570001 | Operation failed. Something went wrong with that request. Check that you are connected to the Internet, then try again. |
The workstation client does not detect an internet connection. What to do?
|
1570002 | Operation failed. Something went wrong with that request. Please try again, or contact support if this keeps happening. |
The workstation client experienced an issue with the network. What to do?
|
1570003 | Operation failed. Something went wrong with that request. Please reboot your computer and try again, or contact support if this keeps happening. |
The workstation client experienced an unrecoverable error. What to do?
|
1580001 | Reenrollment failed. Failed to store reenrollment certificate. | |
1590001 | Registration failed. We could not reach the server to start the pairing process. Please try again, or contact support if it keeps happening. |
The Control Center API version is less than 4 or not defined and a QR code cannot be generated. What to do? Validate the Server version and update if necessary. |
1590002 | Registration failed. We could not reach the server to start the pairing process. Please try again, or contact support if it keeps happening. |
The Control Center failed to generate a QR code. What to do? Check the Control Center Audit Trail or logs. |
1590003 | Registration failed. We could not reach the server to start the pairing process. Please try again, or contact support if it keeps happening. |
The Control Center believes the workstation client doesn't support QR code functionality What to do? Validate the workstation client version and update if necessary. |
1590004 | Registration failed. We could not reach the server to start the pairing process. Please try again, or contact support if it keeps happening. |
A problem occurred during QR code request and response processing. What to do? Analyze the HyprOneService logs to see if there's a Control Center issue. |
HYPR Passwordless for Mac
Code | Error | Cause and Resolution |
General Error Codes (1410xxx) |
||
1410001 | General failure. Something went wrong with that request. Please try again, or contact Support if this keeps happening. |
This error indicates that the workstation client experienced an general error. What to do? When encountering this error, you will often be presented information for troubleshooting inline with the error. Generally retrying the pairing process will resolve itself. If this does not work, ask the user to reboot their workstation. |
1410002 | General failure. Failed to register the workstation with the server. Obtain a new install token and reinstall the product. |
This error indicates that the install token specified at installation time is not valid for this workstation What to do?
|
Registration / Authentication Error Codes
|
||
1420001 | Registration failed. We're already waiting for a device to finish registering for this account, please try again in a minute. |
This error indicates that the workstation client experienced a network error and a new attempt has been started. What to do?
|
1420002 | Registration failed. Something went wrong with that request. Check that you are connected to the internet, then try again. |
This error indicates that the workstation client experienced a network error during new device pairing. What to do?
|
1420003 | Registration failed. Something went wrong with that request. Check that you are connected to the internet, then try again. |
This error indicates that the request has timed out. This may be the result of a registration taking longer than the allowed duration, or the failure to receive a response from the server during a step in the pairing process. What to do?
|
1420004 | Registration failed. Something went wrong during device registration. Try again, or contact support if this keeps happening. |
This error indicates that device pairing failed. This may happen for a number of reasons with the most common cause due to instability in the network connection at a critical step in the process. What to do?
|
1420005 | Operation failed. Something went wrong unpairing your device. Please try again. |
This error indicates that device unpairing failed. This may happen for a number of reasons with the most common cause due to instability in the network connection at a critical step in the process. What to do?
|
1420006 | Registration failed. Something went wrong during the creation of the authentication certificate. Check that you are connected to the internet, then try again. |
This error indicates that the certificate to be associated with the user could not be generated or installed in the system. This may happen for a number of reasons, including instability in the network connection with the domain controller What to do?
|
1420007 | Registration failed. Something went wrong trying to identify the Certification Authority server. Check that you are connected to the domain, then try again. |
This error indicates that the MacOS LDAP repository didn't have an entry for the Certification Authority for the current user. What to do?
|
1420008 | Registration failed. The Kerberos user name isn't in the expected format. Check that you are connected to the domain, then try again. |
This error indicates that the Kerberos username isn't in the format user@fully.qualified.domain.name. What to do?
|
1420009 | Registration failed. Something went wrong trying to contact the Certification Authority server. Check that you are connected to the Internet, then try again. |
This error indicates a problem trying to contact the Certification Authority server(s) What to do?
|
1420010 | Registration failed. The Certification Authority server refused to issue the certificate. Check that you are authorized to request certificates, then try again. |
This error indicates an authentication problem trying to contact the Certification Authority server(s). What to do?
|
1420011 | Registration failed. The Certification Authority server didn't accept the certificate template. Check the configuration, then try again. |
This error indicates that the certificate template specified in the configuration file is not valid. What to do?
|
1420012 | Registration failed. The Certification Authority server failed to issue the certificate. Check the logs on the server for the underlying reason, then try again. |
This error indicates that the Certification Authority server could not complete the operation. What to do?
|
1420013 | Registration failed. The Certification Authority reported that the clock of the computer is not aligned with the clock on the server. Check the clock, then try again. |
This error indicates that the clock of the computer is not synchronized with the clock of the Certification Authority server. What to do? Verify the date and time settings on the domain controller and adjust the clock on the client computer so that it is aligned with it, then retry the operation. |
1420014 | Registration failed. Failed to import the certificate issued by the Certification Authority server. Check the encryption scheme of the template, then try again. |
This error indicates that the certificate issued by the Certification Authority could not be imported locally. What to do? Verify that the certificate template defined on the domain controller is using the RSA cipher with 2048 bits. |
1420015 | Registration failed. The user's Kerberos ticket has expired. Renew it, then try again. |
This error indicate that the Kerberos ticket of the user has expired. What to do? 1. Renew the ticket by using the `kinit` utility. |
1420016 | QR Fallback Authentication is not enabled. |
What to do? Verify you are logging into the correct application, and try again. If the issue persists, verify with an administrator or Support that the application in question is using QR Fallback. |
1430001 | Registration failed. The password you entered is incorrect. |
This error indicates that the user was unable to authenticate during the pairing process. Users are asked to enter in their password one last time during pairing to ensure that the person pairing is the individual who logged into the workstation. What to do?
|
1430002 | Deregistration failed. The password you entered is incorrect. |
This error indicates that device unpairing failed. This may happen for a number of reasons with the most common cause due to instability in the network connection at a critical step in the process. What to do?
|
1430003 | Unable to complete certificate binding. |
This error indicates that the user most likely didn't enter her password when requested by MacOS when binding the user to the certificate. Ensure to enter the user password when requested by the system dialog with the yellow smartcard chip icon. |
1440001 | Registration failed. You cancelled the registration process so this device was not set up. |
This error indicates that the user canceled the pairing process when asked to confirm their authorization with their current password. What to do?
|
1450001 | General Authentication Error. |
This error indicates that the workstation client experienced an error while unlocking the user. What to do? Wait 2 minutes and then proceed to authenticate again. If this does not resolve the issue, try a reboot and see if the issue persists. |
HYPRspeed (Desktop SSO) Error Codes (1460xxx) |
||
1460001 | Desktop SSO failed. Unable to authenticate on web site. |
An attempt to login on a web site using the same session used on the workstation (Desktop SSO) was denied by the server What to do? 1. Ensure that you authenticated on the workstation using HYPR 2. If the error persist, contact support |
1460002 | Desktop SSO failed. Feature has not been enabled. |
Desktop SSO isn't turned on for this HYPR server. |
1460003 | Desktop SSO failed. Secure Endpoint has not been enabled. | Secure Endpoint Protection is not enabled on the workstation. |
1460004 | Desktop SSO failed. SSO request is not valid. | The arguments of the request don't match the settings of the workstation. |
1460005 | Desktop SSO failed. You must be authenticated with HYPR in order to use Desktop SSO. | An attempt to login on a web site using the same session used on the workstation (Desktop SSO) failed because there is no active session. 1. Lock the workstation and unlock it using HYPR. 2. If the error persists, contact Support. |
1460006 | Failed to sign SSO challenge. |
The crypto operations required by DesktopSSO could not be performed. Contact Support. |
General Error Codes (1470xxx) |
||
1470001 | Operation failed. Something went wrong with that request. Check that you are connected to the Internet, then try again. |
This error indicates that the workstation client experienced an issue with the network. What to do?
|
1470002 | Operation failed. Something went wrong with that request. Please try again, or contact Support if this keeps happening. |
This error indicates that the workstation client experienced an unrecoverable error. What to do?
|
1470003 | Unable to retrieve the public key. | This error indicates that the public key for HYPR is not available in the Keychain. Check Keychain for com.hypr.employeeaccess and see if public key is available. |
1470004 | Unable to retrieve the private key. | This error indicates that the public key for HYPR is not available in the Keychain. Check Keychain for com.hypr.employeeaccess and see if public key is available. |
HYPR Cloud / HYPR On Prem (Server)
Please note that these errors may be displayed in the HYPR Mobile App as well; this indicates that the root cause of the problem is the server-related error.
Code | Error | Cause and Resolution |
RP Service Error Codes (1201xxx) |
||
1201001 | Usually the result of the server under load/contention. The authorization request has been interrupted for the ClientRegistrationComplete request. |
What to do? 1. Check the logs for any indications of server failures. 2. The user can retry after 1 minute. |
1201002 | The user already has a pending registration request. |
What to do? Device pairing may still be in progress. Try again in a couple of minutes, or contact support if the issue persists. |
1201003 | This error indicates that the push provider is not configured for this application. |
What to do? Configure a push provider in the Control Center. |
1201004 | The user has a pending request with the same ID. |
What to do? Wait for session to timeout over 1 minute or so. Re-try: a Registration may still be in progress. Try again in a couple of minutes, or contact support if the issue persists. |
1201005 | The session provided is not valid. |
What to do? Wait 1 minute and try again, or contact support if the issue persists. |
1201006 | The client or device software version is incompatible with the server. |
What to do? Please contact support to confirm that you have the correct software version. |
1201007 | The registration request is invalid. |
What to do? Try again after 1 minute or contact support if the issue persists. |
1201008 | This error indicates that the client cancelled registration and the current operation cannot proceed. |
What to do? Wait 1 minute and try again. |
1201009 | An authentication or registration attempt already exists. |
What to do? Please wait 1 minute and try again. If the issue continues, check the audit log within the Control Center. |
1201010 | This error indicates that an invalid image was uploaded. |
What to do? The max file size is 256kb. Please try again with a smaller image. |
1201011 | The session is not valid for this request because it has timed out. It took too long to complete the action. |
What to do? The user should restart the app and try to authenticate again. |
1201012 | The current machine does not exist in the user's session. |
What to do? Wait 1 minute for the session to expire, and then try again. |
1201013 | The request is invalid for the user's session. OR No authentication payload found. |
What to do? Wait 1 minute for the session to expire, and then try again. |
1201014 | The user's session cannot be found. |
What to do? Wait 1 minute for the session to expire, and then try again. |
1201015 | This error indicates that there was a problem registering the user for push notifications. |
What to do? The administrator should check that the API token is valid in their push notification settings. |
1201016 | The user's session cannot be found. |
What to do? Wait 1 minute for the session to expire, and then try again. |
1201017 | This indicates that there was an internal error creating an SSL client. |
What to do? Wait 1 minute and try again. If the issue persists, contact HYPR support. |
1201018 | Registration failed due to a timeout. |
What to do? The user can wait 1 minute and try again. |
1201019 | There was an issue communicating with the client. |
What to do? Wait 1 minute and try again. |
1201020 | The sessionId provided in the request is invalid. |
What to do? Wait 1 minute for the session to expire, and then try again. |
1201021 | There was a problem updating the status for the machine. |
What to do? Check that the machine is paired and try again. |
1201022 | The authentication failed due to the presence of another pending authentication request. |
This usually happens when the user canceled or failed the first authentication attempt and initiated the second one right away. HYPR by default allows only one user authentication per minute so that the server will cancel the second authentication attempt. What to do?
|
1201023 | The operation failed due to invalid request parameters. |
What to do? Wait for 1 minute and try again. Contact Support if the issue persists. |
1201026 | An authentication or registration attempt already exists. |
What to do? Please wait 1 minute and try again. If the issue continues, check the audit log within the Control Center. |
1201027 | There's a pending unpairing request for this device. |
What to do? Ensure that another de registration attempt is not in progress. Wait for 1 minute and re-try. |
1201029 | Invalid Workstation Configuration. |
What to do? Verify that the Workstation settings for this application are correct. |
1201030 | Issue occurred with Workstation Lock. |
What to do? Wait for 1 minute and try again. Contact support if the issue persists. |
1201031 | Registration canceled by client setup. |
What to do? Wait 1 minute and try again. |
1201032 | The machined display name for the provided rpAppId is not found. |
What to do? Verify that the appId is correct and that it currently exists and try again. |
1201033 | Invalid username provided. |
What to do? Verify that the username is correct and that it currently exists and try again. |
1201034 | There was a problem deleting the user. |
What to do? Wait for 1 minute and try again. Contact support if the issue persists. |
1201035 | The machined display name for the provided rpAppId is not found. |
What to do? Verify that the appId is correct and that it currently exists and try again. |
1201036 | The display name for this machine could not be found. |
What to do? Verify that the display name is correct and that it currently exists and try again. |
1201037 | There was an issue with Workstation Web Login. |
What to do? Wait for 1 minute and try again. Contact support if the issue persists. |
1201038 | The information collected during the registration process cannot be saved. |
What to do? Wait for 1 minute and try again. Contact support if the issue persists. |
1201039 | During the registration process, a caller sent a request that is incompatible with the current state of the registration. |
What to do? Wait 1 minute for the session to expire, and then try again. |
1201040 | There was a problem retrieving FIDO2 OOB Request. |
What to do? Wait 1 minute for the session to expire, and then try again. |
1201041 | Cannot find a feature with the given name. |
What to do? Verify that the flag name is correct and try again. |
1201042 | This feature flag is deprecated. |
What to do? Cannot update a flag that is deprecated. Vertify the flag name is correct. |
1201043 | Cannot find a Magic Link entry for the token given. |
What to do? Verify that the token is correct and try again. |
1201044 | Magic Link is not valid for the token given. |
What to do? Verify that the token is correct and try again. |
1201045 | This feature is not currently enabled. |
What to do? Please enable this feature flag and try again. |
1201046 | The Endpoint API token is invalid or expired. |
What to do? Verify that the token is correct and try again. |
1201047 | No registration record for this device and rpApplication. |
What to do? Verify that the token is correct and try again. |
1201048 | The Token was not found. |
What to do? Verify that the token is correct and try again. |
1201049 | The SSO challenge is not found in the cache. |
What to do? Try again. Contact HYPR support if the issue persists. |
1201050 | Signature validation failed. |
What to do? Try again. Contact HYPR support if the issue persists. |
1201051 | The public key was not found in the certificate. |
What to do? Try again. Contact HYPR support if the issue persists. |
1201052 | The deviceID, rpAppId, or namedUser is null. |
What to do? Try again. Contact HYPR support if the issue persists. |
1201053 | Resetting the Magic Link, as it was clicked and no devices were registered. |
What to do? Wait 1 minute and try again, or acquire a new Magic Link. |
1201054 | Error locating the original request to enroll certificate for this Workstation. |
What to do?
|
1201055 | Failed to submit certificate enrollment request for the Workstation. |
What to do?
|
1201056 | Failed to submit certificate enrollment request for the Workstation. |
What to do?
|
1201057 | Browser (OOB) authentication has been cancelled. |
What to do? Mobile device cancelled the auth in progress. This is usually initiated by the user. |
1201058 | Device failed to de-register Browser (OOB). |
What to do? Re-try from device or contact support to delete from ControlCenter admin console. |
1201059 | Device failed to de-register Workstation. |
What to do? Re-try from device or contact support to delete from ControlCenter admin console. |
1201060 | Failed to unlock Workstation. |
What to do? Wait for a minute and try again. Contact support if the issue persists. |
1201061 | Could not find a registered web account. |
What to do? The device isn't registered to a web (OOB) account. Register via Device Manager. |
1201062 | FIDO session is expired. |
What to do? Lock/Unlock the Workstation to refresh the FIDO session. |
1201063 | The logged in user ended up in an unexpected invalid state. |
What to do? Please try logging out and re-logging in and if that does not resolve the issue, please try re-registering the user. |
1201064 | Desktop SSO workstation client could not sign the challenge. |
What to do? Retry the operation and/or check the workstation logs. |
1201065 | There was a problem with generation of UAF record checksum. |
What to do? Contact support. |
1201066 | There was a problem with generation of device record checksum. |
What to do? Contact support. |
1201067 | There was a problem with validation of UAF record checksum. |
What to do? Contact support. |
1201068 | There was a problem with validation of device record checksum. |
What to do? Contact support. |
1201069 | Attempt validating checksum with no extension defined. |
What to do? Contact support. |
1201070 | The crypto provider was requested to use a hash algorithm that is unsupported. |
What to do? Change the hash algorithm to a supported value. |
1201071 | The crypto provider requested is unsupported. |
What to do? Change the crypto provider to a supported value. |
1201072 | The crypto provider was requested to use a key id that is unsupported. |
What to do? Change the key id to a supported value. |
1201073 | The crypto provider was requested to use a hash algorithm that is unsupported. |
What to do? Change the hash algorithm to a supported value. |
1201074 | The batch database update failed. |
What to do? Please contact support. |
1201075 | Could not verify the registered web account against the registrations on the device. |
What to do? Ensure that the web account is paired to the mobile used to unlock the Workstation. |
1201076 | Could not verify the encrypted column. |
What to do? Ensure that the encryption key hasn't been changed. |
1201077 | Multiple web accounts registered to the device. |
What to do? This scenario is not supported. Try a different log in method or ensure that only one user account is registered to the HYPR web Application. |
1201078 | Error locating the certificate revocation request. |
What to do? The certificate may have been revoked already. Confirm its revocation in the server logs. |
1201079 | Error reported by the CA service while signing or revoking a certificate. |
What to do? Check the Control Center error logs and the CA administration console. |
1201080 | Signed data are wrong. |
What to do? Please verify if data are signed properly. |
1201081 | Domain root certificate issue. |
What to do? Please verify the provided certificate. It probably already exists in the db. |
1201082 | Domain root certificate issue. |
What to do? Please verify the provided certificate. |
1201083 | Unauthorized workstation lock. |
What to do? Register the device with the workstation. |
1201084 | Authentication attempt has been blocked by brute force detection in keycloak |
What to do? Please wait a minute and try again. If the issue continues, check the audit log within the Control Center. |
1201085 | Possible brute force attempt detected for user latest failed authentication attempt. |
What to do? Please wait a minute and try again. If the issue continues, check the audit log within the Control Center. |
1201086 |
Risk policy (Adapt) evaluation request failed. May accompany a 403 status code. |
This is a security measure to protect your information. If you believe this is an error or you need assistance, then please contact your administrator. What to do? Check connectivity and configuration in CC. |
1201087 | Risk policy (Adapt) has incorrect configurations. |
What to do? Check connectivity and configuration in CC. |
1201088 | Risk policy (Adapt) evaluation has timed out, try again or reconfigure timeout. |
What to do? Check connectivity and configuration in CC. |
1201089 | Risk policy (Adapt) could not be found |
What to do? Check that policyId is correct and try again. |
1201090 | This feature is currently enabled. |
What to do? Please disable this feature flag and try again. |
CC Service Error Codes (1202xxx) |
||
1202001 | This error indicates a generic server issue. |
What to do? Check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202002 | The user does not have any registered devices for the rpAppId. |
What to do? The user should register a device under the requested application. |
1202003 | The request provided invalid data. |
What to do? Try again. Contact HYPR Support if the issue persists. |
1202004 | The provided access token is invalid. |
What to do? Check the access token supplied in the API request. Re-issue a new access token if needed. |
1202005 | This error indicates that the current license is invalid. |
What to do? Check that the license server is reachable and that a valid license has been applied. |
1202006 | Could not find corresponding pin request from client. |
What to do? Try again. Contact HYPR support if the issue persists. |
1202007 | This indicates that an internal service was not reachable. |
What to do? Check that all services are available and running. |
1202008 | This indicates that the license server is not reachable. |
What to do? Check that the license server is available and running. |
1202009 | An invalid application was used. |
What to do? Check that you have created and set up the application in the Control Center. |
1202010 | The FIDO operation failed due to invalid request data. |
What to do? Try again. Contact support if the issue persists. |
1202011 | The workstation session was not found. |
What to do? Wait for session to timeout over 1 minute or so. Re-try |
1202012 | There was an issue with the websocket connection between the server and workstation. |
What to do? Use Offline Mode or restart the computer and try again. |
1202013 | Authorization between the device and workstation failed. |
What to do? Check that the workstation can reach the Active Directory server, and that the workstation HYPR service is running. Otherwise restart the computer, or use Offline Mode. |
1202014 | The Control Center failed to reach the UAF server. |
What to do? Check that the UAF server is running and reachable. |
1202015 | This error indicates an issue with extensions. |
What to do? Try again or contact support if the issue persists. |
1202016 | The workstation does not appear to be registered. |
What to do? Try again or contact support if the issue persists. |
1202017 | This error indicates a problem with the SSL certificate. |
What to do? Ensure that the certificate is in the correct format and try again. |
1202018 | This error indicates an issue creating a session. |
What to do? Code problem. Check logs for session creation problem. |
1202019 | Ensure that the Action ID (Authentication Policy) is setup in Control Center for the Application. Action ID does not match Client Action ID. |
What to do? Check Control Center for policy setup. |
1202020 | The application setup is incomplete or incorrect. |
What to do? Please ensure that the action ID is configured for RPAppId in the Control Center. |
1202021 | Invalid data request object was received. |
What to do? Please ensure configurations are valid and try again. |
1202022 | Could not find the device requested. |
What to do? Please make sure your device has been paired with the computer. |
1202023 | There was a problem sending push notifications to the user. |
What to do? Please make your device is paired, and push notifications are enabled. |
1202024 |
Error sending login recovery e-mail. User could not be found.
|
What to do? Please ensure your device is registered to login with this website. |
1202025 | The operation on the workstation has timed out. |
What to do? Wait 1 minute and try again. |
1202026 | There was an issue with push provider configuration. |
What to do? Please make sure push notifications are enabled, and your device has been paired with the device manager. |
1202027 | There was an issue with push provider configuration. Either push is disabled or the url is null. |
What to do? Check Control Center logs and contact HYPR Support for assistance. |
1202028 | There was an issue with the challenge used in the FIDO operation. |
What to do? Wait 1 minute and try again, check the audit log within the Control Center. |
1202029 | There was an error in the adapter processing. The adapter URL is not correct. |
What to do? Ensure that the adapter URL is valid and reachable from the server. |
1202030 | There was an error in the adapter processing. This was the resulting response bean from the adapter. |
What to do? Check server logs for extension problems. |
1202031 | There is an issue with the extension JAR package. |
What to do? Please ensure the identity provider extension follows the rules, and try again. |
1202032 | Failed to stop or unload the extension. |
What to do? Please ensure the identity provider extension follows the rules, and try again. |
1202033 | Failed to load extensions. Path: |
What to do? Check server logs for failure details. Usually, it's a filesystem permissions issue. |
1202034 | There was a problem with your identity provider extensions. |
What to do? Check server logs for the specific extension problem. A runtime exception for a third-party product is not known to the server. |
1202035 | Failed to initialize server cache. |
What to do? Server is not able to load applications from server and/or cache them. Check server logs for root cause. |
1202036 | Mobile device record not found on the server. |
What to do? Might indicate a registration problem or perhaps the mobile device has been unpaired by the user. |
1202037 | HMAC of the message payload is invalid. |
What to do? In some APIs the device supplies an HMAC of the message. This allows us to confirm the integrity of the message. Try re-registering the mobile device. |
1202038 | Device key in the request is invalid. |
What to do? Registration data could be corrupt. RP app or the server might not be the one we registered with. |
1202039 | When revealing recovery PINs, no existing device registrations found. The search was by machineId, rpAppId, deviceId and machineUser. |
What to do? Do a registration if it is a new device or an authentication other wise. Make sure recovery PINs are enabled in the control center. |
1202040 | MachineName not found. No matching MachineId found for machineName. |
What to do? For the retrieve recovery PINs API, the machineName is the diplayed name. It is used to find the machineId to query the existing device registrations. The resolution is to provide an existing machineName. |
1202041 | A key agreement handshake component was missing when validating the Recovery PINs authentication. |
Restart registration or authentication. If the issue persists, contact your support. |
1202042 | Validation of publicKeyAgreementAuth or recoveryPinsAuth failed. |
What to do? There is a mismatch on the keys used to sign the uath. This is likely a legitimately invalid case and someone is trying to send the wrong keys. |
1202043 | Invalid recovery PINs, due to invalid recoveryPinsAuth. |
What to do? Try registration or authentication with a new device. |
1202044 | Unable to lookup null/empty sessionId. |
What to do? Wait 1 minute and try again; check the audit log within the Control Center. |
1202045 | The requested push message is not available. |
What to do? The device is requesting a Firebase message from the server via poll, but it is not available. This may happen when the message is expired, the HMAC is incorrect, or no payload is sent. |
1202046 | Invite to onboarding user was not able to be sent. |
What to do? Wait 1 minute and try again; check the audit log within the Control Center. |
1202047 | Onboarding was not able to communicate with the SSO Provider. |
What to do? Wait 1 minute and try again; check the audit log within the Control Center. |
1202048 |
Your username doesn't exist in your IDP, but it must exist for initial integration. Please refer to the documentation for guidance.
|
What to do? Make sure the username is typed correctly and that is exists on your network; then try again. |
1202049 |
The username provided doesn't exist in the SSO provider.
|
What to do? Make sure the username is typed correctly and that is exists in your SSO system; then try again. |
1202050 |
The API token provided seems to be invalid for your IdP.
|
What to do? Verify your API Token is still valid, then try agian. |
1202051 |
Error sending invitation e-mail. This functionality is only available on HYPR Cloud platforms.
|
What to do? Email Onboarding Service is only available on HYPR Cloud. |
1202052 |
It looks like this person has already been invited.
|
What to do? The username for this RP App has already been invited and a Magic Link has already been generated for them. Try another username or use Resend Invitation to send a new invitation to this user. |
1202053 |
The API token provided seems to be expired for your IdP.
|
What to do? Verify the API Token is still valid for your IdP, then try again. |
1202054 |
The application name provided is invalid for your IdP.
|
What to do? Please check the RP Application configuration in Control Center Advanced Mode. |
1202055 |
We can't seem to be able to create an OIDC application in your IdP. Please refer to the documentation for guidance.
|
What to do? Verify your IdP OIDC Settings, then try again. |
1202056 | Keycloak Realm creation failed. |
What to do? Please retry the integration. |
1202057 | Keycloak Realm Token failed to be retrieved. |
What to do? Please retry the integration. |
1202058 | Failed to retrieve Keycloak SAML metadata. |
What to do? Please retry the integration. |
1202059 | Failed to CREATE Auth Flow. |
What to do? Please retry the integration. |
1202060 | Failed to ADD Authentication Flow to Realm. |
What to do? Please retry the integration. |
1202061 | Failed to GET Authentication Flow. |
What to do? Please retry the integration. |
1202062 | Failed to create the Client scope. |
What to do? Please retry the integration. |
1202063 | Keycloak failed to create the OIDC client. |
What to do? Please retry the integration. |
1202064 | Keycloak failed to create the SAML client. |
What to do? Please retry the integration. |
1202065 | Failed to get the Keycloak execution flow. |
What to do? Please retry the integration. |
1202066 | Failed to configure the Keycloak Authenticator. |
What to do? Please retry the integration. |
1202067 | Failed to enable the Keycloak Authenticator. |
What to do? Please retry the integration. |
1202068 | Failed to get the Keycloak Secret. |
What to do? Please retry the integration. |
1202069 | Failed to delete the Keycloak Realm. |
What to do? Please retry the integration. |
1202070 | Failed to create user in the Realm. |
What to do? Please retry the integration. |
1202071 | Failed to get a user from the Realm. |
What to do? Please retry the integration. |
1202072 | Failed to delete a user from the Realm. |
What to do? Please retry the integration. |
1202075 | Invalid recovery PIN update. |
What to do? Please retry the integration. |
1202076 | Failed to configure CC Extension. |
What to do? Please retry the integration. |
1202300 | Failed to configure CC Extension. |
What to do? Please retry the integration. |
1202301 | Failed to configure CC Extension for Azure. |
What to do? Please retry the integration. |
1202302 | Failed to get CC CSRF Token for integration operations. |
What to do? Please retry the integration. |
1202303 | Failed to generate API Tokens for integration operations. |
What to do? Please retry the integration. |
1202500 | Failed to complete the AzureAPI call. OR Status code 429 (TOO_MANY_REQUESTS) when API throttling thresholds are exceeded. |
What to do? Please retry the integration. OR You are using too many API calls to gather your data. Try using the Bulk Export API to collect masses of data. |
1202501 | This indicates that the license validation has failed. |
What to do? The administrator should check that the correct license has been provided. |
1202502 | Unable to delete the application. |
What to do? Check that you have created and set up the application in the Control Center. |
1202503 | Unable to create or update application. |
What to do? Check that you don't have created the same application in the Control Center. |
1202504 | Could not connect to Data Lake API. |
What to do? Check the correct values are present in the DataLakeConfig, and IAM User creds are in Vault. |
1202505 | Certificate verification error. |
What to do? Verify your certificate. Check if certification path can be built and all certificates in the chain are valid and there are no CRL checks that are failed. Check network connection to distribution point of CRL. |
1202506 | Could not read default app name from server configuration. Check Vault setup. |
What to do? Check Vault setup. |
1202507 | This error indicates a Redis script issue. |
What to do? Check the Redis script. |
1202508 | This error indicates a redis queue issue. |
What to do? Check the Redis script. |
1202509 | Invalid property configuration. |
What to do? Make sure to add JavaDoc to newly introduced config property. |
1202510 | Invalid algorithm code problem. |
What to do? Check hash algorithm code in DesktopSSO configuration, CBOR algorithm, or IANA algorithm in FIDO2 configuration. |
1202511 | RO is missing in some service. |
What to do? Check service definition. |
1202512 | There was an error during negotiating version between clientVersion, deviceVersion, serverVersion. |
What to do? Check proper versions. |
1202513 | Access token is invalid. |
What to do? Check yout token. |
1202514 | Invalid Push Notification Payload Problem. |
What to do? Check the payload. |
1202515 | User e-mail invalid. |
What to do? Provide valid e-mail. |
1202516 | QR code is invalid. |
What to do? Check the QR code validity or wait for a new one to generate. |
1202517 | The device registration could not be processed successfully. |
What to do? If the issue persists, contact HYPR Support. |
1202519 | There was a state transition problem during device authentication request processing. |
What to do? If the issue persists, contact HYPR Support. |
1202520 | This error indicates a generic server issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202521 | This error indicates a configuration issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202522 | This error indicates a vault configuration issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202523 | This error indicates a Redis configuration issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202524 | ControlCenter.log doesn't exist. |
What to do? Check the log directory. |
1202525 | Failed to modify Feature Flag. Lack of Authority. |
What to do? Contact HYPR Support for assistance. |
1202526 | Feature Flag toggle for the rpApp is forbidden. |
What to do? Don't try to toggle the Feature Flag in question. |
1202527 | Invalid session record. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202528 | This error indicates a cache configuration issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202529 | This error indicates a cache configuration issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202530 | This error indicates a websocket message issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202531 | This error indicates a websocket message issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202532 | This error indicates a websocket message issue. |
What to do? The administrator should check the server logs for indicators of an unhandled error. If the issue persists, contact HYPR Support. |
1202601 |
Authentication has been blocked due to failure limit being reached by user. May accompany a 403 status code. |
What to do? Wait the specified duration until your account is unblocked; then try again. If the issue persists, contact your support with this issue. |
FIDO2 Service Error Codes (1203xxx) |
||
1203001 | Failed to execute FIDO2 request. |
What to do? Wait 1 minute and try again, check the audit log within the Control Center. |
1203002 | Could not validate extension response. |
What to do? Wait 1 minute and try again, check the audit log within the Control Center. |
1203003 | FIDO2 settings are null. |
What to do? Please make sure FIDO2 settings are configured. |
1203004 | FIDO2 settings model is null. |
What to do? Please make sure the settings model is populated and try again. |
1203005 | There is a problem with the METADATA. |
What to do? Wait 1 minute and try again, check the audit log within the Control Center. |
1203006 | The FIDO2 server is unreachable. |
What to do? Check Control Center logs and contact HYPR Support for assistance. |
1203007 | FIDO2 settings are not currently enabled. |
What to do? Enable FIDO2 and try again. |
1203008 | Missing FIDO metadata. aaguid={aaguid} |
What to do? Check Control Center logs and contact HYPR Support for assistance. |
1203009 | FIDO2 authenticator certificate, specified in the metadata, is about to expire. |
What to do? Update authenticator metadata with the latest copy from the FIDO MetaData Service. |
1203010 | WebAuthn operation cannot be completed because initial session is not found. |
What to do? Try again. If problem persists, contact HYPR Support to increase the FIDO2 session timeout. |
1203011 | WebAuthn operation cannot be completed due to DPK problem. |
What to do? Try again. If the problem persists, contact HYPR Support for investigation. |
1203012 | WebAuthn operation cannot be completed due to FIDO2 policy. |
What to do? Try a different FIDO2 authenticator, or call an administrator for details. |
1203013 | Origin returned by client/browser does not match RP origin. |
What to do? Call administrator to verify RP origin in FIDO2 settings is set properly. |
|
||
1203034 | There was a problem with your identity provider extensions. |
What to do? Check server logs for the specific extension problem. A runtime exception for a third-party product is not known to the server. |
RADIUS Service Error Codes (1204xxx) |
||
1204010 |
RADIUS server ID was not found. |
What to do? Choose an existing radiusServerId. |
1204011 | RADIUS server cannot be created. |
What to do? Check RADIUS server constraints. |
1204012 | RADIUS server cannot be created. |
What to do? Check RADIUS server data. |
1204013 | RADIUS server cannot be updated. |
What to do? Check RADIUS server constraints. |
1204014 | RADIUS server cannot be updated. |
What to do? Check RADIUS server data. |
1204015 | RADIUS server cannot be deleted. |
What to do? Check RADIUS server data and constraints. |
1204016 | RADIUS configuration ID was not found. |
What to do? Choose RADIUS config ID which exists. |
1204017 | RADIUS configuration cannot be created. |
What to do? Check RADIUS config constraints. |
1204018 | RADIUS configuration cannot be created. |
What to do? Check RADIUS config data. |
1204019 | RADIUS configuration cannot be updated. |
What to do? Check RADIUS config constraints. |
1204020 | RADIUS configuration cannot be updated. |
What to do? Check RADIUS config data. |
1204021 | RADIUS configuration cannot be deleted. |
What to do? Check RADIUS config data and constraints. |
1204022 | RADIUS client ID was not found. |
What to do? Choose RADIUS client ID which exists. |
1204023 | RADIUS client cannot be created. |
What to do? Check RADIUS client constraints. |
1204024 | RADIUS client cannot be created. |
What to do? Check RADIUS client data. |
1204025 | RADIUS client cannot be updated. |
What to do? Check RADIUS client constraints. |
1204026 | RADIUS client cannot be updated. |
What to do? Check RADIUS client data. |
1204027 | RADIUS client cannot be deleted. |
What to do? Check RADIUS client data and constraints. |
1204028 | RADIUS server has not updated Control Center with its status yet. |
What to do? Ensure RADIUS server is configured properly and try again later. |
1204029 | RADIUS server name already exists. |
What to do? Choose a different server name. |
1204030 | RADIUS config name already exists. |
What to do? Choose a different config name. |
1204031 | RADIUS client name already exists. |
What to do? Choose a different client name. |
1204032 | RADIUS integration name already exists. |
What to do? Use existing RADIUS integration. |
1204033 | RADIUS integration cannot be created. |
What to do? Check RADIUS integration constraints. |
1204034 | RADIUS integration cannot be created. |
What to do? Check RADIUS integration data. |
1204035 | RADIUS integration cannot be deleted. |
What to do? Check RADIUS integration data and constraints. |
1204036 | RADIUS integration ID cannot be found. |
What to do? Choose an existing RADIUS integration ID. |
1204037 | The RP app value provided for the RADIUS integration is invalid. |
What to do? For a standalone RADIUS integration, the RP app value must be unique. To leverage an existing integration, the RP app must exist and be configured properly. |
1204038 | The RP app ID for the RADIUS server was not found. |
What to do? Ensure the RP app ID being associated with the RADIUS server exists. |
1204039 | The RP app ID for the RADIUS config was not found. |
What to do? Ensure the RP app ID being associated with the RADIUS config exists. |
1204040 | RADIUS clients cannot be created. |
What to do? Check RADIUS client constraints. |
1204041 | RADIUS clients cannot be created. |
What to do? Check RADIUS client data. |
1204042 | RADIUS onboarding cannot create integration. |
What to do? Check integrations setup data. |
1204043 | RADIUS onboarding cannot create RADIUS server. |
What to do? Check server setup data. |
1204044 | RADIUS onboarding cannot create RADIUS configuration. |
What to do? Check configuration setup data. |
1204045 | RADIUS onboarding cannot create RADIUS clients. |
What to do? Check client setup data. |
1204046 | RADIUS onboarding cannot be created. |
What to do? Check onboarding setup data. |
IdP Service Error Codes (1205xxx) |
||
1205001 | IdP user does not exist. |
What to do? Please verify the IdP user exists. |
1205002 | Invalid API key. |
What to do? Please contact Support. |
1205002 | API key has expired. |
What to do? Please contact Support. |
1205003 | Invalid RP App name. |
What to do? Please contact Support. |
1205004 | Unable to create OIDC. |
What to do? Please contact Support. |
1205005 | Unable to create OIDC application. |
What to do? Please contact Support. |
1205006 | Error creating OIDC routing rule. |
What to do? Please contact Support. |
1205007 | Error creating OIDC policy rule. |
What to do? Please contact Support. |
1205008 | Error configuring OIDC. |
What to do? Please contact Support. |
1205009 | Error configuring extension. |
What to do? Please contact Support. |
1205010 | Error configuring extention association. |
What to do? Please contact Support. |
1205011 | Error configuring device config. |
What to do? Please contact Support. |
1205012 | Invalid SSO URL. |
What to do? Please verify the URL is correct. |
1205013 | Duplicate RP AppID. |
What to do? Please verify there are no other RP applications with the same name. |
1205014 | SSO profile is in use. |
What to do? Please contact Support. |
1205015 | IDP configuration not found. |
What to do? Please contact Support. |
1205018 | Bad Request found when trying to activate routing rules. |
What to do? Please contact Support. |
1205019 | Bad Request found when trying to deactivate routing rules. |
What to do? Please contact Support. |
1205025 | Failed to validate IdP integrations. |
What to do? Please retry the integration. |
UAF Service Error Codes (1206xxx) |
||
1206001 | UAF Code OK (1200). |
What to do? Please contact Support for any questions. |
1206002 | UAF Code Bad request (1400). |
What to do? Please contact Support. |
1206003 | UAF Unknown AAID (1480). |
What to do? Please contact Support. |
1206004 | Unknown KeyId (1481). |
What to do? Please contact Support for any questions. |
1206005 | UAF Code OK (1491). |
What to do? Please contact Support for any questions. |
1206006 | UAF Unacceptable Attestation (1496). |
What to do? Please contact Support for any questions. |
1206007 | UAF Unacceptable content (1498). |
What to do? Please contact Support for any questions. |
1206008 | UAF Internal Server Error (1500). |
What to do? Please contact Support for any questions. |
1206009 | UAF Internal Error - Invalid Cache (1501). |
What to do? Please contact Support for any questions. |
1206010 | UAF Registration record not found (1502). |
What to do? Please contact Support for any questions. |
1206011 | Could not retrieve the applications. |
What to do? Please contact Support for any questions. |
1206012 | Error creating or updating the application. |
What to do? Please contact Support for any questions. |
1206013 | Invalid characters in the field. |
What to do? Please contact Support for any questions. |
1206014 | Cannot find the application. Please verify you provided the correct AppId. |
What to do? Please contact Support for any questions. |
1206015 | Incorrect AppID provided. |
What to do? Please contact Support for any questions. |
1206016 | Could not retrieve the logins for this user. Please make sure all parameters are correct. |
What to do? Please contact Support for any questions. |
1206017 | Cannot validate the JSON create action bean parameter. |
What to do? Please make sure that all necessary value are specified from the CreateUAFActionBean class. |
1206018 | Error deleting the action. |
What to do? Please contact Support for any questions. |
1206019 | Could not retrieve the authenticators for this user. Please make sure all parameters are correct. |
What to do? Please contact Support for any questions. |
1206020 | Could not lock the user for this aaid. |
What to do? Please make sure all inputs are valid. |
1206021 | The difference between the stored count of login attempts and the authenticator count of login attempts has become inconsistent. |
What to do? An authenticator may be malfunctioning or have been cloned. Logs investigation is recommended. |
1206022 | Could not delete the user. |
What to do? Retry deleting or see the logs. |
1206023 | The UAF authenticator certificate specified in the metadata is about to expire. |
What to do? Update authenticator metadata with latest copy from the FIDO MetaDataService. |
1206024 | UAF invalid encoding problem. |
What to do? Check the UAF encoding. |
1206025 | UAF invalid input problem. |
What to do? Check the UAF input. |
1206026 | UAF invalid request problem. |
What to do? Check the UAF request. |
1206027 | UAF invalid attestation statement problem. |
What to do? Check the UAF attestation statement. |
1206028 | UAF invalid attestation statement problem |
What to do? Check the UAF attestation statement. |
1206029 | UAF invalid client data problem. |
What to do? Check the UAF client data. |
1206030 | UAF invalid authenticator data problem. |
What to do? Check the UAF client authenticator data. |
1206031 | UAF invalid attested credential data problem. |
What to do? Check the UAF attested credential data. |
1206032 | UAF invalid rpi hash problem. |
What to do? Check the UAF rpi hash. |
1206033 | UAF User handle is invalid. |
What to do? Check the UAF user handle. |
1206034 | UAF key type code problem. |
What to do? Check the UAF key type code. |
1206035 | UAF curve type code problem. |
What to do? Check the UAF curve type code. |
1206036 | UAF attestation signature problem. |
What to do? Check UAF attestation signature. |
1206037 | UAF assertion signature problem. |
What to do? Check UAF assertion signature. |
1206038 | UAF invalid CredentialId problem. |
What to do? Check UAF CredentialId. |
1206039 | The certificate does not meet requirements. |
What to do? Check the certificate. |
1206040 | FIDO2 App setup is invalid. |
What to do? Check FIDO2 App setup. |
1206041 | UAF Authenticator metadata is invalid. |
What to do? Check UAF Authenticator metadata |
1206042 | JWT payload is invalid. |
What to do? Check the JWT payload. |
1206043 | Certificate revocation check problem. |
What to do? Please contact Support for any questions. |
1206044 | Operation is not permitted. |
What to do? Please contact Support for any questions |
1206045 | A session is in progress for this user |
What to do? Please contact support for any questions. |
1206046 | UAF Unregistered extension. |
What to do? Please contact Support for any questions. |
1206047 | Could not construct UAFRequest from UAFResponse. |
What to do? Please contact Support for any questions. |
1206048 | Pending QR Fallback request not found. |
What to do? Check that activation code is correct and try again. |
1206049 | QR Fallback is disabled. |
What to do? Verify that Manual QR retrieval is set to Enabled and try again. |
Identity Verification (IdV) Service Error Codes (1207xxx) |
||
1207000 | There was an issue looking up the user info. |
What to do? Check the error payload for details. |
1207001 | There was a configuration issue with the user info service. |
What to do? Check the error payload for details. |
1207002 | The source state was incomplete for this workflow |
What to do? Check the error payload for details. |
1207003 | There was an issue calculating the distance from the user's IP address to their home address |
What to do? Ensure the user's computer is connected near their home address. |
1207004 | The user's home address was not found |
What to do? Add a home address to the user object. |
1207005 | Could not find the user's coordinates from their IP address |
What to do? Check the error payload for details. |
1207006 | There was an issue looking up the user info. |
What to do? Check the error payload for details. |
1207007 | The address of the IP could not be determined |
What to do? Please contact support for any questions. |
1207008 | There was a problem with the requestors magic link. |
What to do? Please contact support for any questions. |
1207009 | There was no transition found for this event. |
What to do? Please contact support for any questions. |
Certificate Authority (CA) Service Error Codes (1208xxx) |
||
1208000 | There was no CA found for the given id. |
What to do? Ensure the requested CA belongs to the current chain or one that already exists in CC. |
1208001 | We were unable to issue the certificate. |
What to do? Please contact support for any questions. |
1208002 | We were unable to get the certificate. |
What to do? Please contact support for any questions. |
1208003 | We were unable to revoke the certificate. |
What to do? Please contact support for any questions. |
1208004 | We were unable to get the certificate chain. |
What to do? Please contact support for any questions. |
HYPR for Android / HYPR SDK for Android
Code | Error | Cause and Resolution |
11100 | Operation was cancelled. |
This error indicates the user has entered in an incorrect 'user presence' check when prompted for their workstation password. During the pairing process, an enterprise may require the user to type in their current password one final time to validate that they are the professional who has logged into the workstation. When this is incorrectly entered, such as in the case where a rogue or malicious user tries to register on a colleague's unlocked workstation, the pairing process will not complete. What to do? 1. Check that the user is on a secure network (office or VPN) try again. This will ensure the user is ready to begin pairing. 2. If the issue persists - Try to register again but proceed quickly through the pairing process. This will ensure that end user speed is not the cause of the issue. 3. If the issue persists - Guide the user to reboot workstation before trying again. |
11100 | Operation cancelled. Please try again. |
The cancel button or back button was pressed during a PIN authentication. What to do? No resolution is needed as this is normal behavior. |
11100 | Operation cancelled. Please try again. |
The cancel button or back button was pressed during a fingerprint authentication. What to do? No resolution is needed as this is normal behavior. |
11100 | Authentication was cancelled. |
The cancel button or back button was pressed during a face/voice authentication. What to do? No resolution is needed as this is normal behavior. |
11100 | Operation cancelled. Please try again. |
The cancel button or back button was pressed during a face/voice registration. What to do? No resolution is needed as this is normal behavior. |
11101 | Unlock Operation was cancelled but returned an Offline Token PIN. | |
111010 | Registration Failed. Please try again or contact your support for more detail. |
Authenticator does not support the attestation type. This occurs when a policy is set to use a Full Basic Authenticator ADP SDK, but the developer used a Surrogate Authenticator Prefs SDK instead. What to do? Modify your policy to use the correct AAIDs. |
ASM / Authentication Errors (112xxx) |
||
112001 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112002 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112003 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112004 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112005 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112006 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112007 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112008 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112009 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112010 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112011 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112012 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112013 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112014 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112015 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112016 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112017 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112018 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112019 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112020 | Operation Failed. Please try again or contact your support for more detail. |
ASM Internal Error What to do? Internal SDK error. Check the logs for more details. |
112501 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112502 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112503 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112504 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112505 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112506 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112507 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112508 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112509 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112510 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112511 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112512 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112513 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112514 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112515 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112516 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112517 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112518 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112519 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112520 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112521 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112522 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112523 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112524 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112525 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112526 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112527 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112528 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112529 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112530 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112531 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
112532 | Operation Failed. Please try again or contact your support for more detail. |
Authenticator Internal Error What to do? Internal SDK error. Check the logs for more details. |
FIDO Client Errors (113xxx) |
||
113001 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113002 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113003 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113004 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113005 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113006 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113007 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113008 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113009 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113010 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113011 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113012 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113013 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113014 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113015 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113016 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113017 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113018 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113019 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113020 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113021 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113022 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113023 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113024 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113025 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113026 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113027 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113028 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113029 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113030 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113031 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113040 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113041 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113050 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113051 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113052 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113053 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113054 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113055 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113056 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113057 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113058 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113059 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113060 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113061 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113062 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113063 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113064 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113065 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113066 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113067 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113068 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113069 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113070 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113071 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113072 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113073 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113074 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113075 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113080 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113081 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113082 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113083 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113084 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113085 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113086 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113087 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113088 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113089 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113090 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113091 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113092 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113093 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113094 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113095 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113096 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
113097 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Internal Error What to do? Internal SDK error. Check the logs for more details. |
General Errors (114xxx) |
||
114010 | Operation Failed. Please try again or contact your support for more detail. |
Any generic failure that is not caused by the user but rather the underlying framework. Example: null pointer exceptions, invalid states, operating system errors, invalid develop implementations of interfaces, etc. What to do? Check the logs for more details. |
114011 | FacetId Check Failed. Please contact your support for more detail. |
The FacetId generated by the top-level application is not present on the Fido Server. What to do? The FacetId needs to be added to the Fido Server FacetId list. |
114012 | Discovery Failed due to no Authenticator matching the policy. Please contact your support for more detail. |
There was no valid authenticator on the device that matched the policy from the server. What to do? Be sure that you are using an authentication that matches with the set policy. Please contact your support for more detail. |
114013 | Operation Failed. Please contact your support for more detail. |
The negotiated server API version is too low for the attempted operation. What to do? Upgrade the server to a version that supports the operation. |
114020 | Authenticator Hardware Not Supported. Please contact your support for more detail. |
The authenticator hardware is not supported on the device which resulted in an invalid application state. What to do? This error is unlikely, but may occur if HYPR is used with a non-HYPR FIDO Client. Please contact your support for more detail. |
114030 | Authenticator is not Registered. Please contact your support for more detail. |
The authenticator is not registered. What to do? Make sure the authenticator is registered. If the issue persists, please contact your support for more detail. |
114030 | Authentication failed. Palm not recognized. Please try again. |
Palm recognition failed due to the palm not being recognized. What to do? Please try again if your palm is registered with this device. |
114040 | Transaction Invalid. Please contact your support for more detail. |
There is a list of transactions specified in the JSON, however, there is no transaction with the type "text/plain". What to do? Correct the JSON being sent in the push notification. |
114050 | Operation failed. This app needs permission to use the camera. Please enable it in the app\’s settings. |
Camera permissions were denied when attempting to scan a barcode. What to do? This app needs permission to use the camera. Please enable it in the app's settings. |
114060 | Operation Failed. Please try again or contact your Support for more detail. |
This a generic error returned by the server to the HYPR Mobile App during the operation. It is a catch-all for several conditions; the root cause should be analyzed by reviewing Audit Trail logs and searching on the trace ID. What to do?
|
114070 | Operation Failed. Please try again or contact your support for more detail. |
Invalid SSL credentials were used. What to do? Make sure that your SSL credentials are correct. |
114071 | Operation Failed. Please try again or contact your support for more detail. |
Malformed Server URL was received or set in the application. What to do? Check the URLs being set in the application or in the barcode. |
114080 | Operation failed. Seems like you have no internet connection. Make sure you are connected to the internet and try again. |
No internet connection. What to do? Make sure you are connected to the internet and try again. |
114090 | Operation cancelled. Please try again. |
This error occurs if the app was backgrounded at any time during an operation. What to do? Please try again, making sure to not background the app. |
Barcode Scanner Errors (11410x) | ||
114100 | Operation Failed. Please try again or contact your support for more detail. |
Barcode scanner failed to start. What to do? Internal SDK error. Check the logs for more details. |
114101 | Operation Failed. Please try again or contact your support for more detail. |
Barcode scanner received a null camera exception. What to do? Internal SDK error. Check the logs for more details. |
114102 | Operation Failed. Please try again or contact your support for more detail. |
Barcode scanner received an access error. What to do? Internal SDK error. Check the logs for more details. |
114103 | Operation Failed. Please try again or contact your support for more detail. |
Barcode scanner preview exception. What to do? Internal SDK error. Check the logs for more details. |
114104 | Operation Failed. Please try again or contact your support for more detail. |
No barcode captured. What to do? Internal SDK error. Check the logs for more details. |
114105 | Operation Failed. Please try again or contact your support for more detail. |
Barcode JSON exception. What to do? Internal SDK error. Check the logs for more details. |
Push Errors (11411x) |
||
114110 | Operation Failed. Please try again or contact your support for more detail. |
Machine null during push notification received. What to do? Internal SDK error. Check the logs for more details. |
114111 | This authentication request is expired. Please try to authenticate again to continue. |
This authentication request is expired. What to do? User should start a new authentication. |
Relying Party Adapter Errors (11412x-114139) |
||
114120 | Operation Failed. Please try again or contact your support for more detail. |
Relying Party Adapter response not valid. What to do? Internal SDK error. Check the logs for more details. |
114121 | Operation Failed. Please try again or contact your support for more detail. |
Relying Party Adapter response database error. What to do? Internal SDK error. Check the logs for more details. |
114122 | Operation Failed. Please try again or contact your support for more detail. |
Relying Party Adapter workstation unlock user logged out. What to do? Internal SDK error. Check the logs for more details. |
114123 | Operation Failed. Please try again or contact your support for more detail. |
Relying Party Adapter workstation unlock user already logged in. What to do? Internal SDK error. Check the logs for more details. |
114124 | Operation Failed. Please try again or contact your support for more detail. |
Relying Party Adapter workstation unlock authentication timed out. What to do? Internal SDK error. Check the logs for more details. |
114125 | Operation Failed. Please try again or contact your support for more detail. |
Relying Party Adapter workstation unlock rejected by workstation. What to do? Internal SDK error. Check the logs for more details. |
114126 | Operation Failed. Please try again or contact your support for more detail. |
Relying Party Adapter workstation unlock complete rejected by workstation. May indicate that workstation lost private key and pairing is broken. What to do? Internal SDK error. Check the logs for more details. |
114130 | We were unable to lock your computer. Please try again on your computer. |
Relying Party Adapter workstation lock failed, workstation unreachable. What to do? Check if the workstation has internet access. |
114131 | Operation Failed. Please try again or contact your support for more detail. | Please try again or contact your support for more detail. |
FIDO Payload Adapter Errors (11414x) |
||
114140 | Operation Failed. Please try again or contact your support for more detail. |
Fido Payload Adapter JSON exception. What to do? Internal SDK error. Check the logs for more details. |
FIDO Client Adapter Errors (11415x) |
||
114150 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Adapter invalid activity action. What to do? Internal SDK error. Check the logs for more details. |
FIDO Client Manager Errors (11416x-11417x) |
||
114160 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager JSON exception. What to do? Internal SDK error. Check the logs for more details. |
114161 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager could not find Fido Client Activity. What to do? Internal SDK error. Check the logs for more details. |
114162 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager no activity status result received. What to do? Internal SDK error. Check the logs for more details. |
114163 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager invalid activity result received. What to do? Internal SDK error. Check the logs for more details. |
114164 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager activity data result null. What to do? Internal SDK error. Check the logs for more details. |
114165 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager callback null. What to do? Internal SDK error. Check the logs for more details. |
114166 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager no discovery data received. What to do? Internal SDK error. Check the logs for more details. |
114167 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager invalid UAF intent type. What to do? Internal SDK error. Check the logs for more details. |
114168 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager intent type missing. What to do? Internal SDK error. Check the logs for more details. |
114169 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager missing error code. What to do? Internal SDK error. Check the logs for more details. |
114170 | Operation Failed. Please try again or contact your support for more detail. |
Fido Client Manager invalid error code. What to do? Internal SDK error. Check the logs for more details. |
FIDO Deregistration Activity (11418x-11419x) |
||
114180 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity not receive lower level error status code. What to do? Internal SDK error. Check the logs for more details. |
114181 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity AAIDs JSON exception. What to do? Internal SDK error. Check the logs for more details. |
114182 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity opdata missing. What to do? Internal SDK error. Check the logs for more details. |
114183 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity opdata null. What to do? Internal SDK error. Check the logs for more details. |
114184 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity activity resume fail. What to do? Internal SDK error. Check the logs for more details. |
114185 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity activity result request code invalid. What to do? Internal SDK error. Check the logs for more details. |
114186 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity error result no status. What to do? Internal SDK error. Check the logs for more details. |
114187 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity intent op null. What to do? Internal SDK error. Check the logs for more details. |
114188 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity intent msg extra null. What to do? Internal SDK error. Check the logs for more details. |
114189 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity intent uaf msg null. What to do? Internal SDK error. Check the logs for more details. |
114190 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity fidointent type invalid. What to do? Internal SDK error. Check the logs for more details. |
114191 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity reg callback invalid method. What to do? Internal SDK error. Check the logs for more details. |
114192 | Operation Failed. Please try again or contact your support for more detail. |
Deregister Activity dereg callback invalid method. What to do? Internal SDK error. Check the logs for more details. |
Display Screen License PIN (11420x) |
||
114200 | Operation Failed. Please try again or contact your support for more detail. |
QR Code parsing error. What to do? Internal SDK error. Check the logs for more details. |
Display Screen Machine (11421x-11428x) |
||
114210 | Operation Failed. Please try again or contact your support for more detail. |
Machine progress exception. What to do? Internal SDK error. Check the logs for more details. |
114211 | Operation Failed. Please try again or contact your support for more detail. |
Machine progress device setup exception. What to do? Internal SDK error. Check the logs for more details. |
114212 | Operation Failed. Please try again or contact your support for more detail. |
Machine progress device setup callback success exception. What to do? Internal SDK error. Check the logs for more details. |
114213 | Operation Failed. Please try again or contact your support for more detail. |
Machine progress device setup callback fail exception. What to do? Internal SDK error. Check the logs for more details. |
114214 | Operation Failed. Please try again or contact your support for more detail. |
Machine progress get fido registrations exception. What to do? Internal SDK error. Check the logs for more details. |
114215 | Operation Failed. Please try again or contact your support for more detail. |
Machine progress add invalid OOB entry type. What to do? Internal SDK error. Check the logs for more details. |
114216 | Operation Failed. Please try again or contact your support for more detail. |
Machine progress device setup success machine null. What to do? Internal SDK error. Check the logs for more details. |
114217 | Operation Failed. Please try again or contact your support for more detail. |
Machine progress add post fido exception. What to do? Internal SDK error. Check the logs for more details. |
114220 | Operation Failed. Please try again or contact your support for more detail. |
Machine device setup exception. What to do? Internal SDK error. Check the logs for more details. |
114230 | Operation Failed. Please try again or contact your support for more detail. |
Machine delete exception. What to do? Internal SDK error. Check the logs for more details. |
114231 | Operation Failed. Please try again or contact your support for more detail. |
Machine delete empty machine id. What to do? Internal SDK error. Check the logs for more details. |
114240 | Operation Failed. Please try again or contact your support for more detail. |
Machine unlock exception. What to do? Internal SDK error. Check the logs for more details. |
114241 | Operation Failed. Please try again or contact your support for more detail. |
Machine unlock invalid qr code. What to do? Internal SDK error. Check the logs for more details. |
114250 | Operation Failed. Please try again or contact your support for more detail. |
Machine offline unlock exception. What to do? Internal SDK error. Check the logs for more details. |
Operations Errors (114290-114999) |
||
114290 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation invalid server response instance What to do? Internal SDK error. Check the logs for more details. |
114291 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation invalid server confirmation response What to do? Internal SDK error. Check the logs for more details. |
114292 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation invalid fido complete response What to do? Internal SDK error. Check the logs for more details. |
114300 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation init null. What to do? Internal SDK error. Check the logs for more details. |
114301 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation audit event size 0. What to do? Internal SDK error. Check the logs for more details. |
114302 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation not supported in API version, too low. What to do? Internal SDK error. Check the logs for more details. |
114303 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation init machine null. What to do? Internal SDK error. Check the logs for more details. |
114304 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation exchange token info empty. What to do? Internal SDK error. Check the logs for more details. |
114305 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation poll method not overridden What to do? Internal SDK error. Check the logs for more details. |
114306 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation patch method not overridden What to do? Internal SDK error. Check the logs for more details. |
114307 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation json exception What to do? Internal SDK error. Check the logs for more details. |
114308 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation fido data null What to do? Internal SDK error. Check the logs for more details. |
Operation - Authentication (11431x) |
||
114310 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation authentication request username empty. What to do? Internal SDK error. Check the logs for more details. |
114311 | [None.] |
`getInitialRequest rpAppType` is WEB and machine is WORKSTATION but feature flag is off for `WINDOWS_WEB_ENROLLMENT` What to do? Enable the `WINDOWS_WEB_ENROLLMENT` feature flag on the server in order to use a workstation that was registered under a WEB RP App type. |
Operation - Deregistration (11432x) |
||
114320 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation deregistration AAID key is empty. What to do? Internal SDK error. Check the logs for more details. |
114320 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation deregistration key ID is empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Logging (11434x) |
||
114340 | Operation Failed. Please try again or contact your support for more detail. | Please try again or contact your support for more detail. |
Operation - License Device Registration (11435x-11437x) |
||
114350 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation device setup pin empty. What to do? Internal SDK error. Check the logs for more details. |
114351 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation device setup callback response invalid. What to do? Internal SDK error. Check the logs for more details. |
114360 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation device registration request empty parameter. What to do? Internal SDK error. Check the logs for more details. |
114361 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation device registration request invalid. What to do? Internal SDK error. Check the logs for more details. |
114362 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation device registration callback response invalid. What to do? Internal SDK error. Check the logs for more details. |
114363 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation device registration callback invalid offline payload. What to do? Internal SDK error. Check the logs for more details. |
114370 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation device setup invalid RP type. What to do? Internal SDK error. Check the logs for more details. |
114371 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation device setup callback response invalid. What to do? Internal SDK error. Check the logs for more details. |
114372 | Machine already paired. | Stop trying to pair the machine; or unpair it if necessary. |
Operation - Web Deregistration (11438x-11439x) |
||
114380 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation website deregistration device ID empty. What to do? Internal SDK error. Check the logs for more details. |
114381 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation website deregistration request machines empty. What to do? Internal SDK error. Check the logs for more details. |
114382 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation website deregistration request returned machines empty. What to do? Internal SDK error. Check the logs for more details. |
114390 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation deregistration device ID empty. What to do? Internal SDK error. Check the logs for more details. |
114391 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation deregistration request machines empty. What to do? Internal SDK error. Check the logs for more details. |
114392 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation deregistration request returned machines empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Machine Status (11440x) |
||
114400 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation machine status request device ID empty. What to do? Internal SDK error. Check the logs for more details. |
114401 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation machine status request RP App ID empty. What to do? Internal SDK error. Check the logs for more details. |
114402 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation machine status callback response invalid. What to do? Internal SDK error. Check the logs for more details. |
114403 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation machine status callback App Profile empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Unlock Canceled (11441x) |
||
114410 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock init invalid state. What to do? Internal SDK error. Check the logs for more details. |
114411 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock cancel request session ID empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Unlock Complete (11442x) |
||
114420 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete machine empty. What to do? Internal SDK error. Check the logs for more details. |
114421 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete session ID empty. What to do? Internal SDK error. Check the logs for more details. |
114422 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete invalid HMAC. What to do? Internal SDK error. Check the logs for more details. |
114423 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete login cert empty. What to do? Internal SDK error. Check the logs for more details. |
114424 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete request parameter empty. What to do? Internal SDK error. Check the logs for more details. |
114425 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete callback invalid. What to do? Internal SDK error. Check the logs for more details. |
114426 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete calback invalid offline payload. What to do? Internal SDK error. Check the logs for more details. |
114427 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete callback machine empty. What to do? Internal SDK error. Check the logs for more details. |
114428 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock complete callback new cert save fail. What to do? Internal SDK error. Check the logs for more details. |
Operation - Unlock (11443x) |
||
114430 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock session ID empty. What to do? Internal SDK error. Check the logs for more details. |
114431 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock callback counter error. What to do? Internal SDK error. Check the logs for more details. |
114432 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock callback offline exception. What to do? Internal SDK error. Check the logs for more details. |
114433 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock callback machine empty. What to do? Internal SDK error. Check the logs for more details. |
114434 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock callback response invalid. What to do? Internal SDK error. Check the logs for more details. |
114435 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation workstation unlock callback response new cert invalid. What to do? Internal SDK error. Check the logs for more details. |
Operation - Magic Link (11444x) |
||
114440 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation magic link callback response invalid. What to do? Internal SDK error. Check the logs for more details. |
Operation - Server Information (11445x) |
||
114450 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation server info callback response invalid. What to do? Internal SDK error. Check the logs for more details. |
Operation - Push Token (11446x) |
||
114460 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation push token request device ID empty. What to do? Internal SDK error. Check the logs for more details. |
114461 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation push token request machine ID empty. What to do? Internal SDK error. Check the logs for more details. |
114462 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation push token request machine username empty. What to do? Internal SDK error. Check the logs for more details. |
114463 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation push token request new token hmac empty. What to do? Internal SDK error. Check the logs for more details. |
114464 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation push token request new token value empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Registration Canceled (11447x) |
||
114470 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation registration cancel request PIN empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Authentication Canceled (11448x) |
||
114480 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation authentication cancel request session ID empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Features (11449x) |
||
114490 | Operation Failed. Please try again or contact your support for more detail. |
Features operation features callback response invalid. What to do? Internal SDK error. Check the logs for more details. |
Operation - Lock (11450x) |
||
114500 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation lock request session ID empty. What to do? Internal SDK error. Check the logs for more details. |
114501 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation lock request RP app ID empty. What to do? Internal SDK error. Check the logs for more details. |
114502 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation lock request device ID empty. What to do? Internal SDK error. Check the logs for more details. |
114503 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation lock request machine ID empty. What to do? Internal SDK error. Check the logs for more details. |
114504 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation lock request machineusername ID empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Pending Authentication (11451x) |
||
114510 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation pending authentication JSON exception. What to do? Internal SDK error. Check the logs for more details. |
114511 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation pending authentication JSON payload invalid. What to do? Internal SDK error. Check the logs for more details. |
114512 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation pending authentication RP App ID empty. What to do? Internal SDK error. Check the logs for more details. |
114513 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation pending authentication device ID empty. What to do? Internal SDK error. Check the logs for more details. |
114514 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation pending authentication machine ID empty. What to do? Internal SDK error. Check the logs for more details. |
114515 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation pending authentication machine username empty. What to do? Internal SDK error. Check the logs for more details. |
114516 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation pending authentication HMAC empty. What to do? Internal SDK error. Check the logs for more details. |
Operation - Token Exchange (11452x) |
||
114520 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation exchange token JSON payload invalid. What to do? Internal SDK error. Check the logs for more details. |
114521 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation exchange token request fields invalid. What to do? Internal SDK error. Check the logs for more details. |
114522 | Operation Failed. Please try again or contact your support for more detail. |
Machine operation exchange token response error. What to do? Internal SDK error. Check the logs for more details. |
Operation - Authentication Session (11453x) |
||
114530 | It looks like your phone isn’t paired with this web account. Contact your admin for help with pairing. |
This happens when the user is trying to log in with QR Code Authenticator, but the user hasn't paired QR Code Authenticator with this URL/Mobile Device yet. What to do? The user should pair with the QR Authenticator and try to log in again. |
114531 | It looks like your phone isn’t paired with this web account. Contact your admin for help with pairing. |
This happens when the user is trying to log in with QR Code Authenticator, but the user hasn't paired QR Code Authenticator with this URL/Mobile Device yet. What to do? The user should pair with the QR Authenticator and try to log in again. |
114532 | This login timed out. Have your phone ready and restart the login on your browser. |
When the user is trying to log in with QR Code Authenticator, the authentication payload is missing the valid session ID. This happens when the user attempts to log in with QR Code Authenticator but didn't authenticate within a timeout period. What to do? The user should try to authentication again and ensure that authentication gets completed within one minute. |
114533 | Authentication cancelled. This feature is not enabled. |
Deep link authentication is blocked by feature flag. What to do? Disable feature flag BLOCK_DYNAMIC_LINK_AUTH_MOBILE and try again. |
Operation - Asynchronous Registration Start (11460x) |
||
114600 | Operation Failed. Please try again or contact your support for more detail. |
The registration state is not valid. What to do? Please try again. |
114601 | The registration timed out. Start a new registration from your computer or web account to try again. |
The registration timed out. What to do? Please try again. |
114602 | The registration was canceled. Start a new registration from your computer or web account to try again. |
The registration was cancelled. What to do? Please try again. |
114603 | Operation Failed. Please try again or contact your support for more detail. |
The registration response was invalid. What to do? Please try again. |
Operation - Async Reg Complete (11461x) |
||
114610 | Operation Failed. Please try again or contact your support for more detail. |
The registration state is not valid. What to do? Please try again. |
114611 | The registration timed out. Start a new registration from your computer or web account to try again. |
The registration timed out. What to do? Please try again. |
114612 | The registration was canceled. Start a new registration from your computer or web account to try again. |
The registration was cancelled. What to do? Please try again. |
114613 | Operation Failed. Please try again or contact your support for more detail. |
The registration response was invalid. What to do? Please try again. |
Operation - Log Submission (11462x) |
||
114620 | Log submission operation request fields invalid. |
What to do? Internal SDK error. Check the logs for more details. |
114621 |
Log submission operation gzip file failed. What to do? |
Internal SDK error. Check the logs for more details. |
114622 | Log submission operation error response from server. |
What to do? Internal SDK error. Check the logs for more details. |
Operation - Cert Retrieval (11463x) |
||
114630 | Cert Retrieval operation request fields invalid. |
What to do? Internal SDK error. Check the logs for more details. |
114631 | Cert Retrieval operation callback response invalid. |
What to do? Internal SDK error. Check the logs for more details. |
114632 | Cert Retrieval operation callback response cert invalid. |
What to do? Internal SDK error. Check the logs for more details. |
114633 | Cert Retrieval operation callback response cert exception. |
What to do? Internal SDK error. Check the logs for more details. |
114634 | Cert Retrieval Confirm operation request fields are invalid. |
What to do? Internal SDK error. Check the logs for more details. |
114635 | Cert Retrieval Confirm operation response fail from server. |
What to do? Internal SDK error. Check the logs for more details. |
Operation - Certificate Retrieval Confirmation (11464x) |
||
114640 | Certificate retrieval confirmation is missing important fields. |
What to do? Verify the confirmation contains all necessary information. If the issue persists, contact an administrator. |
114641 | Certificate retrieval confirmation failed. |
What to do? Verify the confirmation contains all necessary information, and connectivity exists for it to be sent. If the issue persists, contact an administrator. |
Operation - Pending Authentication (11465x) |
||
114650 | Machine not found. |
What to do? Verify the machine is connected to the web; connect to a VPN if your network requires a VPN connection. If the issue persists, contact an administrator. |
114651 | Authentication check payload already found. |
What to do? The payload is a duplicate. Wait a few minutes and try again. If the issue persists, contact an administrator. |
114652 | Authentication check payload is invalid. |
What to do? The payload is not valid. Wait a few minutes and try again. If the issue persists, contact an administrator. |
114653 | Authentication check payload not found. |
What to do? The payload is missing. Wait a few minutes and try again. If the issue persists, contact an administrator. |
Operation - Web Status Registration (1146xx) |
||
114660 | Required fields for web status registration are missing. |
What to do? Verify the fields in the request are correct, then try again. |
114661 | An invalid response was returned during web status registration. |
What to do? Verify the fields in the response are correct, then try again. |
114662 | Web status registration is not available. |
What to do? Verify CC configuration shows Web Status Registration as enabled, then try again. |
114670 | Required fields for web status registration confirmation are missing. |
What to do? Verify the fields in the confirmation are correct, then try again. |
114671 | Web status registration confirmation failure. |
What to do? Verify the fields in the confirmation response are correct, then try again. |
Action Checks (115xxx) |
||
115000 | Operation Failed. Please try again or contact your support for more detail. |
Action could not be started because HYPR is not initialized What to do? Internal SDK error. Check the logs for more details. |
115001 | Operation Failed. Please try again or contact your support for more detail. |
One or more values provided to HyprActions are not valid. This usually happens only when SDK developers are integrating HYPR with APIs. What to do? The developer should analyze the application logs and ensure that implementation follows HYPR documentation. Escalate to HYPR Support if the issue keeps happening. |
115010 | Operation Failed. Please try again or contact your support for more detail. |
Action not valid. What to do? Internal SDK error. Check the logs for more details. |
115011 | Operation Failed. Please try again or contact your support for more detail. |
Action null. What to do? Internal SDK error. Check the logs for more details. |
115012 | Operation Failed. Please try again or contact your support for more detail. |
Add app profile data empty. What to do? Internal SDK error. Check the logs for more details. |
115013 | Operation Failed. Please try again or contact your support for more detail. |
Init OOB device setup already setup. What to do? Internal SDK error. Check the logs for more details. |
115014 | Operation Failed. Please try again or contact your support for more detail. |
OOB start screen not overridden. What to do? Internal SDK error. Check the logs for more details. |
115015 | Operation Failed. Please try again or contact your support for more detail. |
Pre OOB setup screen not overridden. What to do? Internal SDK error. Check the logs for more details. |
115016 | Operation Failed. Please try again or contact your support for more detail. |
Unlock machine does not exist. What to do? Internal SDK error. Check the logs for more details. |
115017 | Operation Failed. Please try again or contact your support for more detail. |
Lock machine does not exist. What to do? Internal SDK error. Check the logs for more details. |
115018 | Operation Failed. Please try again or contact your support for more detail. |
Push machine does not exist. What to do? Internal SDK error. Check the logs for more details. |
115019 | Operation Failed. Please try again or contact your support for more detail. |
Push HMAC invalid. What to do? Internal SDK error. Check the logs for more details. |
115020 | Operation Failed. Please try again or contact your support for more detail. |
Pending auth check machine does not exist. What to do? Internal SDK error. Check the logs for more details. |
115021 | Operation Failed. Please try again or contact your support for more detail. |
Add app profile rptype invalid. What to do? Internal SDK error. Check the logs for more details. |
115022 | Operation Failed. Please try again or contact your support for more detail. |
Add app profile already exists. What to do? Internal SDK error. Check the logs for more details. |
115023 | Operation Failed. Please try again or contact your support for more detail. |
Add app profile data invalid. What to do? Internal SDK error. Check the logs for more details. |
115024 | Operation Failed. Please try again or contact your support for more detail. |
The Pending Authentication list is empty. What to do? Internal SDK error. Check the logs for more details. |
115100 | Operation Failed. Your device is not running a supported OS version. |
The device is not running a supported OS version. What to do? User should update to the latest version of Android to continue using the app. |
115101 | Operation Failed. Your device is not using a supported version of the HYPR mobile application. |
The device is not using a supported version of the HYPR mobile application. What to do? User should update to the latest version of the App. |
115102 | Operation Failed. Your device is not running a supported OS version and is not using a supported version of the HYPR mobile app. |
The device is not running a supported OS version and is not using a supported version of the HYPR mobile app. What to do? User should update to the latest version of iOS then update to the latest version of the App. |
115150 | Operation Failed. Please try again or contact your support for more detail. |
Action data app profile db id not set. What to do? Update to the supported Android OS version and HYPR version. |
115151 | Operation Failed. Please try again or contact your support for more detail. |
Action data domain user profile db id invalid. What to do? Update to the supported Android OS version and HYPR version. |
115152 | Operation Failed. Please try again or contact your support for more detail. |
Action data domain user profile db id no match. What to do? Update to the supported Android OS version and HYPR version. |
115153 | Operation Failed. Please try again or contact your support for more detail. |
Action data rpurl or session id empty. What to do? Update to the supported Android OS version and HYPR version. |
115154 | Operation Failed. Please try again or contact your support for more detail. |
Action data oobentrytype invalid. What to do? Update to the supported Android OS version and HYPR version. |
115155 | Operation Failed. Please try again or contact your support for more detail. |
Action data oobentrytype direct pin or json empty. What to do? Update to the supported Android OS version and HYPR version. |
115156 | Operation Failed. Please try again or contact your support for more detail. |
Action data oobentrytype magiclink token empty. What to do? Update to the supported Android OS version and HYPR version. |
115157 | Operation Failed. Please try again or contact your support for more detail. |
Action data oobentrytype magiclink rpurl empty. What to do? Update to the supported Android OS version and HYPR version. |
115158 | Operation Failed. Please try again or contact your support for more detail. |
Action data machine profile db id emtpy. What to do? Update to the supported Android OS version and HYPR version. |
115159 | Operation Failed. Please try again or contact your support for more detail. |
Action data addappdata emtpy. What to do? Update to the supported Android OS version and HYPR version. |
115160 | Operation Failed. Please try again or contact your support for more detail. |
Action data addappdata invalid. What to do? Update to the supported Android OS version and HYPR version. |
115161 | Operation Failed. Please try again or contact your support for more detail. |
Action data pushtoken empty. What to do? Update to the supported Android OS version and HYPR version. |
115162 | Operation Failed. Please try again or contact your support for more detail. |
Action data qrjson empty. What to do? Update to the supported Android OS version and HYPR version. |
115163 | Operation Failed. Please try again or contact your support for more detail. |
Action data qrjson invalid. What to do? Update to the supported Android OS version and HYPR version. |
115164 | Operation Failed. Please try again or contact your support for more detail. |
Action data offline fido auth invalid. What to do? Update to the supported Android OS version and HYPR version. |
115165 | Operation Failed. Please try again or contact your support for more detail. |
Action data action invalid. What to do? Update to the supported Android OS version and HYPR version. |
115166 | Operation Failed. Please try again or contact your support for more detail. |
Action data null. What to do? Update to the supported Android OS version and HYPR version. |
115167 | Operation Failed. Please try again or contact your support for more detail. |
Action data invalid. What to do? Update to the supported Android OS version and HYPR version. |
Cryptographic Checks (1152xx) |
||
115200 | Operation Failed. Please try again or contact your support for more detail. |
Crypto issue with PKCS12 Certificate. What to do? Internal SDK error. Check the logs for more details. |
115210 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115211 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115220 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115221 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115222 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115230 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115231 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115232 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115233 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115234 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115235 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115236 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115240 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115241 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115242 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115243 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115244 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115245 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115246 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115247 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115248 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115249 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115250 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115251 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
115252 | Operation Failed. Please try again or contact your support for more detail. |
Crypto Internal Error What to do? Internal SDK error. Check the logs for more details. |
Database - Remote Device Checks (1153xx) |
||
115300 | Failed to add info to current device because current device is null. |
What to do? Internal SDK error. Check the logs for more details. |
115301 | Operation Failed. Please try again or contact your support for more detail. |
DB machine add info null exception. What to do? Internal SDK error. Check the logs for more details. |
115302 | Operation Failed. Please try again or contact your support for more detail. |
Failed to add info to current device because machineId was empty. What to do? Internal SDK error. Check the logs for more details. |
115303 | Operation Failed. Please try again or contact your support for more detail. |
Failed to add info to current device because machineName was empty. What to do? Internal SDK error. Check the logs for more details. |
115304 | Operation Failed. Please try again or contact your support for more detail. |
Failed to add info to current device because machineType was empty. What to do? Internal SDK error. Check the logs for more details. |
115305 | Operation Failed. Please try again or contact your support for more detail. |
Failed to add info to current device because machineUsername was empty. What to do? Internal SDK error. Check the logs for more details. |
115306 | Operation Failed. Please try again or contact your support for more detail. |
Failed to add info to current device because sessionId was empty. What to do? Internal SDK error. Check the logs for more details. |
115307 | Operation Failed. Please try again or contact your support for more detail. |
Failed to add info to current device because machine already exists. What to do? Internal SDK error. Check the logs for more details. |
115308 | Operation Failed. Please try again or contact your support for more detail. |
DB machine set machine display name empty. What to do? Internal SDK error. Check the logs for more details. |
115309 | Operation Failed. Please try again or contact your support for more detail. |
DB machine set machine pos not exist. What to do? Internal SDK error. Check the logs for more details. |
115310 | Operation Failed. Please try again or contact your support for more detail. |
DB machine set machine id not exist. What to do? Internal SDK error. Check the logs for more details. |
115330 | Operation Failed. Please try again or contact your support for more detail. |
DB user set id empty. What to do? Internal SDK error. Check the logs for more details. |
115331 | Operation Failed. Please try again or contact your support for more detail. |
DB user get machine empty dbid param. What to do? Internal SDK error. Check the logs for more details. |
115332 | Operation Failed. Please try again or contact your support for more detail. |
BD user get machine does not exist. What to do? Internal SDK error. Check the logs for more details. |
115340 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile add user exists. What to do? Internal SDK error. Check the logs for more details. |
115341 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile delete user by name not exists. What to do? Internal SDK error. Check the logs for more details. |
115342 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile delete user by id not exists. What to do? Internal SDK error. Check the logs for more details. |
115343 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile set user by name not exists. What to do? Internal SDK error. Check the logs for more details. |
115344 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile set user by pos not exists. What to do? Internal SDK error. Check the logs for more details. |
115345 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get user dbid param empty. What to do? Internal SDK error. Check the logs for more details. |
115346 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get user does not exist. What to do? Internal SDK error. Check the logs for more details. |
115347 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get current user does not exist. What to do? Internal SDK error. Check the logs for more details. |
115360 | Operation Failed. Please try again or contact your support for more detail. |
DB app profiles add app profile already exists. What to do? Internal SDK error. Check the logs for more details. |
115361 | Operation Failed. Please try again or contact your support for more detail. |
DB app profiles delete app profile not exists. What to do? Internal SDK error. Check the logs for more details. |
115362 | Operation Failed. Please try again or contact your support for more detail. |
DB app profiles set app profile by name not exists. What to do? Internal SDK error. Check the logs for more details. |
115363 | Operation Failed. Please try again or contact your support for more detail. |
DB app profiles set app profile by url not exists. What to do? Internal SDK error. Check the logs for more details. |
115364 | Operation Failed. Please try again or contact your support for more detail. |
DB app profiles set app profile by id not exists. What to do? Internal SDK error. Check the logs for more details. |
115365 | Operation Failed. Please try again or contact your support for more detail. |
DB app profiles set app profile by position not exists. What to do? Internal SDK error. Check the logs for more details. |
115366 | Limit reached. Please remove a web account and try again. |
DB app profiles web limit reached. What to do? Internal SDK error. Check the logs for more details. |
115367 | Limit reached. Please remove a paired computer and try again. |
DB app profiles workstation limit reached. What to do? Internal SDK error. Check the logs for more details. |
115368 | Limit reached. Please remove a web account and try again. |
DB app profiles web override invalid. What to do? Internal SDK error. Check the logs for more details. |
115369 | Limit reached. Please remove a paired computer and try again. |
DB app profiles workstation override invalid. What to do? Internal SDK error. Check the logs for more details. |
115370 | Limit reached. Please remove a web account and try again. |
DB app profiles web rp limit reached. What to do? Internal SDK error. Check the logs for more details. |
115371 | Limit reached. Please remove a paired computer and try again. |
DB app profiles workstation rp limit reached. What to do? Internal SDK error. Check the logs for more details. |
115372 | Limit reached. Please remove a web account and try again. |
DB app profiles web rp override invalid. What to do? Internal SDK error. Check the logs for more details. |
115373 | Limit reached. Please remove a paired computer and try again. |
DB app profiles workstation rp override invalid. What to do? Internal SDK error. Check the logs for more details. |
115374 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get app dbid param empty. What to do? Internal SDK error. Check the logs for more details. |
115375 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get app does not exist.. What to do? Internal SDK error. Check the logs for more details. |
115376 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get cur app not found. What to do? Internal SDK error. Check the logs for more details. |
115377 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get user dbid param empty. What to do? Internal SDK error. Check the logs for more details. |
115378 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get user does not exist.. What to do? Internal SDK error. Check the logs for more details. |
115379 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get machine dbid param empty. What to do? Internal SDK error. Check the logs for more details. |
115380 | Operation Failed. Please try again or contact your support for more detail. |
DB app profile get machine does not exist.. What to do? Internal SDK error. Check the logs for more details. |
User Agent (1160xx) |
||
116000 | Operation Failed. Please try again or contact your support for more detail. |
User Agent opdata invalid. What to do? Internal SDK error. Check the logs for more details. |
116001 | Operation Failed. Please try again or contact your support for more detail. |
User Agent callback null. What to do? Internal SDK error. Check the logs for more details. |
116002 | Operation Failed. Please try again or contact your support for more detail. |
User Agent request type invalid. What to do? Internal SDK error. Check the logs for more details. |
116010 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op success method invalid. What to do? Internal SDK error. Check the logs for more details. |
116011 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op device setup instance invalid. What to do? Internal SDK error. Check the logs for more details. |
116012 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op api version invalid. What to do? Internal SDK error. Check the logs for more details. |
116013 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op offline unlock machine invalid. What to do? Internal SDK error. Check the logs for more details. |
116014 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op offline unlock prefetch request empty. What to do? Internal SDK error. Check the logs for more details. |
116015 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op machine status instance invalid. What to do? Internal SDK error. Check the logs for more details. |
116016 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op machine status exception. What to do? Internal SDK error. Check the logs for more details. |
116017 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op machine status remove success. What to do? Internal SDK error. Check the logs for more details. |
116018 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op update push token empty. What to do? Internal SDK error. Check the logs for more details. |
116019 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op update push token app profile invalid. What to do? Internal SDK error. Check the logs for more details. |
116020 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op fido operation aaidlist not supported. What to do? Internal SDK error. Check the logs for more details. |
116021 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op fido operation request invalid. What to do? Internal SDK error. Check the logs for more details. |
116022 | Operation Failed. Please try again or contact your support for more detail. |
User Agent Op fido operation instance invalid. What to do? Internal SDK error. Check the logs for more details. |
Get Registrations AAIDs Activity (1161xx) |
||
116100 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity opdata missing. What to do? Internal SDK error. Check the logs for more details. |
116101 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity AAIDs JSON exception. What to do? Internal SDK error. Check the logs for more details. |
116102 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity opdata null. What to do? Internal SDK error. Check the logs for more details. |
116103 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity hyprpersona null. What to do? Internal SDK error. Check the logs for more details. |
116104 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity activity regdata empty. What to do? Internal SDK error. Check the logs for more details. |
116105 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity activity result request code invalid. What to do? Internal SDK error. Check the logs for more details. |
116106 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity error result no status. What to do? Internal SDK error. Check the logs for more details. |
116107 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity intent op null. What to do? Internal SDK error. Check the logs for more details. |
116108 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity intent msg extra null. What to do? Internal SDK error. Check the logs for more details. |
116109 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity intent uaf msg null. What to do? Internal SDK error. Check the logs for more details. |
116110 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity fidointent type invalid. What to do? Internal SDK error. Check the logs for more details. |
116111 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity callback invalid method. What to do? Internal SDK error. Check the logs for more details. |
116112 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activitycallback instance invalid. What to do? Internal SDK error. Check the logs for more details. |
116113 | Operation Failed. Please try again or contact your support for more detail. |
Get Registrations Activity dereg callback invalid method. What to do? Internal SDK error. Check the logs for more details. |
Authenticators (111xxxx) |
||
PIN Authenticator (1110xxx) |
||
1110010 | Authentication failed. Your PIN is incorrect. Please try again. |
Authentication PIN incorrect. What to do? Your PIN is incorrect. Please try again. |
1110020 | Operation failed. Your PIN is incorrect. Please contact your support for more detail. |
The PIN used during headless PIN registration was null. What to do? Make sure that you are using the correct PIN. If the issue persists, please contact your support for more detail. |
1110030 | Operation failed. Your PIN is incorrect. Please contact your support for more detail. |
The PIN used during headless PIN authentication was null. What to do? Make sure that you are using the correct PIN. If the issue persists, please contact your support for more detail. |
1110040 | Operation failed. Your PIN is incorrect. Please contact your support for more detail. |
The PIN used during Headless PIN Registration was invalid. What to do? Make sure that you are using the correct PIN. If the issue persists, please contact your support for more detail. |
1110050 | Operation failed. Your PIN is incorrect. Please contact your support for more detail. |
The PIN used during headless PIN authentication was invalid. What to do? Make sure that you are using the correct PIN. If the issue persists, please contact your support for more detail. |
Biometric Authenticator (1111xxx) |
||
1111010 | Operation failed. Biometric not recognized. Please try again. |
Biometric not recognized. What to do? Biometric not recognized. Please try again. |
1111011 | Operation failed. The ANDROID_BIOMETRIC_PROMPT_SECURITY feature may not be supported by this device. |
The feature ANDROID_BIOMETRIC_PROMPT_SECURITY is not supported on this device. What to do? Turn the ANDROID_BIOMETRIC_PROMPT_SECURITY feature off. Otherwise there is no other resolution for this device. |
1111020 | Operation failed. No biometrics found on this device. You must add one in your phone\'s settings. |
No biometrics found on this device. What to do? No biometrics found on this device. You must add one in your phone's settings. |
1111030 | Operation failed. Too many failure attempts. Please wait to retry. |
Too many failure attempts were made with the Biometric Prompt. What to do? Too many failure attempts. Please wait to retry. |
1111040 | Operation failed. Too many failure attempts. Biometric reader is locked. Please go to Android Settings and unlock biometrics. |
There were more fingerprint failures after the first lockout, resulting in the fingerprint reader being permanently locked. What to do? Too many failure attempts. Fingerprint reader is locked. Please go to Android Settings and unlock fingerprint. |
1111050 | Operation failed. Your request to authenticate this device didn\'t complete in time. Please try again. |
The biometric authentication took too long. What to do? Your request to authenticate this device didn't complete in time. Please try again. |
1111060 | Operation failed. Not enough storage is available. Please free up memory and try again. |
Not enough device storage is available for the operation to proceed. What to do? Please free up disk space and try again. |
1111070 | Operation failed. A new biometric was added to the device. Please re-register. |
A new biometric was added to the device and the FF is turned on to not allow that. What to do? Please re-register the device. |
Face Authenticator (1112xxx) |
||
1112010 | Authentication failed. Something went wrong with your authentication method. Please try again. |
Generic face registration failed with an unknown cause. What to do? Please try again. If the issue persists, please contact your support. |
1112010 | Registration failed. Something went wrong with your authentication method. Please try again. |
Generic face authentication failed with an unknown cause. What to do? Please try again. If the issue persists, please contact your support. |
1112020 | Authentication failed. Your request to authenticate this device didn\'t complete in time. Please try again. |
The user was trying to authenticate with the Face Authenticator, but the authentication took longer than 30 seconds. This usually happens when someone is trying to authenticate with not registered biometrics or the camera couldn't recognize the user's face. What to do? 1. The user should try to authenticate again and ensure that nothing prevents face recognition by the app. 2. The user should restart the device and try again if the steps above didn't help. |
1112020 | Registration failed. Your request to enroll this device didn\'t complete in time. Please try again. |
The user was trying to register with the Face Authenticator, but the authentication took longer than 30 seconds. This usually happens when someone is trying to authenticate with not registered biometrics or the camera couldn't recognize the user's face. What to do? 1. The user should try to register again and ensure that nothing prevents face recognition by the app. 2. The user should restart the device and try again if the steps above didn't help. |
1112030 | Authentication failed. Something went wrong with your authentication method. Please try again. |
Face registration via Sensory failed. What to do? Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support. |
1112040 | Operation failed. This app needs permission to use the camera. Please enable it in the device settings. |
Sensory Face camera was denied when attempting to use face recognition. What to do? This app needs permission to use the camera. Please enable it in the device settings. |
1112050 | Authentication failed. No user registered with face authentication. |
Sensory Face no face registered. What to do? Be sure you are registered for face recognition. |
1112060 | Operation failed. Camera is currently not available. Please close any application which may have the camera in use. |
Physical hardware not available on device. What to do? Camera is currently not available. Please close any application which may have the camera in use. |
1112070 | Operation failed. Not enough storage is available. Please free up memory and try again. |
This issue indicates that there is not enough storage available on device when attempting to use face recognition. What to do? Not enough storage is available. Please free up memory and try again. |
Voice Authenticator (1113xxx) |
||
1113010 | Authentication failed. Something went wrong with your authentication method. Please try again. |
Generic voice registration failed with an unknown cause. What to do? Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support. |
1113010 | Registration failed. Something went wrong with your authentication method. Please try again. |
Generic voice authentication failed with an unknown cause. What to do? Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support. |
1113020 | Authentication failed. Your request to authenticate this device didn\'t complete in time. Please try again. |
Sensory Voice authentication timed out. What to do? Your request to authenticate with this device didn't complete in time. Please try again. |
1113030 | Authentication failed. Something went wrong with your authentication method. Please try again. |
Voice registration failed due to Sensory returning this error code. What to do? Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support. |
1113030 | Registration failed. Something went wrong with your authentication method. Please try again. |
Voice authentication failed due to Sensory returning this error code. What to do? Something went wrong with your authentication method. Please try again. If the issue persists, please contact your support. |
1113040 | Operation failed. This app needs permission to use the microphone. Please enable it in the device settings. |
Sensory Voice was denied microphone permissions when attempting to use voice recognition. What to do? This app needs permission to use the microphone. Please enable it in the device settings. |
1113050 | Authentication failed. No user registered with voice authentication. |
The user has not registered with voice authentication. What to do? Be sure that the user has registered voice authentication and try again. |
1113060 | Operation failed. Microphone is currently not available. Please close any application which may have the microphone in use. |
Microphone is currently not available. What to do? Please close any application which may have the microphone in use. |
1113070 | Operation failed. Not enough storage is available. Please free up memory and try again. |
This error indicates there is not enough storage available on device to complete an operation with the voice authenticator. What to do? Please free up memory and try again. |
Palm Authenticator (1114xxx) |
||
1114010 | Registration failed. Something went wrong with your authentication method. Please try again. |
Palm registration failed due to error. What to do? Something went wrong with your authentication method. Please try again. |
1114020 | Authentication failed. Something went wrong with your authentication method. Please try again. |
Palm authentication failed due to error. What to do? Something went wrong with your authentication method. Please try again. |
1114040 | Operation failed. This app needs permission to use the camera. Please enable it in the device settings. |
Palm permissions denied. What to do? This app needs permission to use the camera. Please enable it in the device settings. |
1114050 | Authentication failed. Your request to authenticate this device didn\'t complete in time. Please try again. |
Your request to authenticate this device didn't complete in time. What to do? Your request to authenticate this device didn't complete in time. Please try again. |
FIDO2 Errors (11200xxx) |
||
11200000 | HYPR_DISPLAY_CODE_FIDO2_ERROR |
What to do? Try again or request support for more assistance. |
11200001 | HYPR_DISPLAY_CODE_FIDO2_CALLBACK_NOT_SET |
What to do? Try again or request support for more assistance. |
11200002 | HYPR_DISPLAY_CODE_FIDO2_CREDENTIAL_NULL |
What to do? Try again or request support for more assistance. |
11200003 | HYPR_DISPLAY_CODE_FIDO2_AUTH_USER_NOT_EXIST |
What to do? Try again or request support for more assistance. |
11200004 | HYPR_DISPLAY_CODE_FIDO2_ACTIVITY_NULL |
What to do? Try again or request support for more assistance. |
11200005 | HYPR_DISPLAY_CODE_FIDO2_MACHINE_USERNAME_NOT_EXIST |
What to do? Try again or request support for more assistance. |
11200006 | HYPR_DISPLAY_CODE_FIDO2_IDP_NOT_ENABLED |
What to do? Try again or request support for more assistance. |
11200007 | HYPR_DISPLAY_CODE_FIDO2_IDP_NOT_CONTAIN_RPID |
What to do? Try again or request support for more assistance. |
11200008 | HYPR_DISPLAY_CODE_FIDO2_CREDENTIAL_NOT_CREATED |
What to do? Try again or request support for more assistance. |
HYPR for iOS / HYPR SDK for iOS
Code | Error | Cause and Resolution |
10100 | Parameters supplied were not valid for the specified operation |
What to do? Try again or request support for more assistance. |
10100 | SHA256 result not available |
What to do? Check debugger logs for more details. |
10101 | The registration operation failed |
What to do? Try again or request support for more assistance. |
10102 | The authentication operation failed |
What to do? Try again or request support for more assistance. |
10102 | The deregister operation failed |
What to do? Try again or request support for more assistance. |
10102 | Unable to register the remote device |
What to do? Try again or request support for more assistance. |
10103 | Deregistration failed |
What to do? Please try again or request support for more assistance. |
10104 | Unable to register the remote device |
What to do? Try again or request support for more assistance. |
10105 | Unable to register the remote device |
What to do? Try again or request support for more assistance. |
10106 | Pairing failed |
What to do? Please try again or request support for more assistance. |
10107 | Unable to unlock the computer due to the connectivity issues |
What to do? Ensure that computer you're trying to login into is connected to the internet. Try to unlock the same computer again after 1 minute. Use the Offline PIN if the steps above didn't help. |
10108 | Unable to cancel the authorized unlock (eg. unlock windows machine) |
What to do? It looks like you are offline, so we couldn't cancel the unlocking process. Check that you are connected to the internet and try again. |
10109 | Unable to complete the remote device authentication (eg. push notification-based operation for web login or transaction) |
What to do? We couldn't reach your device to unlock it. Check that it's turned on, and that you are connected to the internet, then try again. |
10110 | Unable to complete the deregister of one or more remote devices |
What to do? Check that you are connected to the internet and try again. |
10111 | No camera permissions were granted required by Sensory Face Authenticator. |
What to do? Navigate to device settings and make sure that app has permissions to use the camera. Restart the app and try again when permissions were granted. |
10112 | Unable to successfully complete license setup |
What to do? It looks like you are offline, so we couldn't complete the pairing process. Check that you are connected to the internet and try again. |
10113 | Unable to successfully complete status request |
What to do? It looks like you are offline, so we couldn't complete the pairing process. Check that you are connected to the internet and try again. |
10114 | Unable to successfully complete reset app |
What to do? It looks like you are offline, so we couldn't complete the pairing process. Check that you are connected to the internet and try again. |
10128 | Operation cancelled by user |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
10129 | Data verification failed |
What to do? Check debugger logs for more details. |
10200 | Secure Enclave failed |
What to do? Check debugger logs for more details. |
10201 | ADP failed |
What to do? Make sure that ADP initialized with correct configuration. Check debugger logs for more details. |
10300 | Key not found |
What to do? Check debugger logs for more details. |
10999 | The operation was cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
User Agent Errors (10100x-10107x) |
||
101000 | User Agent error |
What to do? HYPRCore error |
101001 | FIDO Registration get request failed |
What to do? Try again or request support for more assistance. |
101002 | FIDO Invalid UAF registration response received |
What to do? Try again or request support for more assistance. |
101003 | FIDO Registration send request failed |
What to do? Try again or request support for more assistance. |
101004 | FIDO Authentication get request failed |
What to do? Try again or request support for more assistance. |
101005 | FIDO Invalid UAF authentication response received |
What to do? Try again or request support for more assistance. |
101006 | FIDO Authentication send request failed |
What to do? Try again or request support for more assistance. |
101007 | FIDO Deregistration get request failed |
What to do? Try again or request support for more assistance. |
101008 | FIDO Invalid UAF deregistration response received |
What to do? Try again or request support for more assistance. |
101009 | Remote Device setup request failed |
What to do? Try again or request support for more assistance. |
101010 | Remote Device registration request failed |
What to do? Try again or request support for more assistance. |
101011 | Remote Device registration for new user failed |
What to do? Try again or request support for more assistance. |
101012 | Remote Device registration for existing user failed |
What to do? Try again or request support for more assistance. |
101013 | Remote Device unlock authentication failed |
What to do? Try again or request support for more assistance. |
101014 | Remote Device unlock failed |
What to do? Try again or request support for more assistance. |
101015 | Remote Device Authentication HMACs generation failed |
What to do? Try again or request support for more assistance. |
101016 | Remote Device unlock failed |
What to do? Try again or request support for more assistance. |
101017 | Remote Device credentials not found during OOB authentication |
What to do? Try again or request support for more assistance. |
101018 | Remote Device OOB authentication failed |
What to do? Something went wrong with your authentication method. Please try again. |
101019 | No registered profiles found |
What to do? Try again or request support for more assistance. |
101020 | Operation failed |
What to do? Please try again or request support for more assistance. |
101021 | Remote Device status update failed |
What to do? Try again or request support for more assistance. |
101022 | Remote Device Cancel unlock failed |
This error indicates that the user was trying to cancel the authenticate request, but it failed due to the computer's connectivity issues. What to do?
|
101023 | Operation failed |
What to do? Please try again or request support for more assistance. |
101024 | Operation failed |
What to do? Please try again or request support for more assistance. |
101025 | Operation failed |
What to do? Please try again or request support for more assistance. |
101026 | Operation failed |
What to do? Please try again or request support for more assistance. |
101027 | Operation failed |
What to do? Please try again or request support for more assistance. |
101028 | Failed to save Remote Device session during setup |
What to do? Try again or request support for more assistance. |
101029 | Operation failed |
What to do? Please try again or request support for more assistance. |
101030 | Operation failed |
What to do? Please try again or request support for more assistance. |
101031 | Attempt to lock an already locked workstation or the workstation does not exist. |
What to do? Try again or request support for more assistance. |
101032 | Attempt to unlock an already unlocked workstation. |
What to do? 1. Try to unlock the account again. 2. Attempt to restart the computer and initiate the unlock again. |
101033 | You've reached the limit of paired web accounts. |
What to do? Unpair an account you're not using and try again. |
101034 | You've reached the limit of paired devices. |
What to do? Unpair a computer you're not using and try again. |
101035 | Workstations limit reached |
What to do? You've reached the limit of paired devices. Unpair a computer you're not using and try again. |
101036 | The account on the current server already paired. Users can't re-pair the same account, de-registration is needed first. |
What to do? Remove this account before trying to pair again. Ensure that you don't have this account paired on mobile app already. |
101037 | The workstation on the current rp already paired |
What to do? This computer is already paired with your HYPR app. You can unlock it from the home screen. |
101038 | This error means that Active Directory Services rejected the authentication or the certificate enrollment. Usually, this will accompany a 403 status code for the authorization request. |
What to do? This error could indicate the misconfiguration of Active Directory Services and may require the system administrator to review logs for more information. For more details, please check HYPROneService, the HYPRCredProvider log files, and the Event Viewer logs from the workstation to which the user is trying to authenticate. Send obtained logs to HYPR Support for more assistance. |
101039 | Operation failed | |
101040 | Offline token access problem. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
101041 | Offline token access not available. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
101042 | Offline token access not enabled. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
101043 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
101044 | Offline mode failed |
What to do? Please make sure you are connected to the internet, next time you are unlocking your computer. |
101045 | Authentication failed |
What to do? We are unable to authenticate you due to an error. Please delete this workstation and re-pair. |
101046 | Operation failed |
What to do? There seems to be an issue with your account. Please try again or unpair and re-pair this workstation. If problems persist, reach out to your support team for more information. |
101047 | Operation failed |
What to do? There seems to be an issue with your account. Please try again or unpair and re-pair this workstation. If problems persist, reach out to your support team for more information. |
101048 | Operation failed |
What to do? There seems to be an issue with your account. Please try again or unpair and re-pair this workstation. If problems persist, reach out to your support team for more information. |
101049 | Operation failed |
What to do? Please try again or request support for more assistance. |
101050 | Invalid Deeplink |
What to do? Please provide a valid deep link |
101051 | OOB Authentication cancelation failed. |
What to do? 1. User should try again in 3 minutes. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
101052 | Device registration cancelation failed. |
What to do? 1. User should try again in 3 minutes. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
101053 | Unable to find user account |
What to do? Please try again or request support for more assistance. |
101054 | Authenticator is not registered |
What to do? Please make sure that the authenticator is registered |
101055 | Push Notification Expired. |
What to do? User should try to authenticate again. |
101056 | Remote Device lock failed. |
What to do? Check if workstation has internet access - Try again or request support for more assistance |
101057 | Pending OOB Auth not supported for this machine type. |
What to do? User should attempt to request pending OOB Authentication for web machines only. |
101058 | The session for this OOB Authentication request is handled already. |
What to do? User should try to login trigger the login on the website one more time before trying to get the pending OOB Authentication request. |
101059 | Pending OOB Authentication error. |
What to do? In most of the cases - because there is no pending auth at the moment, either user didn't trigger it from the web or it is expired already. |
101060 | We couldn’t lock your computer. Please try again later or contact your Admin if this keeps happening. |
What to do? Check if workstation has internet access - Try again or request support for more assistance - check feature flags are enabled. |
101061 | Unknown QR code type. |
What to do? Reach the support. |
101062 | If user has Domain machine registered for this user, the attempt to register VDI machine will fail. |
What to do? Don't try to register VDI machine for the user with already registered Domain machine |
101063 | OOB mobile authentication failure request failed. |
What to do? Failed to authenticate. User should try to authenticate again. |
101064 | HYPR App/SDK Version lower than supported during registration |
What to do? Update HYPR App/SDK. |
101065 | iOS Version lower than supported during registration. |
What to do? Update iOS version. |
101066 | HYPR App/SDK version lower than supported during authentication. |
What to do? Update HYPR App/SDK |
101067 | iOS Version lower than supported during authentication. |
What to do? Update iOS version. |
101068 | HYPR App/SDK Version and iOS lower than supported during registration. |
What to do? Update HYPR App/SDK and iOS. |
101069 | HYPR App/SDK Version and iOS lower than supported during authentication. |
What to do? Update HYPR App/SDK and iOS. |
101070 | Unlock failed. Unlock complete response new cert invalid. |
What to do? Attempt to unlock again. |
API / Endpoint Errors (101071-101074) |
||
101071 | No stored API token for protected endpoint. |
What to do? Ensure that Admin deploying HYPR on the Workstation has specified the correct InstallToken. |
101072 | Failed to Get API Token from Server. |
What to do? Restart the app and try to complete the same operation again. Contact HYPR Support if the issue is still happening. |
101073 | Failed to Save API Token to Keychain. |
What to do? Restart the app and try to complete the same operation again. Contact HYPR Support if the issue is still happening. |
101074 | Protected endpoint failed with invalid token. |
What to do? Ensure that Admin deploying HYPR on the Workstation has specified the correct InstallToken. |
Out-of-Band / Push /Asynchronous Registration (101075-101079) |
||
101075 | Profile Not Found. |
What to do? Restart the app and try to complete the same operation again. Contact HYPR Support if the issue is still happening. |
101076 | Auth QR code invalid |
What to do? Try again or contact support |
101077 | App cannot retrieve auth payload using QR code data |
What to do? Try again or contact support |
101078 | Auth payload invalid |
What to do? Try again or contact support |
101079 | Auth payload session invalid |
What to do? Try again or contact support |
101080 | RP client didn't initialize. |
What to do? Try again or contact support |
101081 | async reg failed with unknown state |
What to do? Try again or contact support |
101082 | Internal error |
What to do? Try again or contact support |
101083 | async reg was canceled from the client side |
What to do? Try again or contact support |
101084 | async reg timeout |
What to do? Try again or contact support |
101085 | Authentication request type is not supported for workstation login |
What to do? Use WFA unlock rather than web authentication for this application |
101086 | No pending push payloads available |
What to do? Authentication on the website is not yet initiated |
101087 | Authentication cancelled. This feature is not enabled. |
What to do? Authentication cancelled. This feature is not enabled. |
101088 | Workstation Not Ready - our workstation isn’t enabled yet. You’ll receive a notification when it’s ready. If it’s been longer than 24 hours, contact your admin. |
This error is thrown when a user selects a pending workstation that has yet to receive a certificate. What to do? Try again or contact Support. |
101089 | Manual QR Code entry failed. |
What to do? Wait a minute, then try again, making sure to be ready to type the code and any accompanying information within 1 minute from initiation. |
101090 | The user agent and the remote device are from different profiles. |
What to do? Wait a minute, then try again. If the issue persists, contact an admin. |
Relying Party Client / License Errors (102xxx) |
||
102000 | Relying Party Client error |
What to do? HYPRCore error |
102001 | Request to the RP server failed |
What to do? Try again or request support for more assistance. |
102002 | The mobile app has received an invalid payload from the server. |
What to do? 1. The user should restart the app and try again. 2. If it didn't resolve the issue, the user should unpair the computer and pair it again to solve this. |
102003 | Parsing RP server response failed |
What to do? Try again or request support for more assistance. |
102500 | License error |
What to do? HYPRCore error |
102501 | Request to Licensing server failed |
What to do? Try again or request support for more assistance. |
102502 | Parsing Licensing server response failed |
What to do? Try again or request support for more assistance. |
102503 | Parsing Licensing server response failed |
What to do? Try again or request support for more assistance. |
HYPR Server Errors (103xxx) |
||
103000 | HYPRErrorServer |
What to do? The server returned an error. Check underlying error for more detail |
FIDO Client Errors (104xxx-106xxx) |
||
UAF General (104000-104007) |
||
104000 | FIDO Client error |
What to do? HYPRCore error |
104001 | FIDO UAF Protocol object missing/malformed. Usually this happens during the integration with the server. |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104002 | FIDO UAF Protocol object missing/malformed |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104003 | Invalid request type in the FIDO Client. |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104004 | FIDO http used instead of https in UAF request |
What to do? Ensure that you're using https FIDO Server URL and try again. |
104005 | FIDO Retrieving facets from url failed |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104006 | FIDO Wrong number of facets retrieved from url |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104007 | FIDO Wrong facets format or content |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
UAF - Registration (104008-104014) |
||
104008 | FIDO Invalid registration request |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104009 | FIDO Failed to initialize ASM |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104010 | FIDO no authenticators matched during registration |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104011 | FIDO registration user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
104012 | FIDO registration failed (multiple reasons) |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104013 | FIDO registration ASM request invalid |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104014 | FIDO registration UAF response invalid |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
UAF - Authentication (104015-104012) |
||
104015 | FIDO Invalid authentication request |
What to do? Try again or request support for more assistance. |
104016 | FIDO Failed to initialize ASM |
What to do? Try again or request support for more assistance. |
104017 | FIDO no authenticators matched during authentication |
What to do? Try again or request support for more assistance. |
104018 | FIDO authentication user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
104019 | FIDO authentication failed (multiple reasons) |
What to do? Try again or request support for more assistance. |
104020 | FIDO authentication ASM request invalid |
What to do? Try again or request support for more assistance. |
104021 | FIDO authentication UAF response invalid |
What to do? Try again or request support for more assistance. |
UAF- Deregistration (104022-104027) |
||
104022 | FIDO Invalid deregistration request |
What to do? Try again or request support for more assistance. |
104023 | FIDO Failed to initialize ASM |
What to do? Try again or request support for more assistance. |
104024 | FIDO deregistration failed (multiple reasons) |
What to do? Try again or request support for more assistance. |
104025 | FIDO deregistration ASM request invalid |
What to do? Try again or request support for more assistance. |
104026 | FIDO unknown operation |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
104027 | FIDO Consumer’s AAID picker view controller doesn’t conform to HYPRAuthenticatorPicker category |
What to do? 1. User should try again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
|
||
104050 | Operation failed. |
This app needs permission to use the camera. Please enable it in the application's settings. |
104060 | Server Error. |
Please try again or contact your Support for more details. |
UAF ASM - Registration (10500x) |
||
105000 | UAF ASM Layer error |
What to do? HYPRCore error |
105001 | FIDO Invalid registration ASM request |
What to do? 1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105002 | FIDO invalid registration ASM request |
What to do? 1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105003 | FIDO authenticator for index not found |
What to do? Try again or request support for more assistance. |
105004 | FIDO cannot generate registration request |
What to do? Try again or request support for more assistance. |
105005 | Error with ASM Registration |
What to do? 1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105006 | FIDO registration failed (multiple reasons) |
What to do? Try again or request support for more assistance. |
105007 | FIDO registration user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
105008 | FIDO required attestation not supported |
What to do? Try again or request support for more assistance. |
105009 | Registration failed |
What to do? Please try again or request support for more assistance. |
UAF ASM - Authentication (105010 - 105022) |
||
105010 | FIDO Invalid authentication ASM request |
What to do? 1. User should restart the application and try to authenticate again. 2. Check debugger logs for more details. |
105011 | FIDO invalid authentication ASM request |
What to do? 1. Ensure that user have registered with this account before 2. Try to re-register and try again 3. Check logs for more details. |
105012 | FIDO authenticator for index not found |
What to do? 1. Ensure that user have registered with this account before 2. Try to re-register and try again 3. Check logs for more details. |
105013 | FIDO authentication signing ASM request invalid |
What to do? 1. User should restart the application and try to authenticate again. 2. Check debugger logs for more details. |
105014 | Authentication failed |
What to do? Please try again or request support for more assistance. |
105015 | Authentication failed |
What to do? Please try again or request support for more assistance. |
105016 | The user is trying to register with Authenticator, but it's not registered. Usually, it happens when authentication policy contains Authenticator which wasn't registered or was removed by the user. |
What to do? 1. Ensure that user have registered with this account before 2. Try to re-register and try again 3. Check logs for more details. |
105017 | FIDO authentication user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
105018 | This error could happened when SDK Developer is trying to use unsupported FIDO command. |
What to do? Check debugger logs for more details and make sure that implementation follows SDK documentation recommendations. |
105019 | FIDO required attestation not supported |
What to do? Check debugger logs for more details. |
105020 | FIDO transaction content cannot be rendered. |
What to do? Check debugger logs for more details and make sure that implementation follows SDK documentation recommendations. |
105021 | Unknown error occurred during the authentication. |
What to do? 1. User should try to authenticate again. 2. User should restart the application and try again. 3. Admin should analyze Audit Trail logs for this user if the problem is still happening. |
105022 | FIDO cannot find key handles for the current username, aaid, keyIds. |
What to do? 1. Ensure that user have registered with this account before 2. Try to re-register and try again 3. Check logs for more details. |
UAF ASM- Deregistration (105023-105030) |
||
105023 | FIDO deregistration invalid ASM request type |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105024 | FIDO deregistration invalid ASM request |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105025 | FIDO deregistration authenticator not found |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105026 | FIDO deregistration invalid ASM request |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105027 | FIDO deregistration failed (multiple reasons) |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105028 | FIDO deregistration cannot find key handles for the current aaid, keyIds |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105029 | FIDO deregistration khAccessTokenHash from server is not equal to the local one |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105030 | FIDO deregistration cannot delete public private key pair |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
UAF ASM - General (105031 - 105039) |
||
105031 | FIDO open settings invalid ASM request type |
What to do? Try again or request support for more assistance. |
105032 | FIDO open settings authenticator not found |
What to do? Try again or request support for more assistance. |
105033 | This error could happened when SDK Developer is trying to use unsupported FIDO command. |
What to do? Check debugger logs for more details and make sure that implementation follows SDK documentation recommendations. |
105034 | FIDO open setting unknown error |
What to do? Try again or request support for more assistance. |
105035 | FIDO get registration invalid ASM request |
What to do? 1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105036 | FIDO get registration invalid ASM request type |
What to do? 1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
105037 | FIDO get registration authenticator not found. Usually this error will occur when authentication policy has authenticators which are not available on user's device. |
What to do? Admin should collect more information about user's device and ensure that authentication policy contains supported authentication method. |
105038 | FIDO get information invalid ASM request type |
What to do? 1. User should try to register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
UAF Authenticator Layer (106xxx) |
||
106000 | UAF Authenticator Layer error |
What to do? HYPRCore error |
106001 | FIDO registration invalid authenticator command |
What to do? Try again or request support for more assistance. |
106002 | FIDO registration authenticator not found |
What to do? Try again or request support for more assistance. |
106003 | FIDO registration no public key data found |
What to do? Try again or request support for more assistance. |
106004 | FIDO registration no registration data found |
What to do? Try again or request support for more assistance. |
106005 | FIDO registration no signed data created |
What to do? Try again or request support for more assistance. |
106006 | FIDO registration no raw signature created |
What to do? Try again or request support for more assistance. |
106007 | FIDO registration user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
106008 | FIDO registration failed |
What to do? Try again or request support for more assistance. |
106009 | FIDO registration result unavailable |
What to do? Try again or request support for more assistance. |
106010 | FIDO registration result unknown |
What to do? Try again or request support for more assistance. |
106011 | FIDO registration user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
106012 | FIDO registration enrollment failed |
What to do? Try again or request support for more assistance. |
106013 | FIDO registration enrollment unavailable |
What to do? Try again or request support for more assistance. |
106014 | FIDO registration enrollment result unknown |
What to do? Try again or request support for more assistance. |
106015 | FIDO registration user already enrolled |
What to do? Try again or request support for more assistance. |
106016 | FIDO registration key generation failed |
What to do? Try again or request support for more assistance. |
106017 | FIDO registration hashing and signing response error |
What to do? Try again or request support for more assistance. |
106018 | FIDO deregistration invalid authenticator command |
What to do? Try again or request support for more assistance. |
106019 | FIDO deregistration authenticator not found |
What to do? Try again or request support for more assistance. |
106020 | FIDO authentication invalid sing command |
What to do? Try again or request support for more assistance. |
106021 | FIDO authentication authenticator not found |
What to do? Try again or request support for more assistance. |
106022 | FIDO authentication authenticator info not found |
What to do? Try again or request support for more assistance. |
106023 | FIDO authentication user not enrolled |
What to do? Try again or request support for more assistance. |
106024 | FIDO cannot find key handles for the current username, aaid, keyIds |
What to do? Try again or request support for more assistance. |
106025 | FIDO sign hashing and signing response error |
What to do? Try again or request support for more assistance. |
106026 | FIDO failed to sign the command |
What to do? Try again or request support for more assistance. |
106027 | FIDO no raw signature created |
What to do? Try again or request support for more assistance. |
106028 | FIDO sign unknown error |
What to do? Try again or request support for more assistance. |
106029 | FIDO sign failed (multiple reasons) |
What to do? Try again or request support for more assistance. |
106030 | FIDO sign user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
106031 | FIDO authentication user not enrolled |
What to do? Try again or request support for more assistance. |
106032 | FIDO transaction sign unknown error |
What to do? Try again or request support for more assistance. |
106033 | FIDO transaction sign failed (multiple reasons) |
What to do? Try again or request support for more assistance. |
106034 | FIDO transaction content cannot be rendered |
What to do? Try again or request support for more assistance. |
106035 | FIDO transaction sign user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
106036 | FIDO get information invalid command |
What to do? Try again or request support for more assistance. |
106037 | FIDO open settings invalid command |
What to do? Try again or request support for more assistance. |
106038 | Operation canceled |
What to do? Please try again or request support for more assistance. |
106039 | Operation canceled |
What to do? Please try again or request support for more assistance. |
Authenticators (107xxx) |
||
107000 | Authenticator Implementation error |
What to do? HYPRCore error |
FaceID (107001-107008) |
||
107001 | Face ID authenticator error. This is a system error returned by the iOS Interface communicating with Face ID Authenticator on the device. |
What to do? Try again or request support for more assistance. |
107002 | Face ID authenticator not available. Usually this happens when iOS can't use Face ID. This can happened due to incomplete permissions or the problem with Face ID on this device. |
What to do? 1. User should ensure that Face ID permissions are granted for this application in the device settings. 2. Ensure that Face ID can be used by any other application. 3. Reboot the device and try again. |
107003 | Face ID authenticator cannot render content |
What to do? Try again or request support for more assistance. |
107004 | Face ID authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107005 | Face ID biometric removal not supported |
What to do? Try again or request support for more assistance. |
107006 | Face ID authenticator user already enrolled |
What to do? Try again or request support for more assistance. |
107007 | Operation failed |
What to do? Please try again or request support for more assistance. |
107008 | Operation failed |
What to do? Please try again or request support for more assistance. |
Fingerprint (107009-107016) |
||
107009 | Fingerprint authenticator error |
What to do? Try again or request support for more assistance. |
107010 | Fingerprint authenticator not available |
What to do? Navigate to device settings and make sure that Touch ID id registered. Restart the app and try to register/authenticate again. |
107011 | Fingerprint authenticator cannot render content |
What to do? Try again or request support for more assistance. |
107012 | Fingerprint authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107013 | Fingerprint biometric removal not supported |
What to do? Try again or request support for more assistance. |
107014 | Fingerprint authenticator user already enrolled |
What to do? Try again or request support for more assistance. |
107015 | Operation failed |
What to do? Please try again or request support for more assistance. |
107016 | Operation failed |
What to do? Please try again or request support for more assistance. |
PIN (107017-107022) |
||
107017 | User is trying to register with PIN, but PIN authenticator user already enrolled |
What to do? User should deregister before trying to register with this authenticator. |
107018 | PIN authenticator cannot render content. |
What to do? 1. Try to re-register and try again 2. Check logs for more details. |
107019 | PIN authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107020 | Authentication Policy contains PIN Authenticator, but PIN authenticator is not enrolled for this user. |
What to do? User should register PIN or policy should be modified to include only registered authenticators. |
107021 | PIN authenticator user data deletion error |
What to do? 1. User should try to de-register again. 2. If the problem is still happening then Admin need to collect logs and analyze it. |
107022 | PIN authenticator user not enrolled |
What to do? User should register PIN or policy should be modified to include only registered authenticators. |
107023 | Fingerprint authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
More FaceID (107024-107038) |
||
107024 | Face ID authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107025 | Face authenticator user already enrolled |
What to do? User should deregister before trying to register with this authenticator. |
107026 | User is not enrolled with Face Authenticator. |
What to do? Try again or request support for more assistance. |
107027 | Operation failed |
What to do? Please try again or request support for more assistance. |
107028 | Face authenticator cannot render content |
What to do? Try again or request support for more assistance. |
107029 | Face authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107030 | Face authenticator user enrollment failed |
What to do? Try again or request support for more assistance. |
107031 | Face authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107032 | Face authenticator enrollment timeout |
What to do? User should try to register again and ensure that registration done in 60 seconds or less. |
107033 | Face authenticator user enrollment result unknown |
What to do? Try again or request support for more assistance. |
107034 | Face authenticator user verification failed |
What to do? Try again or request support for more assistance. |
107035 | Face authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107036 | Face authenticator verification timeout |
What to do? Your request did not complete in time. Please try again. |
107037 | Face authenticator verification result unknown |
What to do? Try again or request support for more assistance. |
107038 | Face authenticator user data migration to new version failed |
What to do? Try again or request support for more assistance. |
Voice (107040-107053) |
||
107040 | Voice authenticator user already enrolled. User is trying to register with Voice, but it's already enrolled. |
What to do? User should remove existing registration before trying to register with this authenticator again. |
107041 | The user is trying to register with Voice Authenticator, but it's not registered. Usually, it happens when authentication policy contains Authenticator which wasn't registered or was removed by the user. |
What to do? 1. Register Voice Authenticator and try again. 2. Modify Authentication policy to only include registered authenticators |
107042 | Voice authenticator failed to de-register. |
What to do? 1. De-register Voice Authenticator and try again. 2. Analyze debugger logs for more details. |
107043 | Voice authenticator cannot render content. |
What to do? Analyze SDK debugger logs and contact HYPR support for the assistance. |
107044 | Voice authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107045 | Voice authenticator user enrollment failed. |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107046 | Voice authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107047 | Voice authenticator enrollment timeout. Usually, it happens when user didn't complete the enrollment process in 60 seconds. |
What to do? User should try to register again in a quiet place and ensure that registration done in 60 seconds or less. |
107048 | Voice authenticator user enrollment result unknown. Usually, it happens when user didn't authenticate on time or tried to authenticate with not registered voice. |
What to do? 1. User should try to authenticate with Voice again. 2. Re-register if the problem still occurs. 3. Analyze SDK debugger logs and contact HYPR support for the assistance. |
107049 | Failed to authenticate the user with Voice. Usually, it happens when user didn't authenticate on time or tried to authenticate with not registered voice. |
What to do? User should try to authenticate again in a quiet place and ensure that authentication done in 30 seconds or less. |
107050 | Voice authenticator user cancelled |
What to do? User should try to perform the same action again. Make sure that user is not backgrounding the app during the operation and don't press cancel button at any point of the flow. |
107051 | Voice authenticator verification timeout. Usually, it happens when user didn't authenticate on time or tried to authenticate with not registered voice. |
What to do? User should try to authenticate again in a quiet place and ensure that authentication done in 30 seconds or less. |
107052 | Voice authenticator verification failed with unknown error. |
What to do? 1. User should try to authenticate again. 2. Admin should analyze SDK logs if the problem is still happening. |
107053 | Voice authenticator user data migration to new version failed. Usually, it happens after HYPR SDK upgrade. |
What to do? Analyze SDK debugger logs and contact HYPR support for the assistance. |
Headless PIN (107060-107067) |
||
107060 | Operation failed |
What to do? Please try again or request support for more assistance. |
107061 | Operation failed |
What to do? Please try again or request support for more assistance. |
107062 | Operation canceled |
What to do? Please try again or request support for more assistance. |
107063 | Operation failed |
What to do? Please try again or request support for more assistance. |
107064 | Operation failed |
What to do? Please try again or request support for more assistance. |
107065 | Operation failed |
What to do? Please try again or request support for more assistance. |
107066 | Operation failed |
What to do? Please try again or request support for more assistance. |
107067 | Operation failed |
What to do? Please try again or request support for more assistance. |
Presence (107080-107083) |
||
107080 | Operation canceled |
What to do? Please try again or request support for more assistance. |
107081 | Operation canceled |
What to do? Please try again or request support for more assistance. |
107082 | Operation canceled |
What to do? Please try again or request support for more assistance. |
107083 | Operation canceled |
What to do? Please try again or request support for more assistance. |
Still More FaceID (107084-107086) |
||
107084 | Operation failed |
What to do? Please check if your passcode is already setup and try again. |
107085 | Operation failed |
What to do? Biometry lockout - please lock the iPhone screen, unlock it using passcode and try again. |
107086 | Operation failed |
What to do? Non-registered face is used to scan. Please use the correct face and try again. |
Palm (1072xx) |
||
107200 | Operation failed |
What to do? Please try again or request support for more assistance. |
107201 | Operation failed |
What to do? Please try again or request support for more assistance. |
107202 | Operation canceled |
What to do? Please try again or request support for more assistance. |
107203 | Operation failed |
What to do? Please try again or request support for more assistance. |
107204 | Operation failed |
What to do? Please try again or request support for more assistance. |
107205 | Operation failed |
What to do? Please try again or request support for more assistance. |
107206 | Operation failed |
What to do? Please try again or request support for more assistance. |
107207 | Operation failed |
What to do? Please try again or request support for more assistance. |
107208 | Operation failed |
What to do? Please try again or request support for more assistance. |
107209 | Operation failed |
What to do? Please try again or request support for more assistance. |
107210 | Operation failed |
What to do? Please try again or request support for more assistance. |
107211 | Operation failed |
What to do? Please try again or request support for more assistance. |
107212 | Operation failed |
What to do? Please try again or request support for more assistance. |
107213 | Operation failed |
What to do? Please try again or request support for more assistance. |
107214 | Operation failed |
What to do? Please try again or request support for more assistance. |
107215 | Operation failed |
What to do? Please try again or request support for more assistance. |
107216 | Operation failed |
What to do? Please try again or request support for more assistance. |
107217 | Operation failed |
What to do? Please try again or request support for more assistance. |
107218 | Operation failed |
What to do? Please try again or request support for more assistance. |
107219 | Operation failed |
What to do? Please try again or request support for more assistance. |
107220 | Operation canceled |
What to do? Please try again or request support for more assistance. |
107221 | Operation failed |
What to do? Please try again or request support for more assistance. |
107222 | Operation failed |
What to do? Please try again or request support for more assistance. |
107223 | Operation failed |
What to do? Please try again or request support for more assistance. |
107224 | Operation failed |
What to do? Please try again or request support for more assistance. |
107225 | Operation failed |
What to do? Please try again or request support for more assistance. |
107226 | Operation failed |
What to do? Please try again or request support for more assistance. |
107227 | Operation failed |
What to do? Please try again or request support for more assistance. |
107228 | Operation failed |
What to do? Please try again or request support for more assistance. |
107229 | Operation failed |
What to do? Please try again or request support for more assistance. |
107230 | Operation failed |
What to do? Please try again or request support for more assistance. |
107231 | Operation failed |
What to do? Please try again or request support for more assistance. |
107232 | Operation failed |
What to do? Please try again or request support for more assistance. |
107233 | Operation failed |
What to do? Please try again or request support for more assistance. |
107234 | Operation failed |
What to do? Please try again or request support for more assistance. |
107235 | Operation failed |
What to do? Please try again or request support for more assistance. |
107236 | Operation failed |
What to do? Please try again or request support for more assistance. |
107240 | Operation failed |
What to do? Please try again or request support for more assistance. |
107241 | Operation canceled |
What to do? Please try again or request support for more assistance. |
107242 | Operation failed |
What to do? Please try again or request support for more assistance. |
107243 | Operation failed |
What to do? Please try again or request support for more assistance. |
HYPR ADP Access (108xxx) |
||
108000 | ADP not initialized |
What to do? Make sure that ADP initialized with correct configuration. Check debugger logs for more details. |
108001 | ADP not available |
What to do? Make sure that ADP initialized with correct configuration. Check debugger logs for more details. |
108002 | ADP already initialized |
What to do? Make sure that ADP initialized with correct configuration. Check debugger logs for more details. |
Offline Mode (109xxx) |
||
109000 | Generic offline tokens error. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109001 | No offline tokens received from server. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109002 | No offline tokens auth received from server. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109003 | No signing certificated received from server. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109004 | Failed to store offline tokens. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109005 | Failed to retrieve offline tokens. |
What to do? Reach the support. |
109006 | The mobile app has received an invalid Offline PINs payload from the server. |
What to do? 1. The user should restart the app and try again. 2. If it didn't resolve the issue, the user should unpair the computer and pair it again to solve this. |
109007 | No offline tokens left. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109008 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
109009 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
109010 | Failed to store discarded offline tokens |
What to do? Try one more time and if doesn't work reach the support. |
109011 | Tokens Base64URL invalid format. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109012 | Offline token field missing in user profile. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109013 | FIDO auth payload error while accessing offline tokens. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109014 | UAF client response error while accessing offline tokens. |
What to do? Try regular unlock before next offline token attempt and if doesn't work reach the support. |
109015 | Authentication canceled while accessing offline tokens. |
What to do? User canceled the authentication, no action needed. |
Offline Mode Key Agreement (1010xxx) |
||
1010000 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010001 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010002 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010003 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010004 | Failed to verify the public key for offline mode. Usually, it happens when authentication for the offline mode has failed. |
What to do? User should try to authenticate again. |
1010005 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010006 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010007 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010008 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010009 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010010 | Offline mode failed |
What to do? Please try again or request support for more assistance. |
1010011 | Random AES iv generation failed during certificate-based login. |
What to do? Reach the support. |
Audit Events (1011xxx) |
||
1011000 | Audit Event failed |
What to do? Audit event failed. Please try again. |
1011001 | Audit Event failed |
What to do? Audit event failed. Please try again. |
1011002 | Audit Event failed |
What to do? Audit event failed. Please try again. |
1011003 | Audit Event failed |
What to do? Audit event failed. Please try again. |
HYPRCore Errors (1020xxx) |
||
1020000 | HMAC validation failed |
What to do? 1. User should try again. 2. If the problem is still happening, ask an administrator to collect logs and analyze it. |
Miscellaneous (1030xxx) |
||
1030000 | Server API version lower than supported by the SDK |
What to do? Upgrade your server to use this Mobile SDK version. |
1030001 | Server API version higher than supported by the SDK |
What to do? Update your mobile app and try again. |
1030010 | Not enough permissions to enable QR scanner. User declined to grant camera permissions. |
What to do? Navigate to device settings and make sure that app has permissions to use the camera. Restart the app and try again when permissions were granted. |
1030011 | Endpoint Security feature flag Required |
What to do? Feature flag `ENDPOINT_API_SECURITY_TOKEN_DEVICE` must be enabled for this flow. |
1030012 | Windows web enrollment feature flag required |
What to do? Feature flag `WINDOWS_WEB_ENROLLMENT` must be enabled for this flow. |
1030013 | Invalid Registration Push Payload |
What to do? Try again or contact Support. |
1072037 | Operation failed |
What to do? Please try again or request support for more assistance. |
1072038 | Operation failed |
What to do? Please try again or request support for more assistance. |
1072039 | Operation failed |
What to do? Please try again or request support for more assistance. |
Enterprise Passkey Error Codes (1030014-1030018) |
||
1030014 | Passkey registration failed. |
What to do? Try again or contact Support. |
1030015 | The IdP for the passkey is not enabled. |
What to do? Verify the IdP settings and connection, then try again. |
1030016 | You have attempted to login to a domain that is not allowed. |
What to do? Login to a different domain. If the problem persists, contact an administrator. |
1030017 | You lack a credential for your passkey. |
What to do? Try unpairing and pairing again. If the issue persists, contact an admin. |
1030018 | Passkey authentication failed. |
What to do? Wait 1 minute and try again. If the issue persists, contact an admin. |