Skip to content

Instantly share code, notes, and snippets.

@brenopolanski

brenopolanski/solving-cors-pentaho-cde.md

Last active February 23, 2021 17:40
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save brenopolanski/fce90f0090ce19bcaa3acef4af9c8eb3 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save brenopolanski/fce90f0090ce19bcaa3acef4af9c8eb3 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. brenopolanski revised this gist Feb 23, 2021. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion solving-cors-pentaho-cde.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,7 +36,7 @@ and then change it to:

    3. Add `cors-filter-2.4.jar` to the `<<pentaho-server>>/tomcat/lib directory`.

    Download: [cors-filter-2.4.jar](http://central.maven.org/maven2/com/thetransactioncompany/cors-filter/2.4/cors-filter-2.4.jar)
    Download: [cors-filter-2.4.jar](https://search.maven.org/remotecontent?filepath=com/thetransactioncompany/cors-filter/2.4/cors-filter-2.4.jar)

    4. Add below filter-mapping into the `<<pentaho-server>>/tomcat/conf/web.xml` file:

  2. brenopolanski renamed this gist Nov 27, 2018. 1 changed file with 0 additions and 0 deletions.
    0 solve-cors-pentaho-cde.md → solving-cors-pentaho-cde.md
    View file
    File renamed without changes.
  3. brenopolanski created this gist Nov 27, 2018.
    86 changes: 86 additions & 0 deletions solve-cors-pentaho-cde.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,86 @@
    # Solving CORS problem on embedding Pentaho CDE dashboard in web application

    > [Cross-Origin Resource Sharing](https://www.w3.org/TR/cors/) (CORS) is a W3C spec that allows cross-domain communication from the browser. By building on top of the XMLHttpRequest object, CORS allows developers to work with the same idioms as same-domain requests.
    Enable Cross Origin Resource Sharing (CORS) in the Community Dashboard Framework (CDF), Community Dashboard Editor (CDE), and Community Data Access (CDA). While you need CDE to embed the dashboard, you will access it from a different server other than the Pentaho Server, so CORS must be enabled in CDF, CDE and CDA. Open the following CDF, CDE, and CDA `settings.xml` files in a text editor:

    - For CDF: `server/pentaho-server/pentaho-solutions/system/pentaho-cdf/settings.xml`.
    - For CDE: `server/pentaho-server/pentaho-solutions/system/pentaho-cdf-dd/settings.xml`.
    - For CDA: `server/pentaho-server/pentaho-solutions/system/cda/settings.xml`.

    Make the following replacements in each `settings.xml` file:

    1. Find the line:

    ```
    <cors-request-allowed>false</cors-request-allowed>
    ```

    and then change it to:

    ```
    <cors-request-allowed>true</cors-request-allowed>
    ```

    2. Find the line:

    ```
    <cors-requests-allowed-domains><!-- allowed domains here --></cors-requests-allowed-domains>
    ```

    and then change it to:

    ```
    <cors-requests-allowed-domains>http://localhost:2777</cors-requests-allowed-domains>
    ```

    3. Add `cors-filter-2.4.jar` to the `<<pentaho-server>>/tomcat/lib directory`.

    Download: [cors-filter-2.4.jar](http://central.maven.org/maven2/com/thetransactioncompany/cors-filter/2.4/cors-filter-2.4.jar)

    4. Add below filter-mapping into the `<<pentaho-server>>/tomcat/conf/web.xml` file:

    ```
    <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>*</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>
    ```

    ## Resources

    - https://www.w3.org/TR/cors/
    - https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
    - https://enable-cors.org
    - https://en.wikipedia.org/wiki/Cross-origin_resource_sharing
    - https://help.pentaho.com/Documentation/8.0/Products/CTools/CDE_Advanced_Solutions
    - http://www.ease2code.com/embedding-pentaho-cde-dashboard-in-web-application/
    - https://daveceddia.com/access-control-allow-origin-cors-errors-in-react-express/