The GeoServer development community has officially announced the release of GeoServer 3.0.2, marking another important milestone for the stable 3.0 production series. Available immediately for download in binary, WAR, Windows installer, documentation, and extension packages, this new stable update brings together a series of core component upgrades, important security hardening measures, and major feature completions driven by the project’s recent crowdfunding campaigns.
As a recommended upgrade for production environments, GeoServer 3.0.2 integrates the latest foundational libraries to ensure optimal performance, stability, and compatibility across enterprise mapping infrastructures. This release bundles GeoTools 35.2 and GeoWebCache 2.0.2, alongside mapfish-print-v2 2.5.2 and ImageN 0.9.3. Furthermore, the release of GeoServer Cloud 3.0.2 marks a notable achievement for the project, representing the first time an updated cloud-native variant has been made available simultaneously on the exact day of the core platform’s release.
The successful coordination and execution of this release were made possible through the collaborative efforts of key community contributors. Jody Garnett of GeoCat spearheaded the release process, while Andrea Aime of GeoSolutions handled rigorous testing protocols. Additionally, Gabriel Roldan of Camptocamp managed the concurrent launch of GeoServer Cloud 3.0.2.
Security Considerations and Upgrade Advice
Addressing security vulnerabilities remains a top priority for the GeoServer maintainers, making version 3.0.2 an essential upgrade for any organization running production-grade mapping services. While the current release incorporates vital security fixes to safeguard enterprise infrastructure, comprehensive details regarding the specific vulnerabilities addressed will be publicly disclosed at the start of November. System administrators managing production deployments are encouraged to review the project’s official security policy documentation on GitHub to better understand how vulnerabilities are identified, managed, and mitigated across the software lifecycle.
OGC API Maps 1.0 Integration
In the realm of open standards, the OGC API Maps community module has undergone significant refinement to align fully with the final OGC API – Maps 1.0.0 specification. This alignment ensures that GeoServer deployments can deliver modern, standards-compliant web mapping services that meet the rigorous interoperability requirements set by the Open Geospatial Consortium. The successful integration of this standard was driven by Andrea Aime of GeoSolutions, who led the development work, with Jody Garnett of GeoCat managing the 3.0.x backport and introducing key improvements to the conformance table editor within the user interface. Detailed configuration and usage guidelines for this capability are now available in the official GeoServer user manual.
GeoFence for GeoServer 3 and Crowdfunding Milestone
The release of GeoServer 3.0.2 also brings long-awaited security and access control capabilities to the platform via the introduction of GeoFence extensions for GeoServer 3. This milestone successfully completes Milestone 4, focusing on core integration, as outlined in the ambitious GeoServer 3 crowdfunding campaign.
To bring GeoFence up to date with modern Java enterprise standards, the codebase has been extensively updated to support Jakarta EE, Spring Framework 7, and Hibernate 7. While these architectural modernizations deliver enhanced performance and long-term viability, existing users migrating from older iterations must exercise caution. Administrators are strongly advised to review the official migration guide prior to upgrading, as the underlying datasource configuration file has been renamed, and the legacy GeoFence authentication provider has been deprecated and removed.
The realization of GeoFence for GeoServer 3 was led by Emanuele Tajariol of GeoSolutions. The development was funded entirely by the generous contributions of the GeoServer 3 crowdfunding sponsors, a diverse coalition of global organizations and individual donors committed to the sustainability and evolution of open-source geospatial software.
Institutional and Individual Contributors
The ongoing development, maintenance, and long-term viability of the GeoServer project rely heavily on the financial backing and institutional commitment of its sponsors and community members. GeoServer 3 receives direct support from a wide array of public sector agencies, private enterprises, and regional organizations.
Institutional supporters contributing to the platform include AfriGIS, Camptocamp, DLR, Dorset Council, Deutsche Telekom, Frachtwerk GmbH, GeoCat BV, Geocrafter – Geospatial Studio, Comune di Genova, g.on, GeoSolutions SRL, geosos, Geospatial Enabling Technologies (GET), Incloud Limited, HL Consulting, Institut national de l’information géographique et forestière (IGN), ITS Digital, JDev, Kreditanstalt für Wiederaufbau, Mammoth Geospatial, National Ocean Service (NOA), Plangis, Office of Public Works, Open Geo Groep, OSGeo:Korea, OSGeo:UK, Quarticle Research Srl, Sea Island Software, Tailormap, terrestris, Ubigu, Value AG, Region Västra Götaland, and WaldExpert.
In addition to these corporate and governmental sponsors, the project acknowledges the individual donations provided by Abhijit Gujar, Hennessy Becerra, Ivana Ivanova, John Bryant, Jason Horning, Jose Macchi, Peter Smythe, Sajjadul Islam, Sebastiano Meier, and Stefan Overkamp. Their collective support ensures that the project can continue to innovate and meet the demands of modern geospatial data architectures.
Introduction of the FIPS Community Module
GeoServer 3.0.2 introduces a brand new FIPS community module designed to meet strict regulatory and compliance requirements. Federal agencies in the United States and their commercial contractors are frequently bound by strict mandates requiring the use of cryptography modules validated under the Federal Information Processing Standard (FIPS) 140-3. This new module enables compliant deployments by ensuring that cryptographic operations adhere to these government-mandated benchmarks.
Deployers should note that the FIPS module currently operates exclusively on Linux environments and requires a freshly initialized data directory, as an automated migration tool for existing data directories is not yet available. Comprehensive documentation for setting up and configuring the FIPS environment has been published in the official user manual.
Release Notes and Community Development
The 3.0.2 release encompasses numerous bug fixes, performance improvements, and ongoing tasks aimed at refining the user and developer experience. A complete, itemized catalog of all new features, enhancements, resolved bugs, and maintenance tasks is publicly accessible via the official GitHub release notes for version 3.0.2.
Parallel to the core release, development on various community modules continues at a rapid pace. These modules are intentionally shared as raw source code within the repository to encourage community-wide collaboration, experimentation, and peer review. Developers and organizations interested in exploring or expanding upon these experimental topics are encouraged to reach out directly to individual module developers to coordinate contributions and offer assistance.
As the GeoServer 3.0 series continues to mature, users looking for historical context or previous iteration logs can reference the detailed release notes for versions 3.0.0, 3.0.1, and 3.0.2 through the project’s primary repository channels.
