...
Installing Fonts for specific types of reports
Anchor | ||||
---|---|---|---|---|
|
...
SSH to Kyvos Reporting node.
Navigate to the installation path of Kyvos Reporting /jakarta/conf/
In the conf folder, the context.xml and web.xml files are displayed.
Add the following CookieProcessor tag in the context.xml file:
Code Block <!-- Default set of monitored resources. If one of these changes, the --> <!-- web application will be reloaded. --> <WatchedResource>WEB-INF/web.xml</WatchedResource> <WatchedResource>WEB-INF/tomcat-web.xml</WatchedResource> <WatchedResource>${catalina.base}/conf/web.xml</WatchedResource> <!-- Uncomment this to disable session persistence across Tomcat restarts --> <!--<Manager pathname="" />--> <CookieProcessor sameSiteCookies="none" /> </Context>
Add the secure tag in the cookie-config in web.xml file:
Code Block <session-config> <session-timeout>30</session-timeout> <cookie-config> <http-only>true</http-only> <secure>true</secure> </cookie-config> </session-config> <filter> <filter-name>CorsFilter</filter-name> <filter-class>org.apache.catalina.filters.CorsFilter</filter-class> <init-param> <param-name>cors.allowed.origins</param-name> <param-value> https://<KyvosWebAppIP>:<Port></param-value> </init-param> <init-param> <param-name>cors.allowed.methods</param-name> <param-value>GET,POST,HEAD,OPTIONS,PUT</param-value> </init-param> <init-param> <param-name>cors.allowed.headers</param-name> <param-value>Content-Type,X-Requested-With,accept,Origin,Access-Control-Request-Method,Access-Control-Request-Headers</param-value> </init-param> <init-param> <param-name>cors.exposed.headers</param-name> <param-value>Access-Control-Allow-Origin,Access-Control-Allow-Credentials</param-value> </init-param> <init-param> <param-name>cors.support.credentials</param-name> <param-value>true</param-value> </init-param> <init-param> <param-name>cors.preflight.maxage</param-name> <param-value>10</param-value> </init-param> </filter> <filter-mapping> <filter-name>CorsFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
Restart the server after making above changes.
Kyvos Reporting integration with Kyvos
Anchor | ||||
---|---|---|---|---|
|
You need to perform some manual steps if:
Kyvos Reporting and Kyvos are deployed on different URL or are on different network
Kyvos reporting is TLS or HTTPS based
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Note Browser policy does not allow cross-site requests by default, so manual steps must be completed to set automatic logout for Kyvos Reporting Integration with Kyvos. |
Perform following manual steps.
SSH to Kyvos Reporting node.
Navigate to the installation path of Kyvos Reporting /jakarta/conf/
In the conf folder, the context.xml and web.xml files are displayed.
Add the following CookieProcessor tag in the context.xml file:
Code Block <!-- Default set of monitored resources. If one of these changes, the --> <!-- web application will be reloaded. --> <WatchedResource>WEB-INF/web.xml</WatchedResource> <WatchedResource>WEB-INF/tomcat-web.xml</WatchedResource> <WatchedResource>${catalina.base}/conf/web.xml</WatchedResource> <!-- Uncomment this to disable session persistence across Tomcat restarts --> <!--<Manager pathname="" />--> <CookieProcessor sameSiteCookies="none" /> </Context>
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.
...