How to include jwt-headers extension in community-latest nightly builds?

GeoServer GeoServer Developer
1

Hello GeoServer developers,

I recently worked on GeoServer PR #8734, which updates the jwt-headers community extension (dependency upgrades and security fixes). The PR has already been merged into main.

However, I’ve noticed that the extension does not appear in the “community-latest” nightly build bundle:
https://build.geoserver.org/geoserver/main/community-latest/

Could anyone clarify what steps are needed to make a new community module automatically included in that build/distribution?
Do I need to adjust a specific Maven profile, update a packaging configuration, or trigger something in the CI scripts?

Thanks for your guidance!

2

While not 100% sure, my guess is that the assembled zip does not make it to the server, because it’s not following the right naming convention.
The assembly.xml should have an id equal to “gs-jwt-headers-plugin”, and it’s lacking the last part of it instead:

If you check the other assembly.xml files under src/community, they should be all following the -plugin convention instead.

Cheers
Andrea

3

Hi everyone,

are there any updates on including jwt-headers in the build output?

We’d also love to see the extension there, especially because the OIDC extension requires it and none of the 2.28 builds includes it.

Thanks and best regards

André

4

Here’s the PR fixing it in main. I have just backported it to 2.28

1 Like
5

Hi Peter,

thanks for the swift response and action! Currently, there seems to be a problem with the build.

But this is exactly what we need :slight_smile:

Best regards

André

1 Like