The open-source geospatial community has announced the official release of GeoServer 3.0.2, marking a major milestone in the ongoing stabilization and enhancement of the popular mapping server. Available immediately for download across standard binary, Web Archive (WAR), and Windows installer formats, alongside comprehensive documentation and a robust suite of extensions, this latest stable release is strongly recommended for mission-critical production environments.
The new software drop incorporates a series of foundational updates, including the latest GeoTools 35.2 and GeoWebCache 2.0.2 releases. Furthermore, it integrates mapfish-print-v2 2.5.2 and ImageN 0.9.3 to ensure optimal rendering and printing performance. In a notable development for cloud-native deployments, GeoServer Cloud 3.0.2 has been released simultaneously with the core platform, marking the first time an updated cloud iteration has been made available directly on release day.
Project contributors and maintainers played a pivotal role in bringing this version to fruition. Special recognition goes to Jody Garnett of GeoCat for orchestrating the release process, Andrea Aime of GeoSolutions for rigorous pre-release testing, and Gabriel Roldan of Camptocamp for spearheading the synchronized GeoServer Cloud launch.
Security Considerations and Production Upgrades
Security remains a primary focus for the GeoServer development team, and version 3.0.2 addresses critical security vulnerabilities that make it an essential upgrade for any organization running production systems. While the update patches these vulnerabilities immediately, detailed descriptions and technical breakdowns of the specific security fixes will be published publicly at the start of November, following standard vulnerability disclosure protocols. Users managing enterprise mapping infrastructure are encouraged to review the project’s established security policy documentation on GitHub for comprehensive guidelines on how vulnerabilities are handled, reported, and remediated within the ecosystem.
OGC API Maps 1.0 Integration
Interoperability continues to be a driving force behind open-source geospatial software development. In GeoServer 3.0.2, the OGC API Maps community module has undergone significant updates to align fully with the final OGC API – Maps 1.0.0 standard. This alignment ensures that organizations utilizing GeoServer can seamlessly serve map resources in compliance with modern open geospatial web standards, facilitating better integration with diverse web mapping clients and spatial data infrastructures.
The successful implementation of the OGC API Maps alignment is the result of collaborative development efforts. Andrea Aime of GeoSolutions led the core development work for the module, while Jody Garnett of GeoCat handled the 3.0.x backporting and introduced vital improvements to the conformance table editor, ensuring a smooth and standards-compliant user experience.
GeoFence for GeoServer 3
The release of GeoServer 3.0.2 also brings fully integrated GeoFence extensions to the GeoServer 3 series. This launch marks the successful completion of Milestone 4: Integration, an objective established under the comprehensive GeoServer 3 crowdfunding campaign.
To bring GeoFence up to date with modern enterprise architectures, the extension has been modernized to run on Jakarta EE, Spring Framework 7, and Hibernate 7. This technical overhaul ensures long-term maintainability and high performance for access control and security management within spatial databases.
However, administrators currently utilizing older iterations of GeoFence must exercise caution before initiating an upgrade. Existing users are strongly advised to consult the official migration guide available in the user manual. The upgrade path requires careful planning because the datasource configuration file has been renamed, and the legacy GeoFence authentication provider has been completely removed in this version.
The delivery of GeoFence for GeoServer 3 was led by Emanuele Tajariol of GeoSolutions, whose development efforts were made possible entirely through the financial contributions and backing of the GeoServer 3 crowdfunding sponsors. The broader GeoServer 3 initiative continues to receive foundational support from a diverse coalition of organizational sponsors and individual donors from around the globe. Corporate backers include AfriGIS, Camptocamp, DLR, Dorset Council, Deutsche Telekom, Frachtwerk GmbH, GeoCat BV, Geocrafter, 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, 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, the project acknowledges individual financial contributions from Abhijit Gujar, Hennessy Becerra, Ivana Ivanova, John Bryant, Jason Horning, Jose Macchi, Peter Smythe, Sajjadul Islam, Sebastiano Meier, and Stefan Overkamp.
FIPS Cryptography Compliance Module
Addressing the strict regulatory requirements of government agencies and enterprise suppliers, GeoServer 3.0.2 introduces a new FIPS community module. The Federal Information Processing Standards (FIPS) 140-3 is a rigorous United States government standard governing cryptography modules. Many federal agencies, defense contractors, and regulated industries are legally or contractually mandated to operate software that exclusively utilizes validated cryptographic modules.
This new community module brings native FIPS compliance capabilities to the platform, though administrators must note specific operational constraints. The FIPS module is currently supported exclusively on Linux operating systems and requires a freshly initialized data directory. There is currently no automated migration tool available to convert an existing standard data directory into a FIPS-compliant structure, requiring careful manual setup for organizations transitioning their environments.
Release Notes and Community Development
The complete inventory of improvements, bug fixes, and development tasks addressed in this cycle can be found in the official 3.0.2 release notes hosted on GitHub. Alongside the core updates, community module development remains active, with contributors continuously exploring experimental features and extensions. Because community modules are shared primarily as source code to foster open collaboration, developers interested in specific experimental topics are encouraged to reach out directly to module authors to offer assistance and accelerate feature maturity within the ecosystem.
