Run the following command to update the truststore.Copy the Root CA and intermediate files to the directory: /etc/pki/ca-trust/source/anchors cp / /etc/pki/ca-trust/source/anchors.If apps run on an App Host appliance, open an SSH session from the Console to the App Host. Use SSH to log in to the QRadar Console's command line as the root user.Note: Certificates can be obtained from your internal certificate authority or in some cases can be exported directly from your browser after you log in to the QRadar Console. Download the Root CA and intermediate files.Additionally, the Root CA and the intermediate files can be combined into a single file however, combining the files is not a requirement for the application to load or display data successfully. Certificates must be X.509 and have PEM base64 encoding. The private Root CA and all intermediate certificates need to be copied to the local truststore of both the Console and App Host if the certificate is required for your applications.
With url: //api/ariel/ (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', HTTPSConnectionPool(host=’ ‘, port=443): Max retries exceeded The app log file, identifies the certificate verify failed: As you configure the Authorized Service token for a newly installed IBM application, the application fails to save the token.'SS元_GET_SERVER_CERTIFICATE', 'certificate verify failed')],)",),)) Url: //api/ariel/ (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', HTTPSConnectionPool(host=’ ‘, port=443): Max retries exceeded with The app log can identify why certificate validation failed: The application loads, but is missing information or dashboard widgets are not populating.Check if your QRadar Certificates are setup properly. A certificate error is displayed in the QRadar user interface when the application loads: Cannot establish secure connection to the console.
0 kommentar(er)
