Complete GeoServer Configuration Parametrization

[simboss]

Apparently the GeoServer Configuration Parametrization does not yet cover certain portions of the configurations (like Security) thus making it difficult to do complete back-ups and restore of the configuration itself in certain environments.

I am asking @giohappy to report his experience on this matter so to drive the scoping work and the successive estimates from the GeoServer team. Obviousl this is an epic as we will have to decide what to implement and in which order once we have a plan with estiamtes.

[giohappy]

@simboss my experience is mainly restricted to the geonode-oauth2 module and authkey modules, but afaik all the security modules are affected by the lack of ability to parametrize their configurations.

• geonode-oauth2
  • Authentication filter using a GeoNode OAuth2
• AuthKey
  • Authentication filter using a key
  • AuthKEY REST Role Service (which is also used by geonode setup)
  • AuthKEY WebService Body Response UserGroup Service (we use it for DJAM)

[simboss]

Anything about GWC. I am pretty sure GWC does not work well with parameterization as well.

[giohappy]

I guess GWC would also benefit from having parametrized configs. I suppose you refer to Caching defaults and Disk Quota mainly.

[nmco]

@simboss is this still something we want?

[simboss]

obviously

[nmco]

GWC parameterization is being discussed HERE.