Re: [Geoserver-devel] Reminder: GeoTools / GeoServer meeting at 15:30 UTC on Tuesday

[bradh]

Please accept my apologies.

Brad



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Reminder: GeoTools / GeoServer meeting at 15:30 UTC on Tuesday

[Ben Caradoc-Davies]

GeoTools / GeoServer committee meeting on Skype at 15:30 UTC on Tuesday:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+/+GeoServer+Meeting=2018=4=17=15=30=0=1

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-8688) Using the WCS "Limited SRS list" can lead to invalid GetCapabilities

[Jukka Rahkonen (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jukka Rahkonen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8688  
 
 
  Using the WCS "Limited SRS list" can lead to invalid GetCapabilities   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 2.13.0  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 WCS  
 
 
Created: 
 16/Apr/18 9:56 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Jukka Rahkonen  
 

  
 
 
 
 

 
 If user configures "Limited SRS list" in the WCS settings then only those coordinate systems are included in the WCS 2.0.1 GetCapabilities as . This may be wrong because in any case the service must support the native CRS of each coverage in the service. What should appear in the GetCapabilities is  
 
a list of all distinct native CRS values of all the coverages in the service 
plus possible new CRS values from the user defined Limited SRS list 
 Reference: For example "6.2 Modifications to GetCapabilities" of the Web Coverage Service Interface Standard - CRS Extension In its crsSupported component it contains the list of CRSs in which the server can return coverages and after Requirement 9: Note As per WCS Core [OGC 09-110r3] every coverage has a Native CRS associated which will be contained in this list among potentially more CRSs; therefore, this list will never be empty as long as the server offers at least one coverage How to reproduce: Configure a limited list with only EPSG:3857. GetCapabilities will list only EPSG:3857 even the coverages in the demo data have other native CRS values.  
 

  

[Geoserver-devel] [JIRA] (GEOS-8687) WCS multidimensional requests (NetCDF/Grib outputs) may lead to un-closed readers and eventually OOMs

[Andrea Aime (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrea Aime created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8687  
 
 
  WCS multidimensional requests (NetCDF/Grib outputs) may lead to un-closed readers and eventually OOMs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 WCS  
 
 
Created: 
 16/Apr/18 6:57 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Andrea Aime  
 

  
 
 
 
 

 
 Multidimensional outputs make WCS generate a GranuleStackImpl as the output "coverage". This plays badly with the coverage cleanup code here: https://github.com/geoserver/geoserver/blob/cd45206f93c4c42388484b4a2a96bd469fde698f/src/wcs/src/main/java/org/geoserver/wcs/CoverageCleanerCallback.java#L68 because the GranuleStackImpl.getRenderedImage returns null: https://github.com/geoserver/geoserver/blob/7076e763387f0f682d05959e5b2d10442be12cf2/src/wcs2_0/src/main/java/org/geoserver/wcs2_0/response/GranuleStackImpl.java#L101 thus preventing the "recursive cleanup" code that also ends up closing readers and the like (because it's based on the RenderedImage, not the coverage) Indeed I don't see NetCDFImageReader.dispose ever being called in a debugger, while doing requests over NetCDF inputs doing multi-coverage NetCDF outputs.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment  
 

[Geoserver-devel] Introduction

[Ronald Hoek - ComponentAgro B . V .]

Hello,

My name is Ronald Hoek.
I'm a spectrum wide application developer (analyst, design, programming, 
testing, user support, bug-fixing, etc.) for a company in the Netherlands.

Recently (this year) we created an application (using Delphi), which matches 
geo-data from different (secure) sources with each other.

Because this data was not always available as a service (and the data was to 
large to distribute), I started looking for a (web)service, which could 'host' 
that geo-data, so the application could request only parts of the complete set.

Then I found GeoServer as one of the first hits, and I was really positively 
surprised by all the possibilities the application has. We did not look very 
far for other solutions, because GeoServer looked so promising and showed some 
exceled behavior an performance during the first tests and the fact GeoServer 
showed very active development.

But as always all software has issues ( 
https://osgeo-org.atlassian.net/browse/GEOS-8683 ).

So now here I am - as a newby to GeoServer - offering to help with further 
development of GeoServer.

As I'm not a Java Developer, but a Windows Application Developer, for now I 
would like to help with tuning the Windows Installer.

I would suggest the following changes in the installer behavior:

  *   Never to overwrite/delete/add files in an existing 'data_dir'
  *   Suggest to the user to use a 'data_dir' outside the application directory
 *   Note: it's best to uninstall the software before upgrading, as the 
'old' Windows Service Entry is removed and a new one is  created

Maybe other issue might be changed in due time.
But for now these are the two issues I would like to change (I also need to 
learn NSIS first...)
Regards,
Ronald Hoek
Application Developer
ComponentAgroB.V.
Oud-Beijerland - The Netherlands
Website: http://www.componentagro.nl
KvK: H24264020

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Jenkins build is back to normal : geoserver-2.13.x #58

[monitor]

See 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-8686) Problem with GeoFence roles checking

[Julien SABATIER (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julien SABATIER created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8686  
 
 
  Problem with GeoFence roles checking   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.12.1  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 geoserver.getcap.log  
 
 
Components: 
 GeoFence  
 
 
Created: 
 16/Apr/18 12:10 PM  
 
 
Environment: 
 Debian 9, Oracle JAVA 8 External OpenLDAP server configured as User, groups and roles service. 17 workspaces, 218 layers, 54 geofence's rules On LDAP : 836 users and 124 roles  
 
 
Priority: 
  High  
 
 
Reporter: 
 Julien SABATIER  
 

  
 
 
 
 

 
 When request a GetCapabilities with a user who have different roles (tested with 3, not admin) on the main wfs/wms URL (/geoserver/wfs), It took a very long time to generate the response (~10minutes). If I set VERBOSE_MODE, I see in the log that for a single user, GeoFence seems to request LDAP for user and user's role a huge amount of time (cf attached file). With tcpdump, I see a huge traffic on port 636 (ldaps) when requesting getcap document. I think there is a huge problem with GeoFence access right checking as it took 10 minutes for a simple GetCapabilities.  
 

  
 
 
  
 
 

Re: [Geoserver-devel] [Geotools-devel] [Geowebcache-devel] GSIP 168, skip beta releases and remove feature freeze

[Alessio Fabiani]

+1 thanks

Regards,

Alessio Fabiani

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==

Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead


GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob:   +39 331 6233686

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

---

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

2018-04-15 19:01 GMT+02:00 Simone Giannecchini <
simone.giannecch...@geo-solutions.it>:

> +1
>
> Regards,
> Simone Giannecchini
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> ==
> Ing. Simone Giannecchini
> @simogeo
> Founder/Director
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob:   +39  333 8128928
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> ---
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate.
> Il loro utilizzo è consentito esclusivamente al destinatario del
> messaggio, per le finalità indicate nel messaggio stesso. Qualora
> riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
> cortesemente di darcene notizia via e-mail e di procedere alla
> distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
> Conservare il messaggio stesso, divulgarlo anche in parte,
> distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
> diverse, costituisce comportamento contrario ai principi dettati dal
> D.Lgs. 196/2003.
>
> The information in this message and/or attachments, is intended solely
> for the attention and use of the named addressee(s) and may be
> confidential or proprietary in nature or covered by the provisions of
> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
> Data Protection Code).Any use not in accord with its purpose, any
> disclosure, reproduction, copying, distribution, or either
> dissemination, either whole or partial, is strictly forbidden except
> previous formal approval of the named addressee(s). If you are not the
> intended recipient, please contact immediately the sender by
> telephone, fax or e-mail and delete the information in this message
> that has been received in error. The sender does not give any warranty
> or accept liability as the content, accuracy or completeness of sent
> messages and accepts no responsibility  for changes made after they
> were sent or for other risks which arise as a result of e-mail
> transmission, viruses, etc.
>
>
> On Sun, Apr 15, 2018 at 2:10 PM, Ben Caradoc-Davies 
> wrote:
> > +1. Thanks, Andrea.
> >
> > Kind regards,
> > Ben.
> >
> >
> > On 15/04/18 20:52, Andrea Aime wrote:
> >>
> >> Hi,
> >> as promised here is the GSIP for the release procedure change we've
> >> already
> >> applied to 2.13.x:
> >>
> >> https://github.com/geoserver/geoserver/wiki/GSIP-168
> >>
> >> Please vote :-)
> >>
> >> Cheers
> >> Andrea
> >>
> >> ==
> >>
> >> GeoServer Professional Services from the 

Re: [Geoserver-devel] how does GeoServer modify a WMS/WMTS request to add authentication?

[Steve Omondi]

Hi Andrea,

Ian, I think that WMS/WMTS/WFS cascading never supported anything besides
> basic and maybe digest authentication.
>
​I can report that I did WMS Cascading​

​with Authkey successfully and it works.

So I wanted to Cascade WMTS in similar way so I can reuse tiles from the
source Geoserver and then it wasn't working wiht the same Authkey.
​
In the same line, WMTS Cascading with Basic Authentication does not work
either





Kind regards,
Steve Omondi

On Sun, Apr 15, 2018 at 4:51 PM, Andrea Aime 
wrote:

> Ah,
> Ian, I think that WMS/WMTS/WFS cascading never supported anything besides
> basic and maybe digest authentication.
> A mechanism such as "authkey" requires the server to add the key into the
> capablilities backlinks (geoserver authkey does
> that, barring any bug), otherwise the client has to know about it, which
> defeats the purpose of the module.
> And working off the links in GetCapabilities is the standard and "correct"
> behavior.
>
> If you're talking with a server that does not add back the key into the
> caps document, then you'll need to add your own
> auth support in the client.
> Again, in the HTTP client would be best, the generic WMS/WMTS should stay
> auth unaware, there
> are just too many possible auth mechanism, best to centralize them in the
> http clients or a wrapper of them.
>
> Cheers
> Andrea
>
>
> On Sun, Apr 15, 2018 at 2:27 PM, Ian Turton  wrote:
>
>> I think that code only handles the "basic" authentication whereas this
>> bug is related to authkey - so at some point someone writes authkey=x
>> into the URL, I just can't work out where.
>>
>> Ian
>>
>> On 15 April 2018 at 10:31, Andrea Aime 
>> wrote:
>>
>>> Hi Ian,
>>> I'm not too familiar with the code bases, but think that the
>>> authentication does not happen in the WMS/WMTS code, but
>>> in the HTTP client instead, e.g.:
>>>
>>> https://github.com/geotools/geotools/blob/master/modules/lib
>>> rary/main/src/main/java/org/geotools/data/ows/SimpleHttpClient.java#L138
>>> https://github.com/geotools/geotools/blob/master/modules/ext
>>> ension/wms/src/main/java/org/geotools/data/ows/Multithreaded
>>> HttpClient.java#L144
>>>
>>> Hope this helps
>>>
>>> Cheers
>>> Andrea
>>>
>>>
>>>
>>> On Fri, Apr 13, 2018 at 1:25 PM, Ian Turton  wrote:
>>>
 I've been looking at GEOS-8671
  thinking it was a
 simple find and replace issue in the WMTS code but it looks like all the
 WMTS code does is take the URL from the getCapabilities response (or the
 server URL if that fails) and makes a request to that. So I now suspect
 that at some point the security code is adding the authentication code to
 the URL - I guessed that SecuredWMTSLayer might be the place to look, but
 that seems to nothing to the URL, tracking back I came to
 SecuredWMTSStoreInfo which looks possible as it calls
 SecuredObjects.secure(wms, policy) - but I can't for the life of me work
 out what is going on in there.

 The worrying thing is that all that SecuredWMTS* code is a straight
 copy and paste from SecuredWMS* so if this fails for WMTS I suspect it will
 fail for WMS.

 Can any one point me to the code that actually rewrites the URL to
 insert the authenicationkey?

 cheers

 Ian
 --
 Ian Turton

 
 --
 Check out the vibrant tech community on one of the world's most
 engaging tech sites, Slashdot.org! http://sdm.link/slashdot
 ___
 Geoserver-devel mailing list
 Geoserver-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geoserver-devel


>>>
>>>
>>> --
>>>
>>> Regards,
>>>
>>> Andrea Aime
>>>
>>> ==
>>> GeoServer Professional Services from the experts! Visit
>>> http://goo.gl/it488V for more information.
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions S.A.S.
>>> Via di Montramito 3/A
>>> 
>>> 55054  Massarosa
>>> 
>>> (LU)
>>> phone: +39 0584 962313
>>> fax: +39 0584 1660272
>>> mob: +39  339 8844549
>>>
>>> http://www.geo-solutions.it
>>> http://twitter.com/geosolutions_it
>>>
>>> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>>>
>>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>>> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
>>> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
>>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
>>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
>>> darcene notizia via