Skip to content

2024.02.00-geOrchestra

Latest
Compare
Choose a tag to compare
@dsuren1 dsuren1 released this 21 Mar 08:40
· 1 commit to 2024.02.xx since this release
ee99a39

This is the final release including all updates previously released within related RCs of the same series and new updates provided in the stable branch 2024.02.xx

The MapStore submodule revision has been updated to point to the latest stable version of MapStore (2024.02), where the majority of the involved updates have been contributed.

What's Changed

Relevant fixes and enhancements

Documentation update

MapStore documentation

MapStore latest documentation to use as a reference

Involved migration guidelines for this RC

Docker Image

https://hub.docker.com/r/geosolutionsit/mapstore2-georchestra/tags?page=1&name=2024.02.00-geOrchestra

Migration Changes

  • NodeJS and NPM update
    From this version the recommended version to build MapStore or for development is Node 20 (minimum version will be Node 16). Please update your Node version accordingly on your develop machine or CI/CD. Always refer to the official requirements section of the online MapStore documentation.

  • Using elevation layer type instead of wms layer with useForElevation property
    The wms layer with useForElevation property is deprecated and a elevation layer introduced in substitution.

    {
        "name": "Map",
        "cfg": {
            "additionalLayers": [
                {
    -               "type": "wms",
    +               "type": "elevation",
                    "url": "/geoserver/wms",
                    "name": "workspace:layername",
    -               "format": "application/bil16",
                    "visibility": true,
    -               "useForElevation": true,
                    "littleEndian": false
                },
                // only needed for 3D terrain
    +           {
    +               "type": "terrain",
    +               "provider": "wms",
    +               "url": "/geoserver/wms",
    +               "name": "workspace:layername",
    +               "littleEndian": false,
    +               "visibility": true,
    +               "crs": "CRS:84"
                }
            ]
        }
    }
  • Integration with openID Connect
    MapStore now supports OpenID Connect (OIDC) authentication with providers like Keycloak, Okta, Google, and Azure.
    Update geostore-spring-security.xml if not using the default file. Otherwise, no changes are needed.

    Apply these changes if required:

    @@ -24,6 +24,7 @@
             <security:custom-filter ref="sessionTokenProcessingFilter" after="FORM_LOGIN_FILTER"/>
             <security:custom-filter ref="keycloakFilter" before="BASIC_AUTH_FILTER"/>
             <security:custom-filter ref="googleOpenIdFilter" after="BASIC_AUTH_FILTER"/>
    +        <security:custom-filter ref="oidcOpenIdFilter" before="OPENID_FILTER"/> <!-- ADD a filter with this ref -->
             <security:anonymous />
         </security:http>
    
    @@ -52,6 +53,7 @@
    
         <!-- OAuth2 beans -->
         <context:annotation-config/>
    +    <bean id="oidcSecurityConfiguration" class="it.geosolutions.geostore.services.rest.security.oauth2.openid_connect.OpenIdConnectSecurityConfiguration"/> <!-- add this bean to configure the integration -->
    
         <bean id="googleSecurityConfiguration" class="it.geosolutions.geostore.services.rest.security.oauth2.google.OAuthGoogleSecurityConfiguration"/>
  • MapFish Print update
    The MapFish Print library has been updated to work with the latest GeoTools version and Java 11 as well as being aligned with the same dependency used by the official GeoServer printing extension

    • Print config file update
      Due to the introduction of the new Jackson Yaml parser, the print config.yaml file has been reviewed and updated. Please refer to the documentation here for the details
    • Enable showing credits/attribution text in Print config
      To ensure that the layers' credits/attributions are displayed correctly on the printed map, specifically at the bottom of the map section, it is necessary to review and update the print config.yaml file.

Note: see what already contributed for the geOrchestra datadir in georchestra/datadir#428.

DB Changes

Follow the migration details with respect to DB/schema changes (migration information is available here in detail):

POSTGRESQL

ORACLE

H2

Extension compatibility

Below versions of extensions are compatible with this RC release

New GeoServer plugins and extensions supported from this release

MapStore supports several plugins for GeoServer. Following are the new GS plugins supported by MS. Complete list can be found here

Full Changelog: 2023.02.03-geOrchestra...2024.02.00-geOrchestra