Question & Answer
Question
Cause
When a request for non-HTML content is made and an error occurs, JSON fields are returned with an error code and a message.
When a request for an HTML document is made and an error occurs, we either return back:
- An HTML page with the error.
- The HTML configuration page with an extra inline notification prompting the user to review and correct the applications configuration.
Note: When the error code is E_REQUIRES_CONFIGURATION, E_PROXY_QRADAR_UNAUTHORIZED, E_PROXY_QRADAR_ENOTFOUND, E_PROXY_QRADAR_CONNREFUSED, E_PROXY_QRADAR_TIMEOUT, or E_PROXY_QRADAR_SSL_ERROR, the HTML configuration page (2) is returned. For all other errors, the HTML error page (1) is returned.
When an error occurs, the proxied app can display a link to /app/qproxy
to display the HTML configuration page.
Answer
Error Code | Status | Message | Description |
E_PROXY_REDIRECTED | 302 | The QRadar instance does not support basic username and password authentication. The requests to QRadar apps UI will be redirected to QRadar directly without proxying. | Redirection because of unsupported authentication for the currently configured QRadar instance. |
E_REQUIRES_CONFIGURATION | 400 | QRadar connection configuration is not set. | The proxy configuration is not set. If the dashboard was accessed before the proxy was configured. If the configuration got deleted, after an application launched, and the application then tried to make a request. |
E_PROXY_QRADAR_ENOTFOUND | 400 | Unable to proxy the request to QRadar due to DNS resolution errors. Check your connection details in QRadar Proxy configuration. | A request for proxying is made and the DNS lookup fails. Possibly an invalid ip or host name used. |
E_PROXY_QRADAR_CONNREFUSED | 400 | Unable to proxy the request to QRadar as connection to QRadar was refused. Check the QRadar IP address/Hostname and port in QRadar Proxy configuration. | A request for proxying is made and the connection is refused. Possible connecting to incorrect port. |
E_PROXY_QRADAR_SSL_ERROR | 400 | Unable to send the request to QRadar because a secure connection to QRadar could not be established. Use the proper certificates from QRadar in the QRadar Proxy configuration. | A request for proxying is made and there is an invalid SSL certificate or Server name indicator (SNI). |
E_PROXY_QRADAR_APP_UNSUPORTED | 400 | The requested QRadar app is not supported. | Proxying to an unsupported app, or wrong configured URL. |
E_PROXY_QRADAR_UNAUTHORIZED | 401 | Unable to proxy the request to QRadar due to authorization error. Check your QRadar authentication token in QRadar Proxy configuration. | When an invalid SEC token is saved in the config, and a request for proxying to QRadar was made. |
E_ENTITLEMENTS_UNAUTHORIZED | 401 | The user"s role for QRadar Proxy could not be verified as the user is not authorized to access the entitlements service. Contact the administrator for granting access. | Entitlement error - either user has no access or there was an error during processing of the users access. |
E_LOCKED_OUT | 401 | You have been locked out of QRadar due to too many failed login attempts. Please try again later. | The QRadar instance locked out the user for too many failed login attempts. |
E_QRADAR_PROXY_NO_ACCESS | 403 | You do not have access to the QRadar Proxy. Contact the administrator for access to the QRadar Proxy. | If the user's CP4S role for QProxy is set to No Access. |
E_ENTITLEMENTS_NOT_FOUND | 403 | The user"s role for QRadar Proxy could not be verified as no entitlements were found in the entitlements service for the user. Contact the administrator for granting access. | Entitlement error - either user has no access or there was an error during processing of the users access. |
E_QCONFIG_FORBIDDEN | 403 | You do not have sufficient access for this operation. Contact the administrator for granting access. | Permission error. |
E_PROXY_QRADAR_UNACCEPTED_LICENSE | 403 | The QRadar license has not been accepted for the account associated with the provided credentials. Retry after the QRadar license has been accepted. | Account used must first log in to QRadar user interface (UI) Console and accept the user license agreement (ULA). |
E_SERVER_SETTINGS_FORBIDDEN | 403 | You do not have sufficient access for this operation. Contact the administrator for granting access. | Unable to access the server settings because of permissions. |
E_PROXY_QRADAR_APP_NOT_FOUND | 404 | The requested QRadar app is not found. | Proxying to an app that is not installed in the currently configured QRadar instance. |
E_PROXY_QRADAR_TIMEOUT | 408 | Unable to proxy the request to QRadar as the request timed out. Check the QRadar IP address/Hostname and port in QRadar Proxy configuration. | When a request for proxying is made and the QRadar host did not respond back within 30 secs, or providing an invalid ip or host name. |
E_ENTITLEMENTS_UNKNOWN_ERROR | 500 | An unknown error occurred while fetching the user's roles from the entitlements service. Check the logs for more details. | Entitlement error - either user has no access or there was an error during processing of the users access. |
E_ENTITLEMENTS_MISSING_PARAMS | 500 | Unable to fetch the user"s roles from the entitlements service due to missing parameters in the request. | Entitlement error - either user has no access or there was an error during processing of the users access. |
E_ENTITLEMENTS_UNKNOWN_ERROR | 500 | An unknown error occurred while fetching the user's roles from the entitlements service. Check the logs for more details. | Entitlement error - either user has no access or there was an error during processing of the users access. |
E_QRADAR_PROXY_NO_ACCESS | 500 | You do not have access to QRadar Proxy. Contact the administrator for access to QRadar Proxy. | Entitlement error - either user has no access or there was an error during processing of the users access. |
E_PROXY_QRADAR_UNKNOWN | 500 | Unable to send the request to QRadar due to an unknown error. Check your connection details in the QRadar Proxy configuration. | An unknown error occurred with the proxy operation. |
E_SERVER_SETTINGS_UNKNOWN_CFGSTORE_GET | 500 | An unknown error occurred while fetching the QRadar Proxy configuration from the Config Store service. Check the logs for more details. | Issue with configured storage. |
E_SERVER_SETTINGS_DECRYPT_CFGSTORE_GET | 500 | An error occurred while decrypting the QRadar Proxy configuration from the Config Store service. Check the logs for more details. | Config store error due to decryption problems. Verify cypher key is correct. |
E_INVALID_USER_IN_REQUEST | 500 | No valid user was found in the request. | Verify user exists, and LDAP is accessible. |
E_MALFORMED_QCONFIG_REQUEST | 500 | The QRadar configuration in the request is malformed. | Verify configuration. |
E_PROXY_UNKNOWN | 500 | Unable to send the request to QRadar due to an unknown error. Check your connection details in the QRadar Proxy configuration. | Verify networking configuration. |
E_UNKNOWN | 500 | An unknown error has occurred. Check the logs for more details. | Contact support. |
E_FAILED_JWT_VERIFICATION | N/A | The JWT token could not be verified. | Verify token. |
E_MISSING_JWT_PARAMS | N/A | The JWT token is missing the required parameters: sub and isc_account. | Verify token. |
Related Information
Was this topic helpful?
Document Information
Modified date:
05 January 2023
UID
ibm16852809