...
Using Web Browser
Open web browser and type the Kyvos or Kyvos Reporting URL in the address bar of the web browser.
Kyvos: https://<ip/hostname>:port/kyvos
Kyvos Reporting: https://<ip/hostname>:port/kyvosreporting
Depending on your browser, you can usually access certificate details by clicking the padlock icon next to the website's URL in the address bar. This icon typically indicates that the connection is secure.
In the context menu, right-click the padlock icon or in the browser's security settings, look for an option View Certificate or Certificate information.
Here's an example image to help you open certificates on Google Chrome or Microsoft Edge. If you're using a different web browser, you can search for instructions.
Google Chrome | Microsoft Edge |
---|---|
Using terminal
Go to the terminal, and navigate to the location where certificate is placed.
To check the alias stored in .jks file, execute the keytool -list -v -keystore your_keystore.jks command.
Execute the keytool -export -alias your_alias -file certificate.cer -keystore your_keystore.jks command to export the certificate from the .jks file to a file in X.509 certificate format (usually with a .cer or .crt extension).
Replace your_alias with the alias of the certificate entry in your keystore, and your_keystore.jks with the path to your .jks file.
...
Login to Kyvos Reporting Portal.
Go to Navigate > Configure > Connection > click on Actions menu (…), and then click Upload Driver.
For uploading the driver, refer to Intellicus documentation.After deploying the Hive jars, restart Kyvos Reporting Service.
Login to Kyvos Manager.
In the navigation pane, click Kyvos and Ecosystem > Kyvos Properties.
On the Kyvos Properties page, in the Globals.properties section, click Add Property. The Add Property dialog appears.
In the Add Property dialog, add property name as INTELLICUSREPORTING_PORTAL_URL and mention the Kyvos Reporting URL as
http://<ip>:<port>/kyvosreporting/rest/tokenValidator/validateTokenAfter saving the property, restart the Kyvos Web Portal.
Login to Kyvos Reporting Portal, and create a Kyvos connection.
Enabling Transport Security Layer (TLS)
Anchor | ||||
---|---|---|---|---|
|
Enable TLS communication between the report engine and web client components: The Kyvos Reporting portal supports TLS communication between the report engine and web client components. This feature mitigates risks associated with unsecured transmission. For further details about enabling TLS, see Intellicus documentation.
After performing post-deployment steps, you can sign in to Kyvos Reporting Services to design smart reports, charts, and dashboards without knowing where and how the data is fetched from the database. For more information about Kyvos Reporting, see the Intellicus documentation.Accessing Kyvos Reporting when integrating with Kyvos:After enabling TLS, you need to perform the following manual steps to allow cross-site requests to access Kyvos Reporting when integrating with Kyvos.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Note
|
Known Behavior
Anchor | ||||
---|---|---|---|---|
|
Selecting the Kyvos Reporting link from the Kyvos Manager dashboard redirects to the IP-based Kyvos Reporting URL, not the load-balanced Kyvos reporting URL.
TLS is not supported in Kyvos Reporting deployment.
All the Kyvos Reporting services (Kyvos Reporting Server and Kyvos Reporting Portal) are installed on the same node.
Migration of Kyvos Reporting services from one node to another is not supported.
Postgres instance is shared between Kyvos and Kyvos Reporting.
If Kyvos Reporting Service has already been deployed and you want to roll back the Kyvos Manager release earlier to 2024.2, then before performing Kyvos Manager rollback, you must remove Kyvos Reporting Service.
...