Versions Compared

Old Version 3

changes.mady.by.user Sarabjeet Kaur

Saved on

compared with

New Version 4

changes.mady.by.user Sarabjeet Kaur

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

  • The integrated application (Kyvos Reporting) should run in SSL mode.

  • Ensure that you use valid certificates from Signed Authorities in both the applications.

  • In case of untrusted certificate or key store, Kyvos Reporting certificate file should be present in Trusted store of your application JVM. See the Importing Certificate Details section.

To access Kyvos Reporting when integrating with Kyvos, perform the following steps.

  1. SSH to Kyvos Reporting node.

  2. Navigate to the installation path of Kyvos Reporting /jakarta/conf/

  3. In the conf folder, the context.xml and web.xml files are displayed.

  4. 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>

  5. 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>

  6. Restart the server after making above changes.

...

Known Behavior
Anchor
KB
KB

  1. 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.

  2. TLS is not supported in Kyvos Reporting deployment.

  3. All the Kyvos Reporting services (Kyvos Reporting Server and Kyvos Reporting Portal) are installed on the same node.

  4. Migration of Kyvos Reporting services from one node to another is not supported.

  5. Postgres instance is shared between Kyvos and Kyvos Reporting.

  6. 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.

...