GeoServer PSC meeting notes, May 19th 2026

GeoTools / GeoServer PMC meeting - 2026-05-19

Attending

  • Torben Barsballe

  • Cécile Vuilleumier

  • Kevin Smith

  • Andrea Aime

  • Nuno Oliveira

  • Peter Smythe

  • Alessandro Ricchiuti

  • Jody Garnett

Actions from prior meetings:

  • non selezionata|17.599999999999998pxx17.599999999999998px

    jody: Contact OGC about CITE for 3.0.0

    • Asked can just certify 3.0.0 and replace 2.28 sticker on website
      (no response yet)
  • non selezionata|17.599999999999998pxx17.599999999999998px

    jody: checkout 3.0-RC tag and deploy manually

Agenda

  1. CITE certification costs

  2. GeoServer Security Volunteers (Alessandro and Pierre)

  3. GeoServer 2.28.4 release manager

  4. GeoServer 3.0 release planning

  5. OAuth extension promotion & migration guide

  6. Chit Chat

Actions

  • non selezionata|17.599999999999998pxx17.599999999999998px

CITE certification costs

Cost estimation: up to 2700$ (OGC API tiles might be one instead of 5, which needs to be confirmed).

Jeroen then replied, contacting OGC, and getting new feedback… we might switch certification from 2 to 3 (losing the certification on 2.28 in the process).

We either switch in time, or we’ll indicate that we pass, that we’re working on getting certified, and we’ll make an announcement later.

GeoServer Security Volunteers (Alessandro and Pierre)

AI reports are increasing (duplicates, false positives too), and we need more manpower. Here is Alessandro Ricchiuti, who would like to join. Pierre from C2C would also like to join.

Jody: Add new volunteers to Security list

GeoServer 2.28.4 release manager

https://github.com/geoserver/geoserver/wiki/Release-Schedule#2026

Peter is working on it, Andrea to release imageio-ext 2.0.1

GeoServer 3.0 release planning

QA fixes and UI improvement:

https://github.com/geoserver/geoserver/pull/9494

OAuth extension promotion & migration guide

The new OAUTH plugin is not backwards compatible, so a migration manual is needed, Alessio will work on it. When GeoServer starts up if it doesn’t find a filter that doesn’t exist it will break, this should be reviewed.

The promotion to extension didn’t move forward, one requirement for it to move forward would be to have some real use cases installations. There were two users reporting they were configuring it and deploying it.

For pending:

  • This is an option, but real world experience may be gathered in time.

  • We can also consider jwt-headers for pending

Chit Chat

Please help review pull-requests folks!
We are into “final” crunch when many unexpected PRs show up with fixes prior to release.

Allow me to correct myself (thanks for questioning it Andrea):

Cost estimation: up to 2100$ (OGC API tiles is only one instead of 5).

Part 1: Core (v1.0)

On the other hand,

ogcapi-features-1.0 remains a 2 (out of 3 or 5) part certification, thus we pay 2x$150.

Part 1: Core (v1.0.1 corrigendum)
Part 2: CRS by Reference (v1.0.1 corrigendum)
Part 3: Filtering, version 1.0.0
Part 4 & 5 are still in draft

Peter

I also took the opportunity to push the OIDC testing in the user forum: GeoServer 3.0-RC OIDC module – special call for feedback

1 Like