[Geoserver-devel] [JIRA] (GEOS-9436) Monitor extension : Ignoring Post processors through configuration
Title: Message Title Imran Rajjad created an issue GeoServer / GEOS-9436 Monitor extension : Ignoring Post processors through configuration Issue Type: Improvement Affects Versions: 2.16.2, 2.17-RC Assignee: Imran Rajjad Components: Monitoring Created: 19/Dec/19 7:34 AM Priority: Medium Reporter: Imran Rajjad A new option inside the `monitor.properties` file to ignore post processors inside monitor extension. The ignoring of post processors can be done by a new option ignorePostProcessors with valid comma separated values (valid values = reverseDNS,geoIp,layerNameNormalizer) Add Comment
Re: [Geoserver-devel] geoserver release 2.15.4 reminder
Excellent, I will process with GWC today. On Wed, Dec 18, 2019 at 11:27 PM Gabriel Roldan wrote: > Btw, after the geotools hotfix for GEOT-6380, the revision numbers are: > > >- GeoServer (rev0b37fcc2b4f82f0d96bf3b04db284b73c8a85c14) >- GeoTools (rev ddef3caa29b06e3fd2d860a04b8133d5840d0292) >- GeoWebCache (rev 6530ecc57f861d952383917ce86fca7021402e22) > > > > On Wed, 18 Dec 2019 at 08:27, Jody Garnett wrote: > >> Checking nightly build for the following revision numbers: >> >> >>- GeoServer (rev0b37fcc2b4f82f0d96bf3b04db284b73c8a85c14) >>- GeoTools (rev 357aa214a7279a21b937e3071106df26a2d8c36f) >>- GeoWebCache (rev 6530ecc57f861d952383917ce86fca7021402e22) >> >> Aside: The About GeoServer page lists GWC revision twice for some reason. >> -- >> Jody Garnett >> >> >> On Tue, 17 Dec 2019 at 17:37, Jody Garnett >> wrote: >> >>> Release is scheduled for tomorrow (mostly likely over several days). >>> Last call for bug fixes :) >>> -- >>> Jody Garnett >>> >> ___ > > >> Geoserver-devel mailing list >> Geoserver-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> > > > -- > Gabriel Roldán > -- -- Jody Garnett ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] geoserver release 2.15.4 reminder
Btw, after the geotools hotfix for GEOT-6380, the revision numbers are: - GeoServer (rev0b37fcc2b4f82f0d96bf3b04db284b73c8a85c14) - GeoTools (rev ddef3caa29b06e3fd2d860a04b8133d5840d0292) - GeoWebCache (rev 6530ecc57f861d952383917ce86fca7021402e22) On Wed, 18 Dec 2019 at 08:27, Jody Garnett wrote: > Checking nightly build for the following revision numbers: > > >- GeoServer (rev0b37fcc2b4f82f0d96bf3b04db284b73c8a85c14) >- GeoTools (rev 357aa214a7279a21b937e3071106df26a2d8c36f) >- GeoWebCache (rev 6530ecc57f861d952383917ce86fca7021402e22) > > Aside: The About GeoServer page lists GWC revision twice for some reason. > -- > Jody Garnett > > > On Tue, 17 Dec 2019 at 17:37, Jody Garnett wrote: > >> Release is scheduled for tomorrow (mostly likely over several days). Last >> call for bug fixes :) >> -- >> Jody Garnett >> > ___ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > -- Gabriel Roldán ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] geoserver release 2.15.4 reminder
Checking nightly build for the following revision numbers: - GeoServer (rev0b37fcc2b4f82f0d96bf3b04db284b73c8a85c14) - GeoTools (rev 357aa214a7279a21b937e3071106df26a2d8c36f) - GeoWebCache (rev 6530ecc57f861d952383917ce86fca7021402e22) Aside: The About GeoServer page lists GWC revision twice for some reason. -- Jody Garnett On Tue, 17 Dec 2019 at 17:37, Jody Garnett wrote: > Release is scheduled for tomorrow (mostly likely over several days). Last > call for bug fixes :) > -- > Jody Garnett > ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] [JIRA] (GEOS-9435) [community - oauth2] Include basic auth header for Oauth2 token instrospection requests
Title: Message Title Alessio Fabiani created an issue GeoServer / GEOS-9435 [community - oauth2] Include basic auth header for Oauth2 token instrospection requests Issue Type: Improvement Assignee: Alessio Fabiani Components: Community modules, OAuth2, Security Created: 18/Dec/19 12:00 PM Priority: Medium Reporter: Alessio Fabiani Currently no authentication is provided when oauth2 provider sends requests to introspect token (for example when calling tokeninfo/ endpoint). As suggested buy common best practices for Oauth2 an authentication is highly encuraged to reduce the exposure to attacks exposure and prevent user private data leakage. The proposal is to add an auth header inside the requests with basic auth encoding of the client is and client secret: base64(client_id:client_secret) This solution will make ti compatible with several oauths/oidc backends (like django-oidc-provider( which expects this header to allow the request. Add Comment
